Repository navigation
v0.4.24
Supersession-path fixes behind the live F6/S2 miss where a red suite reached the acceptance gate.
- Repoint scm-utils 0.3.5 → 0.3.6 (real install + lock normalized to the registry):
addE2eToRunTestsScriptno longer clobbersrun-tests.sh(it line-anchors the E2E marker instead of substring-matching the marker quoted in the template header), so the honest-GREEN + deploy-gate verify run the suite again. The hollow, always-exit-0run-tests.shis why the superseded tests never failed closed. driver-refactor-supersededstep inputstory:superseded-tests.json→story:refactor-verify-assess.json.flag-supersededwrites the marker per AC; a story-granularity supersession spanning >1 AC had no story-root file, soresolveInputsfail-louded ("missing input") before the Driver spawned. The assess finalize aggregates the per-AC flags into the story-level marker's union, which the step now reads.refactorSupersededDirectivereads that marker'sflagged_tests(the union across ACs), replacingsupersededTestsDirectiveon the refactor-superseded turn (which read only one open-AC's file, empty once every AC was done).flagSupersededTestsIfDirty— a deterministic REVIEW backstop (twin of the layering/ux backstops) flagging the build-refactor-routablesuperseded-testssmell on a real migration-drop supersession even when the verdict rubber-stampsrefactor:false.
Full BDD 4635. Pins scm-utils 0.3.6.