@danmoisan/drm-copilot-mcp 1.0.16 → 1.0.18

package/resources/claude-customizations/.claude/skills/discovery-parity-matrix/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: discovery-parity-matrix
+description: 'Produce or refresh the parity matrix in the discovery workflow. Use when building the parity matrix from feature contracts and runtime characterization evidence and routing parity reasoning to the parity role. Fifth stage, after runtime characterization and before behavior reconciliation.'
+---
+
+# Discovery Parity Matrix
+
+Runs the parity stage of the discovery and parity-definition workflow. It
+produces or refreshes the parity matrix by comparing the feature contracts
+against the runtime characterization scenarios, so the workflow can measure how
+closely the modern target reproduces the legacy behavior. All domain specificity
+is read from the domain profile at runtime.
+
+## When to Use This Skill
+
+- Feature contracts and runtime characterization scenarios both exist.
+- You need a current parity matrix before reconciling unspecified behavior.
+
+## Prerequisites
+
+- `discovery-coverage-ledger` and `discovery-runtime-characterization` have
+  completed.
+- The domain profile is loaded and valid.
+
+## Workflow
+
+1. **Consume upstream artifacts.** Read the feature contracts (schema
+   `schemas/discovery/v1/feature-contract.schema.json`) and the runtime
+   characterization scenarios (schema
+   `schemas/discovery/v1/runtime-characterization-scenario.schema.json`).
+
+2. **Produce or refresh the parity matrix.** Build the parity matrix conforming
+   to the schema `schemas/discovery/v1/parity-matrix.schema.json`, mapping each
+   feature contract to its characterized behavior and its current parity state.
+   When the matrix already exists, refresh it in place from the latest upstream
+   artifacts.
+
+3. **Route parity reasoning.** Hand the matrix to the parity role for reasoning
+   about gaps and states (see `## Worker Routing`).
+
+## Worker Routing
+
+- Worker: `legacy-parity-analyst`
+
+The parity role reasons about each parity-matrix entry, classifying parity state
+and flagging gaps for behavior reconciliation.
+
+## Validation
+
+- Validate the parity matrix with `dev.discovery.validate-parity-matrix`.
+- An empty error list is a pass. On any error, follow the direction in
+  `discovery-validate-artifacts`.
+
+## Referenced Skills
+
+- `discovery-workflow` — stage order and the canonical Referenced Contracts
+  registry.
+- `discovery-validate-artifacts` — pass/fail semantics and error routing.
+
+## Notes
+
+- Parity gaps flagged here are the primary input to
+  `discovery-behavior-reconciliation`.

