@danmoisan/drm-copilot-mcp 1.0.24 → 1.0.27

package/resources/codex-and-agents-customizations/.agents/skills/quality-tiers/SKILL.md

@@ -27,7 +27,7 @@ This rule defines the T1–T4 module rigor tier system used by all CI gates in t
 
 ## Uniform-vs-Tier-Dependent Gate Matrix
 
-Per Authoritative Decision #2, line and branch coverage thresholds are uniform across all tiers. Other gates remain tier-dependent.
+Per Authoritative Decision #2, line and branch coverage thresholds are uniform across all tiers. The line threshold applies to every coverage language; the branch threshold applies to languages whose coverage tooling measures branch coverage. Other gates remain tier-dependent.
 
 ### Uniform across all tiers (T1–T4)
 
@@ -36,7 +36,7 @@ Per Authoritative Decision #2, line and branch coverage thresholds are uniform a
 - Type errors: 0.
 - Architecture violations: 0.
 - Line coverage: >= 85%.
-- Branch coverage: >= 75%.
+- Branch coverage: >= 75% for languages whose coverage tooling measures branch coverage. PowerShell (Pester) and bash (kcov) are exempt from this threshold because neither tool measures branch coverage; no branch-coverage gate applies to them.
 - No regression on changed lines.
 
 ### Tier-dependent
@@ -53,4 +53,4 @@ Per Authoritative Decision #2, line and branch coverage thresholds are uniform a
 
 ## Rationale (uniform coverage thresholds)
 
