msd-core/.changeset/2400-planned-phase-empty-transition.md at a613caaeef951d0bb89b6ebb4e6034cb9936b429

Files

Tom Boucher 2bcfaa2e27 fix(#2400 ): warn on planned-phase no-op + sync progress.total_plans (#2552 )

* fix(#2400): warn on planned-phase no-op + sync progress.total_plans

Bug A: When STATE.md Current Position has no recognized labels (narrative
prose), emit a warning field so the workflow detects the no-op instead
of continuing with stale state.

Bug B: Sync progress.total_plans in the YAML frontmatter when a plan
count is provided, preventing contradictory state between frontmatter
(0) and body (actual count). This writes the explicitly-provided count,
not a re-derivation from disk (#500 safe).

Closes #2400

* docs(#2400): backfill changeset PR number (2552)

2026-07-23 07:38:21 -04:00

706 B

Raw Blame History

type, pr

type	pr
Fixed	2552

state.planned-phase now warns on no-op transitions and syncs progress.total_plans — when STATE.md's Current Position has no recognized labels (narrative prose), the command emits a warning field so the workflow can detect the no-op instead of continuing with stale state. When a plan count is provided, progress.total_plans in the YAML frontmatter is updated alongside the body Total Plans in Phase field, preventing contradictory state between the two representations. Previously, the command silently returned success with an empty updated array and zero bytes written, and left progress.total_plans at 0 while the body reported the actual count. (#2400)

706 B Raw Blame History

706 B

Raw Blame History