msd-core/.changeset/archived/501-flat-phase-details-milestone-leak.md at 9e2ef2c94dea3f1267deba570c9a423fb38c2f85

Files

Tom Boucher 8616839cab chore: archive 463 shipped changeset fragments before wiring render (#714 )

CHANGELOG promotion was a manual operator step that was never run, so 463
fragments for work already shipped in <=1.3.1 accumulated in .changeset/.
Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1]
CHANGELOG sections (#690 backfill, PR #694). Rendering them now would
duplicate and mis-attribute shipped work.

Move them to .changeset/archived/ (read non-recursively by all changeset
tooling, so never rendered), keeping only the 3 genuinely-unreleased
fragments at the top level. Prep for wiring `render` into the release
finalize job (#690 follow-up).

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-05 14:53:17 -04:00

702 B

Raw Blame History

type, pr

type	pr
Fixed	513

Milestone phase counts no longer leak across a flat ## Phase Details section — when a ROADMAP listed per-phase details in a single flat ## Phase Details section before the milestone headings, extractCurrentMilestone folded every milestone's ### Phase N: entries into the active-milestone scope, so state json over-counted total_phases/total_plans (the whole project instead of the active milestone). The preamble now strips flat phase-detail blocks, and validate consistency / validate health (W007) compare on-disk phase dirs against the full roadmap so shipped-milestone dirs are not flagged as orphans once the scope is correctly narrowed. (#501)

702 B Raw Blame History

702 B

Raw Blame History