Problem
scripts/tests/test-run-commit-contract.ps1 exits 1 at HEAD 384617f: the run-commit facade's published run-complete.json fails the suite's schema/runIdentity/snapshotIdentity/manifest.sha256 coherence assertion at line 73 ("facade published an incoherent A07 marker").
Verified against a pristine git archive HEAD extract with a binary built from that extract — identical failure, so this is a genuine HEAD defect, not working-tree contamination. The suite was never executed by CI until PR #60 wired it in (as continue-on-error with a comment pointing here), which is how the regression went unnoticed.
Next step
Debug which of the four coherence conditions fails and whether the facade or the test's expectation drifted (the A07 contract is part of the #46 T1 contract freeze surface — the parity harness from #57 does not cover this marker). Once fixed, drop the continue-on-error from the ci.yml step.
Refs #46, #57, PR #60.
Problem
scripts/tests/test-run-commit-contract.ps1exits 1 at HEAD 384617f: the run-commit facade's publishedrun-complete.jsonfails the suite's schema/runIdentity/snapshotIdentity/manifest.sha256 coherence assertion at line 73 ("facade published an incoherent A07 marker").Verified against a pristine
git archive HEADextract with a binary built from that extract — identical failure, so this is a genuine HEAD defect, not working-tree contamination. The suite was never executed by CI until PR #60 wired it in (ascontinue-on-errorwith a comment pointing here), which is how the regression went unnoticed.Next step
Debug which of the four coherence conditions fails and whether the facade or the test's expectation drifted (the A07 contract is part of the #46 T1 contract freeze surface — the parity harness from #57 does not cover this marker). Once fixed, drop the
continue-on-errorfrom the ci.yml step.Refs #46, #57, PR #60.