@danmoisan/drm-copilot-mcp 1.0.26 → 1.1.0

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

@@ -137,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
@@ -164,6 +170,30 @@
             # 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'
+            # Issue #501 fixed the PreToolUse payload transport and shape across the whole
+            # hook surface. CodeCoverage.Path is an explicit per-file allow-list, so the new
+            # shared payload module, the six hooks that were changed but never registered,
+            # and the two dot-sourced helper siblings extracted for headroom are registered
+            # here. Without them the changed production surface would sit outside the
+            # coverage denominator, which the Coverage Exclusion Policy forbids.
+            '.claude/lib/hook-payload/HookPayload.psm1'
+            '.claude/hooks/enforce-promotion-mcp-only.ps1'
+            '.claude/hooks/enforce-orchestration-preimplementation-gate.ps1'
+            '.claude/hooks/enforce-evidence-locations.ps1'
+            '.claude/hooks/enforce-feature-folder-order.ps1'
+            '.claude/hooks/enforce-checkpoint-monotonic.ps1'
+            '.claude/hooks/enforce-prd-feature-before-planner.ps1'
+            '.claude/hooks/enforce-parallel-cohort-barrier-helpers.ps1'
+            '.claude/hooks/enforce-pr-author-skill-helpers.ps1'
         )
         # Optional: don't fail the run on coverage percentage
         CoveragePercentTarget = 0