@danmoisan/drm-copilot-mcp 1.1.25 → 1.1.27

package/resources/powershell/PoshQC/PoshQC.Testing.psm1

@@ -183,10 +183,11 @@ function Invoke-PoshQCTest {
         [scriptblock] $EnsureModule = {
             param([string] $Name, [string] $ErrorMessage, [string] $MinimumVersion, [string] $MaximumVersion)
             # Issue #953 (CR-1): only an installed version inside the supported range counts as present, so a host
-            # whose only Pester is 6.x or the inbox 3.4.0 receives the actionable message instead of an import error.
+            # whose only Pester is 7.x or the inbox 3.4.0 receives the actionable message instead of an import error.
             if (-not (Get-Module -ListAvailable -FullyQualifiedName @{ ModuleName = $Name; ModuleVersion = $MinimumVersion; MaximumVersion = $MaximumVersion })) { throw $ErrorMessage }
-            # Import globally so Pester's Describe/It/Mock resolve in test containers that the
-            # default $InvokePester trampoline now hosts in the global session state (issue #392).
+            # Import globally so Pester's Describe/It/Mock resolve in test containers. Under the default
+            # $InvokePester trampoline, test code runs in this module's session state, not the global
+            # session state (issue #392; see the $InvokePester comment for the Mock consequence).
             # Issue #953 (D8, CR-2): -MinimumVersion and -MaximumVersion keep the import inside the supported range.
             Import-Module $Name -Global -MinimumVersion $MinimumVersion -MaximumVersion $MaximumVersion -ErrorAction Stop
         },
@@ -286,14 +287,15 @@ function Invoke-PoshQCTest {
         },
         [scriptblock] $InvokePester = {
             param($Config)
-            # Host the Pester run in the global session state so discovered test containers do
-            # not execute inside this module's session state. This makes the bundled entry path
-            # (module pre-imported, then Invoke-PoshQCTest -> Invoke-Pester) match the passing
-            # direct run, and lets BeforeAll module guards in test files safely remove/re-import
-            # same-named modules mid-run without orphaning the run's hosting session state
-            # (issue #392). [scriptblock]::Create builds an unbound scriptblock so the installed
-            # global function is not bound to this module's session state; the try/finally pair
-            # removes the temporary global function so no state leaks between suite invocations.
+            # Run Invoke-Pester through a temporary global function built with [scriptblock]::Create,
+            # so the function itself is not bound to this module's session state (issue #392). The
+            # discovered test code nevertheless runs in this module's session state: a test reports
+            # $ExecutionContext.SessionState.Module as PoshQC here, and $null under a plain
+            # Invoke-Pester run. Consequence: after a test re-imports PoshQC, Mock -ModuleName PoshQC
+            # from test code does not reach the re-imported instance; such a test runs its body in
+            # InModuleScope PoshQC and mocks without -ModuleName (observed in issue #1067). The
+            # try/finally pair removes the temporary global function so no state leaks between suite
+            # invocations.
             $trampoline = [scriptblock]::Create('param($c) Invoke-Pester -Configuration $c')
             $null = New-Item -Path 'function:global:Invoke-PoshQCPesterRun' -Value $trampoline -Force
             try {
@@ -325,7 +327,7 @@ function Invoke-PoshQCTest {
         $Root = [IO.Path]::GetFullPath([IO.Path]::Combine($PWD.ProviderPath, $Root))
     }
 
-    & $EnsureModule 'Pester' "Pester is not installed in the supported range (5.9.0 to 5.99.99). Run Install-PoshQCTool (alias Install-PoshQCTools) first." '5.9.0' '5.99.99'
+    & $EnsureModule 'Pester' "Pester is not installed in the supported range (6.2.0 to 6.99.99). Run Install-PoshQCTool (alias Install-PoshQCTools) first." '6.2.0' '6.99.99'
 
     if (-not (& $TestPathExists $SettingsPath)) {
         throw "Settings not found: $SettingsPath"

package/resources/powershell/PoshQC/PoshQC.psm1

@@ -53,9 +53,9 @@ function Install-PoshQCTool {
     }
 
     $requiredModules = @(
-        @{ Name = 'PSScriptAnalyzer'; Version = '1.22.0' },
-        # Issue #953 (D8): UpperBound is exclusive; an installed Pester 6.x does not satisfy the requirement.
-        @{ Name = 'Pester'; Version = '5.9.0'; UpperBound = '6.0.0' }
+        @{ Name = 'PSScriptAnalyzer'; Version = '1.25.0' },
+        # The selected Pester 6 range excludes the next major until separately validated (issue #1082).
+        @{ Name = 'Pester'; Version = '6.2.0'; UpperBound = '7.0.0' }
     )
 
     # Issue #953 (CR-3): one version-range predicate serves the present check and the post-install check.

package/resources/powershell/PoshQC/README.md

@@ -6,14 +6,14 @@ PoshQC is a lightweight PowerShell quality gate that wraps Invoke-Formatter, PSS
 
 - Formats PowerShell code with consistent indentation and pipeline alignment.
 - Lints with PSScriptAnalyzer using a strict, dual-runtime ruleset.
-- Runs Pester tests with code coverage (CoverageGutters output), plus an optional Koverage-friendly copy.
+- Runs Pester tests with code coverage (JaCoCo output), plus an optional Koverage-friendly copy.
 - Provides a single suite entry point that can format, analyze, and test a selected workspace scope.
 - Provides a one-time dependency installer for PSScriptAnalyzer and Pester.
 
 ## Requirements
 
 - PowerShell 5.1 or 7.6+
-- Modules: PSScriptAnalyzer 1.22.0, Pester 5.9.0 or later, below 6.0 (installed automatically via the helper if missing)
+- Modules: PSScriptAnalyzer 1.25.0, Pester 6.2.0 or later, below 7.0 (installed automatically via the helper if missing)
 
 ## Getting started
 
@@ -48,7 +48,7 @@ PoshQC is a lightweight PowerShell quality gate that wraps Invoke-Formatter, PSS
    ```
 
    - Writes JUnit XML to `artifacts/pester/pester-junit.xml`.
-   - Writes CoverageGutters XML to `artifacts/pester/powershell-coverage.xml`.
+   - Writes JaCoCo XML to `artifacts/pester/powershell-coverage.xml`.
    - Also emits `*.koverage.xml` (relative paths) for VS Code Coverage Gutters and Koverage. Disable with `-DisableKoverageCopy` or override the path with `-KoverageOutputPath`.
 
 ## Functions
@@ -63,7 +63,7 @@ PoshQC is a lightweight PowerShell quality gate that wraps Invoke-Formatter, PSS
 - `New-PoshQCShardManifest`: build the in-memory shard manifest (`shardIndex`, `shardCount`, `all`, `selected`, `selectedFullPath`).
 - `Test-PoshQCShardCompleteness`: throw unless a set of shard manifests selects every test file exactly once.
 - `Test-PoshQCShardTestCount`: throw unless the shard test counts sum to a discovery-pass test count.
-- `Merge-PoshQCCoverageReport`: merge the CoverageGutters XML texts of the shards at LINE granularity (no file I/O, no threshold).
+- `Merge-PoshQCCoverageReport`: merge the JaCoCo XML texts of the shards at LINE granularity (no file I/O, no threshold).
 - `Get-PoshQCCoverageLineSummary`: return covered, missed, total, and percent from a report's LINE counter.
 - `Invoke-PoshQCParallelTest`: run the Pester suite as concurrent shard processes on one machine and merge the results (see Local concurrent runs below).
 - `Get-PoshQCParallelWorkerCount`: return the default worker count, half the logical processors, at least 1 and at most 8.
@@ -75,8 +75,8 @@ PoshQC is a lightweight PowerShell quality gate that wraps Invoke-Formatter, PSS
 - PSScriptAnalyzer settings: `./settings/pssa.settings.psd1`
    - Enforces compatible syntax for 5.1 and 7.6, 4-space indentation, ShouldProcess for state-changing functions, and safety guards (no Invoke-Expression, no global vars, etc.).
 - Pester settings: `./settings/pester.runsettings.psd1`
-  - Runs tests under `scripts` and `tests/powershell`, outputs JUnit XML and CoverageGutters coverage, and enables coverage. The shipped runsettings carry no `CodeCoverage.Path` list; `Invoke-PoshQCTest` derives the coverage population from the workspace (see Coverage population below).
-  - Coverage uses Pester's profiler-based mode (`CodeCoverage.UseBreakpoints = $false`, issue #953), which needs Pester 5.4 or later and is faster than breakpoint mode on the same coverage population. The PoshQC suites target PowerShell 7; profiler mode under Windows PowerShell 5.1 is not exercised in CI. To use breakpoint mode, pass a settings file with `UseBreakpoints = $true` through `-SettingsPath`.
+  - Runs tests under `scripts` and `tests/powershell`, outputs JUnit XML and JaCoCo coverage, and enables coverage. The shipped runsettings carry no `CodeCoverage.Path` list; `Invoke-PoshQCTest` derives the coverage population from the workspace (see Coverage population below).
+  - Coverage uses Pester's profiler-based mode (`CodeCoverage.UseBreakpoints = $false`, issue #953), which needs Pester 6.2 or later and is faster than breakpoint mode on the same coverage population. The PoshQC suites target PowerShell 7; profiler mode under Windows PowerShell 5.1 is not exercised in CI. To use breakpoint mode, pass a settings file with `UseBreakpoints = $true` through `-SettingsPath`.
   - When `-ScanFolders` is supplied to `Invoke-PoshQCSuite` or the lower-level commands, the suite narrows discovery to those workspace-relative or workspace-contained folders.
 - Coverage population (issue #527): `Invoke-PoshQCTest` measures the same file set for the same workspace whichever module copy is loaded.
   - Workspace configuration: `config/poshqc-coverage.json` with the schema `{"version": 1, "roots": [...]}`. Each root is a workspace-relative folder. The file is validated fail-fast, and every error names `config/poshqc-coverage.json`: empty content, invalid JSON, a `version` other than 1, a missing or non-array `roots`, and a blank, absolute, or `..`-segment entry are rejected. An empty `roots` array yields an empty population.
@@ -98,7 +98,7 @@ PoshQC is a lightweight PowerShell quality gate that wraps Invoke-Formatter, PSS
   - A shard that selects no test file (more shards than test files) stops with an error before Pester runs.
   - `Merge-PoshQCCoverageReport` merges the shard reports with `ci = max(ci)` per line and recomputes the LINE and INSTRUCTION counters, so the merged LINE figures are exact. It omits `class` and `method` elements and METHOD and CLASS counters, because those cannot be recomputed from line hits.
 - Output-path parameters (issue #1048): `Invoke-PoshQCTest -TestResultPath <path> -CoverageOutputPath <path>` replace the JUnit and coverage output paths of the settings file for one invocation; a relative path is resolved against `-Root`. When a parameter is omitted or blank, the settings value is used.
-- Local concurrent runs (issue #1048): `Invoke-PoshQCParallelTest -Root . [-WorkerCount <n>]` runs the suite as concurrent shard processes on one machine. Pester 5 has no in-process parallel mode, so each shard is a separate `pwsh` process; the VS Code task `PoshQC: 4 test (Pester, parallel)` runs it.
+- Local concurrent runs (issue #1048): `Invoke-PoshQCParallelTest -Root . [-WorkerCount <n>]` runs the suite as concurrent shard processes on one machine. Each shard runs Pester 6 in a separate `pwsh` process; the VS Code task `PoshQC: 4 test (Pester, parallel)` runs it.
   - The worker count defaults to half the logical processor count, at least 1 and at most 8 (`Get-PoshQCParallelWorkerCount`); `-WorkerCount` overrides it.
   - Each shard runs `Invoke-PoshQCTest -ShardIndex <i> -ShardCount <N>` with its JUnit, coverage, and manifest files and its console log (`shard.log`, standard error in `shard.log.err`) under `artifacts/pester/parallel/shard-<i>/`.
   - After every shard has exited, the runner checks the manifests with `Test-PoshQCShardCompleteness`, merges the JUnit reports with `Merge-PoshQCJunitReport` and the coverage reports with `Merge-PoshQCCoverageReport`, and writes `artifacts/pester/pester-junit.xml`, `artifacts/pester/powershell-coverage.xml`, and the `powershell-coverage.koverage.xml` copy.
@@ -109,7 +109,7 @@ PoshQC is a lightweight PowerShell quality gate that wraps Invoke-Formatter, PSS
 
 - Day-to-day: run `Invoke-PoshQCFormat`, `Invoke-PoshQCAnalyze`, then `Invoke-PoshQCTest` before committing.
 - Bundled / scoped: run `Invoke-PoshQCSuite -Root . -ScanFolders @('scripts', 'tests/powershell')` when you want the suite to focus on selected workspace folders.
-- CI: call `Invoke-PoshQCTest` to get tests + coverage and consume JUnit/CoverageGutters artifacts.
+- CI: call `Invoke-PoshQCTest` to get tests + coverage and consume JUnit/JaCoCo artifacts.
 
 ## Notes for standalone use
 

package/resources/powershell/PoshQC/settings/pester.runsettings.psd1

@@ -16,9 +16,9 @@
     }
     CodeCoverage = @{
         Enabled               = $true
-        # Use Pester's CoverageGutters format so VS Code Coverage Gutters
+        # Use Pester's JaCoCo format so VS Code Coverage Gutters
         # can map file paths correctly.
-        OutputFormat          = 'CoverageGutters'
+        OutputFormat          = 'JaCoCo'
         OutputPath            = 'artifacts/pester/powershell-coverage.xml'
         # Issue #527: no Path list. Invoke-PoshQCTest derives the coverage population from the
         # workspace (config/poshqc-coverage.json, else the effective test scan folders); see README.md.

package/resources/templates/policy_audit/AGENTS.md

@@ -42,9 +42,8 @@ When performing a policy audit:
 When asked to perform a Policy Audit for a component, branch, or PR:
 
 1. **Identify scope**
-   - Determine what is being audited (e.g., "fix-all.ps1 unit tests", "Lexile scoring pipeline refactor", "new Python module X").
+   - Determine what is being audited (e.g., "fix-all.ps1 unit tests", "scoring pipeline refactor", "new Python module X").
    - Identify the relevant code files and test files.
-   - **Document baseline coverage BEFORE making changes** (if development has not yet started, or shelve changes temporarily to establish baseline).
 
 2. **Create an audit document**
    - Generate a timestamp in ISO-8601 format `yyyy-MM-ddTHH-mm` (e.g., "2026-01-08T14-30" for Jan 8, 2026 at 2:30 PM).
@@ -57,7 +56,7 @@ When asked to perform a Policy Audit for a component, branch, or PR:
      - Fill in the Coverage Metrics by Language table with one row per language.
      - Complete all applicable language sections (3A, 3B, 3C, 3D for code; 4A, 4B for tests).
      - Delete sections for languages NOT involved in this change.
-   - **Fill in baseline coverage metrics** from pre-development measurement (per language that has coverage).
+   - Record each retained baseline field as `N/A - no pre-change run`.
    - Add one per-language comparison bullet for every in-scope language that has coverage requirements.
 
 3. **Evaluate policy compliance**
@@ -69,17 +68,17 @@ When asked to perform a Policy Audit for a component, branch, or PR:
      - Record **status** (`✅ PASS`, `⚠️ PARTIAL`, `❌ FAIL`, `N/A`) and **evidence** in the appropriate table rows.
    - **For multi-language changes:**
      - Run each language's toolchain separately and document results in its section.
-     - **Python:** Black → Ruff → Pyright → Pytest (with coverage)
-     - **PowerShell:** Invoke-PoshQCFormat → Invoke-PoshQCAnalyze → Invoke-PoshQCTest (with coverage)
+     - **Python:** Black → Ruff → Pyright → `poetry run pytest -n auto` (with coverage)
+     - **PowerShell:** Invoke-PoshQCFormat → Invoke-PoshQCAnalyze → Invoke-PoshQCParallelTest (with coverage)
      - **Bash:** shfmt → shellcheck → bats (coverage N/A)
      - **JSON:** format_json → validate_json (coverage N/A)
    - **For coverage metrics (Python and PowerShell only):**
-     - Compare post-change coverage to baseline to verify no regression (per language).
+     - Read each changed file from the single gate run and compare it with the coverage thresholds (per language).
      - Isolate and measure coverage of new/modified code only (must be ≥90% per language).
-     - Use concrete examples showing calculations: "Baseline: 85.2% → Post-change: 87.1% (+1.9%) ✅"
+     - Use concrete examples showing calculations: "Post-change: 87.1% against the 85% line threshold ✅"
    - **Fail-closed evidence handling:**
-     - No policy audit may report PASS unless it includes numeric baseline and post-change coverage metrics for every language in scope, plus changed/new-code coverage when required.
-     - If any required baseline artifact, QA artifact, or coverage-comparison artifact is missing, the verdict must be BLOCKED or INCOMPLETE, never PASS.
+     - No policy audit may report PASS unless it includes numeric post-change coverage metrics for every language in scope, plus changed/new-code coverage when required.
+     - If any required QA artifact or post-change coverage metric is missing, the verdict must be BLOCKED or INCOMPLETE, never PASS.
      - Do not synthesize or backfill missing audit evidence from memory or inference.
      - If evidence is missing, stop and report the exact missing artifact paths.
    - **For scenario testing:**
@@ -105,7 +104,7 @@ When asked to perform a Policy Audit for a component, branch, or PR:
 6. **Summarize and recommend**
    - Complete the summary sections at the end of the template:
      - Policy-by-policy summary
-     - Metrics summary (with deterministic baseline/post-change/new code coverage)
+     - Metrics summary (with deterministic post-change and new code coverage)
      - Recommendation (`Ready for merge`, `Needs revision`, or `Blocked`)
    - Ensure the final audit document is consistent with the underlying evidence and toolchain output.
 

package/resources/templates/policy_audit/policy-audit.yyyy-MM-ddTHH-mm.md

@@ -30,8 +30,8 @@
 
 | Language | Files Changed | Tests | Test Result | Baseline Coverage | Post-Change Coverage | New Code Coverage |
 |----------|--------------|-------|-------------|-------------------|---------------------|-------------------|
-| Python | [N] files | [N] tests | [✅/❌] [N] pass, [N] fail | [N]% lines, [N]% funcs | [N]% lines, [N]% funcs | [N]% |
-| PowerShell | [N] files | [N] tests | [✅/❌] [N] pass, [N] fail | [N]% cmds, [N]% funcs | [N]% cmds, [N]% funcs | [N]% |
+| Python | [N] files | [N] tests | [✅/❌] [N] pass, [N] fail | N/A - no pre-change run | [N]% lines, [N]% funcs | [N]% |
+| PowerShell | [N] files | [N] tests | [✅/❌] [N] pass, [N] fail | N/A - no pre-change run | [N]% cmds, [N]% funcs | [N]% |
 | Bash | [N] files | [N/A] tests | [✅/❌/N/A] | N/A (no coverage) | N/A (no coverage) | N/A |
 | JSON | [N] files | N/A | [✅/❌] validation | N/A (config files) | N/A (config files) | N/A |
 
@@ -39,15 +39,15 @@
 
 ### Coverage Evidence Checklist
 
-- TypeScript baseline coverage artifact: [path or `N/A - out of scope`]
+- TypeScript baseline coverage artifact: N/A - no pre-change run
 - TypeScript post-change coverage artifact: [path or `N/A - out of scope`]
-- PowerShell baseline coverage artifact: [path or `N/A - out of scope`]
+- PowerShell baseline coverage artifact: N/A - no pre-change run
 - PowerShell post-change coverage artifact: [path or `N/A - out of scope`]
 - Per-language comparison summary: [section reference or artifact path]
 
-**Non-negotiable verdict rule:** No policy audit may report PASS unless it includes numeric baseline and post-change coverage metrics for every language in scope, plus changed/new-code coverage when required.
+**Non-negotiable verdict rule:** No policy audit may report PASS unless it includes numeric post-change coverage metrics for every language in scope, plus changed/new-code coverage when required.
 
-**Fail-closed rule:** If any required baseline artifact, QA artifact, or coverage-comparison artifact is missing, the verdict must be BLOCKED or INCOMPLETE, never PASS.
+**Fail-closed rule:** If any required QA artifact or post-change coverage metric is missing, the verdict must be BLOCKED or INCOMPLETE, never PASS.
 
 **Evidence rule:** Do not synthesize or backfill missing audit evidence from memory or inference. If evidence is missing, stop and list the exact missing artifact paths.
 
@@ -94,8 +94,7 @@
 
 | Requirement | Status | Evidence |
 |------------|--------|----------|
-| **Baseline Coverage Documented** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Baseline (pre-development):** [N]% lines, [N]% functions<br>**Command:** `[coverage command]`<br>**Timestamp:** [YYYY-MM-DD HH:MM]<br>**Note:** Document baseline BEFORE making changes to avoid re-computation during audit. |
-| **No Coverage Regression** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Post-change coverage:** [N]% lines, [N]% functions<br>**Change:** [+/-N]% lines, [+/-N]% functions<br>**Status:** [No regression / Regression detected: justification]<br>**Example:** "Baseline: 85.2% → Post-change: 87.1% (+1.9%) ✅ PASS" |
+| **Changed Files Meet Thresholds** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Post-change coverage:** [N]% lines, [N]% functions, read from the single gate run<br>**Thresholds:** [line and branch thresholds that apply]<br>**Status:** [All changed files meet the thresholds / Files below a threshold: list]<br>**Example:** "Post-change: 87.1% against the 85% line threshold ✅ PASS" |
 | **New Code Coverage ≥90%** | [✅/❌/N/A] [PASS/FAIL/N/A] | **New/modified files:** [list files]<br>**New code coverage:** [N]% (must be ≥90%)<br>**Calculation method:** [describe how new code was isolated for measurement]<br>**Example:** "New module `foo.py`: 127/135 lines covered = 94.1% ✅ PASS" |
 | **Comprehensive Coverage** | [✅/❌/N/A] [PASS/FAIL/N/A] | **All functions/classes tested:**<br>- `function_name()` (lines X-Y): [N] tests<br>- `ClassName` (lines A-B): [N] tests<br>**Untested code:** [list with justification]<br>**Example:**<br>- `parse_config()` (lines 45-67): 3 tests<br>- `ConfigLoader` (lines 100-150): 5 tests<br>- Untested: `__repr__()` (trivial representation, no business logic) |
 | **Positive Flows** - Valid inputs | [✅/❌/N/A] [PASS/FAIL/N/A] | **All positive scenarios tested:**<br>- `test_function_with_valid_string`: Tests normal string input → returns expected output<br>- `test_function_with_valid_number`: Tests numeric input in valid range → performs calculation<br>- `test_function_with_default_params`: Tests function with default parameters → uses correct defaults<br>**Total positive tests:** [N] |
@@ -109,7 +108,7 @@
 
 Repeat one bullet per in-scope language that has coverage requirements. Keep the checklist above even when a language is out of scope, but use `N/A - out of scope` for the artifact path.
 
-- [Language]: Baseline: [N]% [unit] -> Post-change: [N]% [unit]. Change: [+/-N]% [unit delta]. New/changed-code coverage: [N]% or `N/A - out of scope`. Disposition: [PASS/FAIL/N/A]. Evidence: [artifact path(s)].
+- [Language]: Baseline: N/A - no pre-change run -> Post-change: [N]% [unit]. Change: N/A. New/changed-code coverage: [N]% or `N/A - out of scope`. Disposition: [PASS/FAIL/N/A]. Evidence: [artifact path(s)].
 
 ### 1.3 Test Structure and Diagnostics
 
@@ -208,7 +207,7 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 | **Formatting with Black** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run black .`<br>**Result:** [Describe result] |
 | **Linting with Ruff** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run ruff check`<br>**Result:** [Describe result] |
 | **Type checking with Pyright** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run pyright`<br>**Result:** [Describe result] |
-| **Testing with Pytest** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run pytest`<br>**Result:** [Describe result] |
+| **Testing with Pytest** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run pytest -n auto`<br>**Result:** [Describe result] |
 
 #### 3A.2 Python Design & Typing
 
@@ -342,7 +341,7 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 
 | Requirement | Status | Evidence |
 |------------|--------|----------|
-| **Use Pytest** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run pytest`<br>**Result:** [Describe test results] |
+| **Use Pytest** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run pytest -n auto`<br>**Result:** [Describe test results] |
 | **No Alternative Test Runners** | [✅/❌/N/A] [PASS/FAIL/N/A] | [Confirm only Pytest is used.] |
 
 ---
@@ -353,8 +352,8 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 
 | Requirement | Status | Evidence |
 |------------|--------|----------|
-| **Use Pester v5.x** | [✅/❌/N/A] [PASS/FAIL/N/A] | [Describe Pester v5 features used (BeforeAll, BeforeEach, Describe/Context/It, modern Should syntax).] |
-| **Use PoshQC Configuration** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `Invoke-PoshQCTest -Root .`<br>**Config:** `scripts/powershell/PoshQC/settings/pester.runsettings.psd1`<br>[Describe configuration updates if any.] |
+| **Use Pester v6.x** | [✅/❌/N/A] [PASS/FAIL/N/A] | [Describe Pester v6 features used (BeforeAll, BeforeEach, Describe/Context/It, modern Should syntax).] |
+| **Use PoshQC Configuration** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `Invoke-PoshQCParallelTest -Root .`<br>**Config:** `scripts/powershell/PoshQC/settings/pester.runsettings.psd1`<br>[Describe configuration updates if any.] |
 | **PowerShell 5.1 & 7.6+ Compatible** | [✅/❌/N/A] [PASS/FAIL/N/A] | [Describe compatibility testing. Note any version-specific features.] |
 
 #### 4B.2 Test Style and Structure
@@ -379,7 +378,7 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 
 | Requirement | Status | Evidence |
 |------------|--------|----------|
-| **Use PoshQCTest Command** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `Invoke-PoshQCTest -Root .`<br>**Result:** [Describe test results] |
+| **Use PoshQCTest Command** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `Invoke-PoshQCParallelTest -Root .`<br>**Result:** [Describe test results] |
 | **No Alternative Test Runners** | [✅/❌/N/A] [PASS/FAIL/N/A] | [Confirm only Pester is used through PoshQC.] |
 
 ---
@@ -438,7 +437,7 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 | Black Formatting | `poetry run black .` | [result] | [✅/❌] |
 | Ruff Linting | `poetry run ruff check` | [result] | [✅/❌] |
 | Pyright Type Checking | `poetry run pyright` | [result] | [✅/❌] |
-| Pytest Tests | `poetry run pytest` | [result] | [✅/❌] |
+| Pytest Tests | `poetry run pytest -n auto` | [result] | [✅/❌] |
 
 **For PowerShell:**
 
@@ -446,7 +445,7 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 |-------|---------|--------|--------|
 | Invoke-Formatter | `Invoke-PoshQCFormat -Root .` | [result] | [✅/❌] |
 | PSScriptAnalyzer | `Invoke-PoshQCAnalyze -Root .` | [result] | [✅/❌] |
-| Pester Tests | `Invoke-PoshQCTest -Root .` | [result] | [✅/❌] |
+| Pester Tests | `Invoke-PoshQCParallelTest -Root .` | [result] | [✅/❌] |
 
 **Notes:**
 [Document any pre-existing failures unrelated to this work. Explain any deviations from clean runs.]
@@ -515,7 +514,7 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 
 [Provide a brief summary of overall compliance status and any major findings.]
 
-**Fail-closed reminder:** Do not mark the audit PASS, fully compliant, or ready for merge when any required baseline artifact, QA artifact, coverage metric, or coverage-comparison artifact is missing.
+**Fail-closed reminder:** Do not mark the audit PASS, fully compliant, or ready for merge when any required QA artifact or post-change coverage metric is missing.
 
 ---
 
@@ -626,8 +625,8 @@ poetry run ruff check --fix  # auto-fix
 poetry run pyright
 
 # Testing
-poetry run pytest
-poetry run pytest --cov=src/[package] --cov-report=term-missing
+poetry run pytest -n auto
+poetry run pytest -n auto --cov=src/[package] --cov-report=term-missing
 ```
 
 **For PowerShell:**
@@ -639,7 +638,7 @@ Import-Module ./scripts/powershell/PoshQC; Invoke-PoshQCFormat -Root .
 Import-Module ./scripts/powershell/PoshQC; Invoke-PoshQCAnalyze -Root .
 
 # Testing
-Import-Module ./scripts/powershell/PoshQC; Invoke-PoshQCTest -Root .
+Import-Module ./scripts/powershell/PoshQC; Invoke-PoshQCParallelTest -Root .
 ```
 
 ---