msd-core/.changeset/2022-roadmap-verify-gate.md at 53e3028005e720498fe8250d188e3d4c1b9fbf1b

Files

Tom Boucher bb01f46c6b fix(#2022 ): gate roadmap update-plan-progress checkbox on verification passed (#2030 )

* fix(#2022): gate roadmap update-plan-progress checkbox on verification passed

cmdRoadmapUpdatePlanProgress stamped the phase checkbox + completion date
the moment all summaries landed, with NO verification gate — unlike
cmdPhaseComplete (phase.cts:1436) which checks readVerificationStatus. Since
update-plan-progress is called after every wave and every plan, the checkbox
fired before gsd-verifier confirmed the phase.

- src/roadmap.cts: isComplete now requires summaryCount >= planCount AND
  readVerificationStatus(phaseDir).status === 'passed'.
- tests/roadmap.test.cjs: 2 regression tests (no VERIFICATION.md → not
  complete; gaps_found → not complete) + updated 3 existing complete tests
  to include a passed VERIFICATION.md.

Closes #2022

* docs(#2022): backfill changeset pr 2030

2026-07-05 16:59:23 -04:00

624 B

Raw Blame History

type, pr

type	pr
Fixed	2030

roadmap update-plan-progress no longer checks the phase checkbox without verification — the command stamped the phase-level ROADMAP checkbox and completion date the moment the last plan summary landed (called routinely after every wave and every plan), with no verification gate — unlike phase.complete which correctly requires readVerificationStatus(...).status === 'passed'. Now isComplete requires both all plan summaries AND a passed verification, matching the cmdPhaseComplete contract, so the checkbox only fires after gsd-verifier has confirmed the phase. (#2022)

624 B Raw Blame History

624 B

Raw Blame History