package/resources/claude-customizations/.claude/skills/discovery-repo-inventory/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: discovery-repo-inventory
+description: 'Drive the language-neutral repository and project inventory analyzer for the discovery workflow. Use when running the inventory stage against the domain profile source and target roots, recording analyzer outputs under the profile artifacts root, and running stack-specific analyzers generically per the profile technology stack. Second stage after profile load.'
+allowed-tools: Bash Read Glob Grep
+---
+
+# Discovery Repo Inventory
+
+Runs the inventory stage of the discovery and parity-definition workflow. It
+drives the language-neutral repository/project inventory analyzer against the
+roots declared in the domain profile, records outputs under the profile's
+artifact root, and then runs any stack-specific analyzers generically, without
+naming any concrete technology. All domain specificity is read from the domain
+profile at runtime.
+
+## When to Use This Skill
+
+- You have loaded the domain profile and are ready to inventory the legacy
+  source and the modern target.
+- You need analyzer outputs recorded as evidence for the coverage stage.
+
+## Prerequisites
+
+- The domain profile loads via `dev.discovery.profile`.
+- The analyzer framework CLI is available (referenced by name only; the full
+  registry lives in `discovery-workflow`).
+
+## Workflow
+
+1. **Load the domain profile.** Run `dev.discovery.profile` to load and echo the
+   consumer repository's `discovery-profile.yaml`. Read the following keys and
+   use them for every subsequent step; do not hard-code any of them:
+   - `legacy_source.root` — the legacy application source root.
+   - `target.root` — the modern target root.
+   - `artifacts.root` — where analyzer outputs and discovery artifacts are
+     recorded.
+   - `technology_stack` — the declared stack, used to select stack-specific
+     analyzers generically.
+
+2. **Run the language-neutral inventory analyzer.** Drive the inventory command
+   (assumed `dev.discovery.inventory`; see the fan-in note below) against
+   `legacy_source.root` and `target.root`. Record all outputs under
+   `artifacts.root` following the profile's artifact conventions.
+
+   **Fan-in reconciliation assumption:** the inventory command name
+   `dev.discovery.inventory` is assumed and may be renamed when the analyzer
+   framework (epic #9006) lands. The canonical registry entry and this fragment
+   are the only two locations to reconcile; the canonical entry lives in
+   `discovery-workflow`.
+
+3. **Run stack-specific analyzers generically.** For the declared
+   `technology_stack`, run any stack-specific analyzer commands documented by the
+   analyzer framework. Do not name a concrete analyzer or technology here; the
+   profile's `technology_stack` value selects the applicable analyzers at
+   runtime. Record their outputs under `artifacts.root` as well.
+
+4. **Record evidence references.** Capture each analyzer output as an
+   evidence-reference instance so downstream stages can cite provenance.
+
+## Validation
+
+- Before the inventory stage begins, confirm the profile is valid with
+  `dev.discovery.validate-profile`.
+- After recording evidence references, validate them with
+  `dev.discovery.validate-evidence-reference`.
+- An empty error list is a pass. On any error, follow the direction in
+  `discovery-validate-artifacts`, which owns the canonical validation-gate
+  mechanics.
+
+## Referenced Skills
+
+- `discovery-workflow` — stage order and the canonical Referenced Contracts
+  registry (analyzer command, agent slugs, schema paths, validators).
+- `discovery-validate-artifacts` — pass/fail semantics and error routing.
+
+## Notes
+
+- This skill introduces no domain-specific identifier. Source root, target root,
+  artifact root, and stack are all read from the domain profile at runtime.
+- Outputs from this stage feed `discovery-coverage-ledger`.

package/resources/claude-customizations/.claude/skills/discovery-runtime-characterization/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: discovery-runtime-characterization
+description: 'Produce runtime characterization scenarios and evidence references in the discovery workflow. Use when characterizing observed runtime behavior of the legacy application into scenarios with supporting evidence and routing analysis to the runtime role. Fourth stage, after coverage and before parity.'
+---
+
+# Discovery Runtime Characterization
+
+Runs the runtime characterization stage of the discovery and parity-definition
+workflow. It captures observed runtime behavior of the legacy application as
+characterization scenarios, each backed by evidence references, so that parity
+analysis can compare intended contracts against observed behavior. All domain
+specificity is read from the domain profile at runtime.
+
+## When to Use This Skill
+
+- Feature contracts and the coverage ledger exist from the coverage stage.
+- You need documented runtime behavior scenarios before building the parity
+  matrix.
+
+## Prerequisites
+
+- `discovery-coverage-ledger` has completed.
+- The domain profile is loaded and valid.
+
+## Workflow
+
+1. **Produce characterization scenarios.** For each behavior requiring runtime
+   observation, produce a scenario conforming to the schema
+   `schemas/discovery/v1/runtime-characterization-scenario.schema.json`. Each
+   scenario records the observed runtime behavior in a domain-neutral form.
+
+2. **Record evidence references.** Attach evidence to each scenario as
+   evidence-reference instances conforming to the schema
+   `schemas/discovery/v1/evidence-reference.schema.json`, so the provenance of
+   each observation is traceable.
+
+3. **Route analysis.** Hand the scenarios to the runtime role for analysis (see
+   `## Worker Routing`).
+
+## Worker Routing
+
+- Worker: `runtime-characterization-analyst`
+
+The runtime role analyzes and confirms each characterization scenario and its
+evidence before the workflow proceeds to parity.
+
+## Validation
+
+- Validate scenarios with `dev.discovery.validate-runtime-scenario`.
+- Validate evidence references with `dev.discovery.validate-evidence-reference`.
+- An empty error list is a pass. On any error, follow the direction in
+  `discovery-validate-artifacts`.
+
+## Referenced Skills
+
+- `discovery-workflow` — stage order and the canonical Referenced Contracts
+  registry.
+- `discovery-validate-artifacts` — pass/fail semantics and error routing.
+
+## Notes
+
+- Scenarios and evidence references from this stage are consumed by
+  `discovery-parity-matrix`.

package/resources/claude-customizations/.claude/skills/discovery-validate-artifacts/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: discovery-validate-artifacts
+description: 'Canonical validation-gate mechanics for the discovery workflow. Use when running the per-artifact discovery validators after each stage and the completion gate at the end, interpreting the empty-error-list pass semantics, and routing any validator error back to the owning stage skill. Seventh and final stage.'
+allowed-tools: Bash Read
+---
+
+# Discovery Validate Artifacts
+
+Owns the canonical validation-gate mechanics for the discovery and
+parity-definition workflow. Each discovery artifact is validated against its
+schema by a `dev.discovery.validate-*` console script after its owning stage,
+and `dev.discovery.validate-all` runs as the workflow completion gate. This skill
+is the single canonical location for the pass/fail semantics; stage skills defer
+to it by name.
+
+## When to Use This Skill
+
+- A stage has produced an artifact and you need to validate it before the next
+  stage proceeds.
+- You have completed all stages and need to run the workflow completion gate.
+- A validator reported errors and you need the routing rule back to the owning
+  stage skill.
+
+## Prerequisites
+
+- The relevant discovery artifacts exist under the profile's artifact root.
+- The validator console scripts are available (registry in `discovery-workflow`).
+
+## Pass/Fail Semantics
+
+Every `dev.discovery.validate-*` invocation yields a `list[str]` of error
+messages. An empty list is a pass; a non-empty list is a failure whose entries
+name the exact problems. The validators never mutate the artifacts they check.
+
+## Per-Stage Validators
+
+Run each validator after its owning stage produces its artifact. On a non-empty
+error list, return to the named owning stage skill, correct the artifact, and
+re-run the validator until the list is empty.
+
+| Validator | Validates schema | Owning stage skill |
+|---|---|---|
+| `dev.discovery.validate-profile` | (domain profile) | `discovery-repo-inventory` |
+| `dev.discovery.validate-evidence-reference` | `schemas/discovery/v1/evidence-reference.schema.json` | `discovery-repo-inventory`, `discovery-runtime-characterization` |
+| `dev.discovery.validate-feature-contract` | `schemas/discovery/v1/feature-contract.schema.json` | `discovery-coverage-ledger` |
+| `dev.discovery.validate-coverage-ledger` | `schemas/discovery/v1/coverage-ledger.schema.json` | `discovery-coverage-ledger` |
+| `dev.discovery.validate-runtime-scenario` | `schemas/discovery/v1/runtime-characterization-scenario.schema.json` | `discovery-runtime-characterization` |
+| `dev.discovery.validate-parity-matrix` | `schemas/discovery/v1/parity-matrix.schema.json` | `discovery-parity-matrix` |
+| `dev.discovery.validate-unspecified-behavior` | `schemas/discovery/v1/unspecified-behavior-record.schema.json` | `discovery-behavior-reconciliation` |
+| `dev.discovery.validate-product-decision` | `schemas/discovery/v1/product-decision-record.schema.json` | `discovery-behavior-reconciliation` |
+
+## Completion Gate
+
+After all stages pass their per-stage validators, run
+`dev.discovery.validate-all` as the workflow completion gate. It validates the
+full artifact set across all seven schemas under `schemas/discovery/v1/`:
+
+- `schemas/discovery/v1/feature-contract.schema.json`
+- `schemas/discovery/v1/coverage-ledger.schema.json`
+- `schemas/discovery/v1/runtime-characterization-scenario.schema.json`
+- `schemas/discovery/v1/parity-matrix.schema.json`
+- `schemas/discovery/v1/unspecified-behavior-record.schema.json`
+- `schemas/discovery/v1/product-decision-record.schema.json`
+- `schemas/discovery/v1/evidence-reference.schema.json`
+
+An empty error list from `dev.discovery.validate-all` means the workflow is
+complete. A non-empty list names the exact artifact and problem; route each entry
+back to its owning stage skill using the per-stage table above, correct the
+artifact, and re-run the gate.
+
+## Referenced Skills
+
+- `discovery-workflow` — stage order and the canonical Referenced Contracts
+  registry (analyzer command, agent slugs, schema paths, validators).
+
+## Notes
+
+- This skill names no domain-specific identifier; artifact locations are read
+  from the domain profile at runtime.

package/resources/claude-customizations/.claude/skills/discovery-workflow/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: discovery-workflow
+description: 'Umbrella sequencing skill for the domain-neutral legacy discovery and parity-definition workflow. Use when onboarding or running the end-to-end discovery workflow across inventory, coverage, runtime characterization, parity, behavior reconciliation, and the validation gate, and when reconciling upstream analyzer and agent contract names. Holds the canonical Referenced Contracts registry.'
+---
+
+# Discovery Workflow
+
+Sequences the reusable, domain-neutral discovery and parity-definition workflow
+end to end. This skill is the entry point: it establishes the stage order,
+directs each stage to its owning skill, and holds the single canonical registry
+of upstream contract names (analyzer CLI commands, agent slugs, schema paths,
+and validators).
+
+All domain specificity is read at runtime from the consumer repository's domain
+profile (`discovery-profile.yaml`) via `dev.discovery.profile`. This skill names
+no concrete repository, path, or technology stack.
+
+## When to Use This Skill
+
+- You are onboarding the discovery and parity-definition workflow in a consumer
+  repository and need the documented stage order.
+- You need the canonical list of upstream contract names to reconcile a renamed
+  analyzer command or agent slug at epic fan-in.
+- You need to know which stage skill owns which artifact and validator.
+
+## Prerequisites
+
+- A `discovery-profile.yaml` domain profile exists in the consumer repository and
+  loads cleanly via `dev.discovery.profile`.
+- The analyzer framework CLI and the four generic agent roles are available in
+  the consumer environment (referenced here by name only).
+
+## Stage Order
+
+Run the workflow in this fixed order. Each stage validates its artifacts before
+the next stage proceeds:
+
+1. **profile** — load and echo the domain profile via `dev.discovery.profile`.
+2. **inventory** — drive the language-neutral repository/project inventory
+   analyzer (`discovery-repo-inventory`).
+3. **coverage** — produce feature contracts and the coverage ledger
+   (`discovery-coverage-ledger`).
+4. **runtime** — produce runtime characterization scenarios and evidence
+   references (`discovery-runtime-characterization`).
+5. **parity** — produce or refresh the parity matrix (`discovery-parity-matrix`).
+6. **reconciliation** — capture unspecified or contradictory behavior and
+   reconcile it into product decisions (`discovery-behavior-reconciliation`).
+7. **validation gate** — run the per-stage validators and the completion gate
+   (`discovery-validate-artifacts`).
+
+Compact form: profile -> inventory -> coverage -> runtime -> parity ->
+reconciliation -> validation gate.
+
+## Worker Routing
+
+The four generic agent roles are routed by slug from their owning stage skills.
+The routing table below is the canonical mapping; each stage skill repeats only
+the single slug it routes to.
+
+| Stage skill | Agent slug |
+|---|---|
+| `discovery-coverage-ledger` | `migration-coverage-reviewer` |
+| `discovery-runtime-characterization` | `runtime-characterization-analyst` |
+| `discovery-parity-matrix` | `legacy-parity-analyst` |
+| `discovery-behavior-reconciliation` | `requirements-reconciler` |
+
+## Referenced Contracts
+
+This registry is the single canonical location for upstream contract names.
+Stage skills name only the specific contract(s) they use and defer to this
+registry for the full set. Indirect reference by skill name is not duplication.
+
+### Domain profile (config contract, issue #360 / epic #9001)
+
+- Config artifact: `discovery-profile.yaml`.
+- CLI: `dev.discovery.profile`.
+
+### Schemas (issue #359 / epic #9002)
+
+Seven schemas under `schemas/discovery/v1/`:
+
+- `schemas/discovery/v1/feature-contract.schema.json`
+- `schemas/discovery/v1/coverage-ledger.schema.json`
+- `schemas/discovery/v1/runtime-characterization-scenario.schema.json`
+- `schemas/discovery/v1/parity-matrix.schema.json`
+- `schemas/discovery/v1/unspecified-behavior-record.schema.json`
+- `schemas/discovery/v1/product-decision-record.schema.json`
+- `schemas/discovery/v1/evidence-reference.schema.json`
+
+### Validators (issue #361 / epic #9003)
+
+Nine `dev.discovery.validate-*` console scripts. Each yields a `list[str]` of
+errors; an empty list is a pass.
+
+- `dev.discovery.validate-profile`
+- `dev.discovery.validate-feature-contract`
+- `dev.discovery.validate-coverage-ledger`
+- `dev.discovery.validate-runtime-scenario`
+- `dev.discovery.validate-parity-matrix`
+- `dev.discovery.validate-unspecified-behavior`
+- `dev.discovery.validate-product-decision`
+- `dev.discovery.validate-evidence-reference`
+- `dev.discovery.validate-all`
+
+### Analyzer framework (epic #9006, in preparation)
+
+- Language-neutral repository/project inventory command: `dev.discovery.inventory`.
+
+  **Fan-in reconciliation assumption:** the inventory command name
+  `dev.discovery.inventory` is assumed. It is not fixed by the prepared upstream
+  summaries and is the epic #9006 owner's decision. This assumption is isolated
+  to this single registry line plus one fragment in `discovery-repo-inventory`.
+  If #9006 lands a different command name, update those two locations only.
+
+### Agent roles (epic #9007, in preparation)
+
+Four generic agent personas, referenced by slug in the Worker Routing table
+above:
+
+- `legacy-parity-analyst`
+- `runtime-characterization-analyst`
+- `requirements-reconciler`
+- `migration-coverage-reviewer`
+
+  **Fan-in reconciliation assumption:** the four agent slugs are assumed to be
+  the kebab-case of the persona titles. Final slugs are the epic #9007 owner's
+  decision. The assumption is isolated to this registry and the per-stage
+  `## Worker Routing` fragments; reconciling a renamed slug at fan-in is a
+  bounded edit.
+
+## Referenced Skills
+
+- `discovery-repo-inventory` — inventory stage mechanics.
+- `discovery-coverage-ledger` — coverage stage mechanics.
+- `discovery-runtime-characterization` — runtime stage mechanics.
+- `discovery-parity-matrix` — parity stage mechanics.
+- `discovery-behavior-reconciliation` — reconciliation stage mechanics.
+- `discovery-validate-artifacts` — canonical validation-gate mechanics.
+
+## Notes
+
+- No skill in this workflow asserts the existence of upstream analyzer or agent
+  files; upstream contracts are referenced by name only, so this workflow stays
+  correct regardless of upstream merge order.
+- Domain specificity (source and target roots, technology stack, artifact
+  conventions) is read from the domain profile at runtime, never hard-coded.

package/resources/claude-customizations/.claude/skills/execute-hard-lock/SKILL.md

@@ -34,7 +34,7 @@ Call the extension's resolver as the first action:
 - Tool: `mcp__drm-copilot__resolve_execute_hard_lock_prompt`
 - Parameters:
   - `target` (required): the plan-of-record path (`${plan-path}`).
-  - `workspace_root` (optional): the workspace root. Omit to default to the current working directory.
+  - `workspace_root` (required): the absolute root of the calling agent's checkout or worktree. The MCP server cannot infer the caller's checkout, so this value must be passed explicitly.
 
 On success, the response contains an `artifacts` array whose first entry is the absolute path of a file containing the resolved hard-lock prompt (produced by the extension passing `--output` and `--quiet` to the bundled Python resolver).
 

package/resources/claude-customizations/pack-manifests/core.json

@@ -11,13 +11,18 @@
     ".claude/agents/epic-review.md",
     ".claude/agents/feature-review.md",
     ".claude/agents/human-exception-runbook.md",
+    ".claude/agents/legacy-parity-analyst.md",
+    ".claude/agents/migration-coverage-reviewer.md",
     ".claude/agents/orchestrator.md",
     ".claude/agents/prd-feature.md",
+    ".claude/agents/requirements-reconciler.md",
+    ".claude/agents/runtime-characterization-analyst.md",
     ".claude/agents/staged-review.md",
     ".claude/agents/status-updater.md",
     ".claude/agents/task-researcher.md",
     ".claude/hooks/enforce-checkpoint-monotonic.ps1",
     ".claude/hooks/enforce-completion-consistency.ps1",
+    ".claude/hooks/enforce-discovery-artifact-gate.ps1",
     ".claude/hooks/enforce-epic-invocation-origin.ps1",
     ".claude/hooks/enforce-epic-merge-gate.ps1",
     ".claude/hooks/enforce-epic-wave-barrier.ps1",
@@ -32,6 +37,7 @@
     ".claude/hooks/enforce-promotion-mcp-only.ps1",
     ".claude/hooks/persist-session-id.ps1",
     ".claude/hooks/validate-bash.ps1",
+    ".claude/hooks/validate-discovery-artifact-gate.ps1",
     ".claude/hooks/validate-executor-output.ps1",
     ".claude/hooks/validate-feature-review-coverage.ps1",
     ".claude/hooks/validate-orchestrator-output.ps1",
@@ -49,7 +55,15 @@
     ".claude/rules/tonality.md",
     ".claude/skills/acceptance-criteria-tracking/SKILL.md",
     ".claude/skills/atomic-plan-contract/SKILL.md",
+    ".claude/skills/cleanup-merged-worktrees/SKILL.md",
     ".claude/skills/commit-message/SKILL.md",
+    ".claude/skills/discovery-behavior-reconciliation/SKILL.md",
+    ".claude/skills/discovery-coverage-ledger/SKILL.md",
+    ".claude/skills/discovery-parity-matrix/SKILL.md",
+    ".claude/skills/discovery-repo-inventory/SKILL.md",
+    ".claude/skills/discovery-runtime-characterization/SKILL.md",
+    ".claude/skills/discovery-validate-artifacts/SKILL.md",
+    ".claude/skills/discovery-workflow/SKILL.md",
     ".claude/skills/epic-orchestrate/SKILL.md",
     ".claude/skills/epic-plan/SKILL.md",
     ".claude/skills/epic-run/SKILL.md",

package/resources/codex-and-agents-customizations/.agents/skills/execute-hard-lock/SKILL.md

@@ -31,7 +31,7 @@ Call the extension's resolver as the first action:
 - Tool: `mcp__drm-copilot__resolve_execute_hard_lock_prompt`
 - Parameters:
   - `target` (required): the plan-of-record path (`${plan-path}`).
-  - `workspace_root` (optional): the workspace root. Omit to default to the current working directory.
+  - `workspace_root` (required): the absolute root of the calling agent's checkout or worktree. The MCP server cannot infer the caller's checkout, so this value must be passed explicitly.
 
 On success, the response contains an `artifacts` array whose first entry is the absolute path of a file containing the resolved hard-lock prompt (produced by the extension passing `--output` and `--quiet` to the bundled Python resolver).
 

package/resources/codex-and-agents-customizations/.codex/config.toml

@@ -2,7 +2,7 @@ default_permissions = ":danger-full-access"
 
 [mcp_servers.drm-copilot]
 command = "npx"
-args = ["-y", "@danmoisan/drm-copilot-mcp@1.0.16"]
+args = ["-y", "@danmoisan/drm-copilot-mcp@1.0.18"]
 required = true
 enabled_tools = [
     "collect_commit_context",

package/resources/config/orchestration-routing.json

@@ -44,9 +44,7 @@
       ],
       "required_skills": [
         "orchestrate",
-        "orchestrator-workflow",
         "feature-promotion-lifecycle",
-        "repo-automation-adapter",
         "atomic-plan-contract",
         "acceptance-criteria-tracking",
         "pr-context-artifacts",

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

@@ -160,7 +160,9 @@ function Invoke-PoshQCTest {
         [scriptblock] $EnsureModule = {
             param([string] $Name, [string] $ErrorMessage)
             if (-not (Get-Module -ListAvailable -Name $Name)) { throw $ErrorMessage }
-            Import-Module $Name -ErrorAction Stop
+            # 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-Module $Name -Global -ErrorAction Stop
         },
         [scriptblock] $TestPathExists = { param([string] $Path) Test-Path $Path },
         [scriptblock] $LoadSettings = { param([string] $Path) Import-PowerShellDataFile -Path $Path },
@@ -256,7 +258,27 @@ function Invoke-PoshQCTest {
             # Use Write-Information so the replayed summary stays visible while respecting approved verbs.
             Write-Information $Message -InformationAction Continue
         },
-        [scriptblock] $InvokePester = { param($Config) Invoke-Pester -Configuration $Config },
+        [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.
+            $trampoline = [scriptblock]::Create('param($c) Invoke-Pester -Configuration $c')
+            $null = New-Item -Path 'function:global:Invoke-PoshQCPesterRun' -Value $trampoline -Force
+            try {
+                Invoke-PoshQCPesterRun $Config
+            } finally {
+                # Remove by the 'Function:\' provider path; a 'function:global:'-qualified path
+                # is honored by New-Item but silently no-ops on Remove-Item, which would leak the
+                # trampoline between suite invocations in a persistent host (issue #392).
+                Remove-Item -Path 'Function:\Invoke-PoshQCPesterRun' -Force -ErrorAction SilentlyContinue
+            }
+        },
         [scriptblock] $CopyCoverage = {
             param([string] $CoveragePath, [string] $RepoRoot, [string] $KoveragePath)
             Convert-PoshQCCoverageToRelative -InputPath $CoveragePath -OutputPath $KoveragePath -RepoRoot $RepoRoot

package/resources/powershell/PoshQC/PoshQC.psm1

@@ -89,6 +89,27 @@ function Install-PoshQCTool {
 # [scriptblock]::Create((Get-Content -Raw)) approach produced scriptblocks with
 # no source file, so breakpoints never bound and PoshQC.ScanConfig.psm1 fell
 # outside the coverage denominator.  Parse errors fail module import fast.
+#
+# issue #392 remediation cycle 2: re-parsing and re-compiling a fresh ScriptBlock
+# for each sub-module on every Import-Module -Force made Pester's code-coverage
+# merge lose already-recorded hit credit for previously covered lines of the
+# re-compiled files (per-file LINE coverage of PoshQC.Testing.psm1 regressed from
+# 149/195 to 131/195 across a bundled run).  To avoid that re-parse/re-compile
+# churn, the parsed ScriptBlock for each sub-module is cached in a process-lifetime
+# AppDomain data slot keyed by absolute path, so ParseFile/GetScriptBlock runs at
+# most once per sub-module per PowerShell process.  Dot-sourcing still runs on
+# every -Force reimport, so functions rebind into each new module session state and
+# the test module-collision guards keep detecting/removing a mismatched instance.
+# The AppDomain slot (not a $global: variable, which PSAvoidGlobalVars forbids)
+# provides the process-lifetime persistence that -Force (which discards the
+# module's own script scope each time) does not.  A cache-miss parse error still
+# fails module import fast.
+$script:PoshQCSubModuleCacheKey = 'PoshQC.ParsedSubModuleScriptBlocks'
+$subModuleCache = [System.AppDomain]::CurrentDomain.GetData($script:PoshQCSubModuleCacheKey)
+if (-not $subModuleCache) {
+    $subModuleCache = @{}
+    [System.AppDomain]::CurrentDomain.SetData($script:PoshQCSubModuleCacheKey, $subModuleCache)
+}
 foreach ($subModuleName in @(
         'PoshQC.FileDiscovery.psm1',
         'PoshQC.ScanConfig.psm1',
@@ -96,13 +117,18 @@ foreach ($subModuleName in @(
         'PoshQC.Testing.psm1'
     )) {
     $subModulePath = Join-Path $script:ModuleRoot $subModuleName
-    $parseErrors = $null
-    $ast = [System.Management.Automation.Language.Parser]::ParseFile(
-        $subModulePath, [ref]$null, [ref]$parseErrors)
-    if ($parseErrors) {
-        throw "Failed to parse sub-module '$subModuleName': $($parseErrors -join '; ')"
+    $cachedScriptBlock = $subModuleCache[$subModulePath]
+    if (-not $cachedScriptBlock) {
+        $parseErrors = $null
+        $ast = [System.Management.Automation.Language.Parser]::ParseFile(
+            $subModulePath, [ref]$null, [ref]$parseErrors)
+        if ($parseErrors) {
+            throw "Failed to parse sub-module '$subModuleName': $($parseErrors -join '; ')"
+        }
+        $cachedScriptBlock = $ast.GetScriptBlock()
+        $subModuleCache[$subModulePath] = $cachedScriptBlock
     }
-    . ($ast.GetScriptBlock())
+    . $cachedScriptBlock
 }
 
 Set-Alias -Name Install-PoshQCTools -Value Install-PoshQCTool

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

@@ -82,6 +82,19 @@
             # to AST-based scriptblocks (Parser::ParseFile(...).GetScriptBlock()) so Pester
             # coverage breakpoints bind to the on-disk source file.
             'scripts/powershell/PoshQC/PoshQC.ScanConfig.psm1'
+            # Issue #357 remediation cycle 1 (fix #1): measure the atomic-planner SubagentStop
+            # hook so its Pester coverage is captured in the canonical artifact.
+            '.claude/hooks/validate-planner-output.ps1'
+            # Issue #366 added the discovery-artifact completion-gate hooks (PreToolUse and
+            # SubagentStop); measured here so the new production hooks are not excluded from
+            # coverage.
+            '.claude/hooks/enforce-discovery-artifact-gate.ps1'
+            '.claude/hooks/validate-discovery-artifact-gate.ps1'
+            # Issue #392 changed the Invoke-PoshQCTest default seams ($EnsureModule -Global
+            # import and the global-session-state $InvokePester trampoline) so the bundled
+            # entry path hosts the Pester run in the global session state; measured here so
+            # the fix produces real per-file changed-line coverage evidence.
+            'scripts/powershell/PoshQC/PoshQC.Testing.psm1'
         )
         # Optional: don't fail the run on coverage percentage
         CoveragePercentTarget = 0

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

@@ -275,9 +275,9 @@ Repeat one bullet per in-scope language that has coverage requirements. Keep the
 
 | Requirement | Status | Evidence |
 |------------|--------|----------|
-| **Formatting with shfmt** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run shell-qc format`<br>**Result:** [Describe result] |
-| **Linting with shellcheck** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run shell-qc check`<br>**Result:** [Describe result] |
-| **Testing with bats** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `poetry run shell-qc test`<br>**Result:** [Describe result or N/A if no tests] |
+| **Formatting with shfmt** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `bash scripts/bash/shell-qc.sh format`<br>**Result:** [Describe result] |
+| **Linting with shellcheck** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `bash scripts/bash/shell-qc.sh check`<br>**Result:** [Describe result] |
+| **Testing with bats** | [✅/❌/N/A] [PASS/FAIL/N/A] | **Command:** `bash scripts/bash/shell-qc.sh test`<br>**Result:** [Describe result or N/A if no tests] |
 
 #### 3C.2 Bash Script Design