-High test coverage is a fundamental quality-control design choice that enables autonomous agentic development and trust in the work product. For that reason, line coverage >= 85% and branch coverage >= 75% apply uniformly across T1–T4; tier-specific lower coverage floors are not used in this repository.
+High test coverage is a fundamental quality-control design choice that enables autonomous agentic development and trust in the work product. For that reason, line coverage >= 85% applies uniformly across T1–T4 to every coverage language, and branch coverage >= 75% applies uniformly across T1–T4 to every language whose coverage tooling measures branch coverage; tier-specific lower coverage floors are not used in this repository. The branch threshold is not applied to PowerShell or bash because Pester and kcov do not measure branch coverage. That exemption is a capability limit on an unevaluable threshold, not a licence to exclude files from measurement: PowerShell and bash production files remain in the coverage denominator under the Coverage Exclusion Policy in `.agents/skills/general-unit-test/SKILL.md`.

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.24"]
+args = ["-y", "@danmoisan/drm-copilot-mcp@1.0.27"]
 required = true
 enabled_tools = [
     "collect_commit_context",

package/resources/customizations/.github/skills/evidence-and-timestamp-conventions/SKILL.md

@@ -83,6 +83,19 @@ When evidence artifacts are used for automated checking or plan reconciliation,
 - `Command: <exact command>`
 - `EXIT_CODE: <int>`
 
+One optional field may also be declared:
+- `ExpectedExitCode: <int>` — the exit code the gate is expected to produce.
+
+Rules for the optional expectation field:
+- The spelling is exact and case-sensitive: `ExpectedExitCode`. `expectedexitcode` and `Expected Exit Code` do not match the accept-list and are discarded as unrecognized rows.
+- The value is a single integer. A leading sign is accepted and no range check is applied; the value is used for an equality comparison only.
+- When the field is absent the expectation defaults to `0`, so every artifact that omits it keeps its existing result. Writing `ExpectedExitCode: 0` explicitly renders identically to omitting the field.
+- A present but non-integer value (including an empty value) makes the WHOLE artifact `unparseable`. An unparseable artifact is dropped by the collector filter, so a typo in the expectation removes the row from the PR body rather than degrading it to `fail`.
+- When the field is duplicated, the FIRST occurrence wins in both the Python and the TypeScript parser; later occurrences are ignored.
+- The field is per-FILE, not per-gate: one artifact carries exactly one expectation, so an artifact recording several gates cannot express a different expectation for each. Record a gate that needs a non-zero expectation in its own artifact file.
+
+A gate whose observed `EXIT_CODE` equals its declared expectation is normalized to `pass`. The observed exit code is still displayed, and the rendered row additionally carries `  - Expected EXIT_CODE: <int>` between the `EXIT_CODE` and `Normalized result` lines when the expectation is non-zero.
+
 ### Baseline Evidence Output Summary (Required)
 
 For baseline evidence artifacts stored under `evidence/baseline/`, include an output summary in addition to the schema fields above:

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

@@ -90,6 +90,27 @@
             # coverage.
             '.claude/hooks/enforce-discovery-artifact-gate.ps1'
             '.claude/hooks/validate-discovery-artifact-gate.ps1'
+            # Issue #475 added the portable discovery-validation module so both discovery
+            # hooks stop invoking a Python interpreter; measured here so the new production
+            # module is not excluded from coverage.
+            '.claude/lib/discovery-validation/DiscoveryValidation.psm1'
+            # Issue #475 added the portable orchestrator-state parity modules so the
+            # completion hook validates the checkpoint without a Python interpreter;
+            # measured here so the new production modules are not excluded from coverage.
+            '.claude/lib/orchestrator-state/OrchestratorStateCheckpointValue.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateReceipts.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateModelReceipts.psm1'
+            # Issue #475 added the portable Codex routing resolvers so the U6.X and U6.T
+            # checkpoint checks resolve deployments and topologies without a Python
+            # interpreter; measured here so the new production modules are not excluded.
+            '.claude/lib/codex-routing/CodexDeployment.psm1'
+            '.claude/lib/codex-routing/CodexTopology.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateCodexModelReceipts.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateCodexTopologyReceipts.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateRoutingMatrix.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateCompletionChecks.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateRoutingContract.psm1'
+            '.claude/lib/orchestrator-state/OrchestratorStateUnconditional.psm1'
             # 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
@@ -116,14 +137,20 @@
             '.codex/hooks/enforce-epic-planning-only.ps1'
             # Issue #447 added the .claude-resident PowerShell blast-radius library, the
             # two-language mirror of scripts/dev_tools/compute_blast_radius.py and its
-            # helper modules. The set is split across five files only to satisfy the
+            # helper modules. The set is split across six files only to satisfy the
             # 500-line limit; measured here so no new production module is excluded from
             # coverage.
+            # Issue #489 added BlastRadiusNormalization.psm1, which holds the
+            # read-by-mandate exclusion plus Get-ContractIdentifier and
+            # Resolve-BlastRadiusModule relocated out of the two modules that had run
+            # out of headroom. The relocation moves already-measured lines, so the new
+            # file is registered here to keep them in the coverage denominator.
             '.claude/lib/blast-radius/BlastRadiusExtraction.psm1'
             '.claude/lib/blast-radius/BlastRadiusGlob.psm1'
             '.claude/lib/blast-radius/BlastRadiusConfig.psm1'
             '.claude/lib/blast-radius/BlastRadiusValidation.psm1'
             '.claude/lib/blast-radius/BlastRadius.psm1'
+            '.claude/lib/blast-radius/BlastRadiusNormalization.psm1'
             # Issue #440 added the two parallel enforcement hooks (the Layer 1 cohort
             # barrier and the worktree removal gate) and extended the invocation-origin
             # hook with the parallel-agent family; measured here so no new or changed
@@ -143,6 +170,15 @@
             # excluded from coverage. The test suite dot-sources the file (guarded body) so
             # line attribution is valid.
             '.claude/hooks/enforce-parallel-abandon-gate.ps1'
+            # Issue #491 added the Mermaid validation PreToolUse hook and its dependency-free
+            # validator library; measured here so the new production files are not excluded from
+            # coverage. The hook's test suite dot-sources the file (guarded body) and the library
+            # suites import the modules, so line attribution is valid.
+            '.claude/hooks/enforce-mermaid-validation.ps1'
+            '.claude/lib/mermaid/MermaidGrammar.psm1'
+            '.claude/lib/mermaid/MermaidLineScanner.psm1'
+            '.claude/lib/mermaid/MermaidMarkdownFences.psm1'
+            '.claude/lib/mermaid/MermaidValidation.psm1'
         )
         # Optional: don't fail the run on coverage percentage
         CoveragePercentTarget = 0