msd-core/.changeset/humble-dogs-gather.md at 697cbb1f05b47a3ea2461ba1d98f0fecf7d1045e

Files

Tom Boucher 05cd55d43b fix(#1913 ): derive workstream progress status from shipped signals (#1916 )

workstream progress trusted the mutable STATE.md `Status` field, so a
shipped/archived milestone whose field was left at `executing` was reported
as executing — a stale hand-maintained field became the source of truth
instead of the authoritative archive/tag/ROADMAP signals.

Derive status in the inventory builder from a milestoneShipped signal
(archived milestone snapshot under milestones/, or a SHIPPED marker in the
workstream ROADMAP), collected by inspectWorkstream. The inventory now
reports `status_source` (field|derived) and `status_conflict` (true when
the derived value disagrees with the stale field), and a shipped workstream
is never reported executing.

- src/workstream-inventory-builder.cts: milestoneShipped input + status_source/status_conflict outputs + derivation
- src/workstream-inventory.cts: workstreamMilestoneShipped() signal detector wired into inspectWorkstream
- tests/workstream-inventory.test.cjs: regression (builder unit + inspectWorkstream integration + negative)

Closes #1913

2026-07-02 10:24:41 -04:00

576 B

Raw Blame History

type, pr

type	pr
Fixed	1916

workstream progress no longer reports shipped milestones as executing — gsd-tools workstream progress now derives each workstream's status from authoritative shipped signals (an archived milestone snapshot under milestones/, or a SHIPPED marker in the workstream ROADMAP) instead of trusting the mutable STATE.md Status field, so a stale field can never hide a shipped/archived milestone. The output adds status_source (field | derived) and status_conflict (true when the derived value disagrees with the stale field). (#1913)

576 B Raw Blame History

576 B

Raw Blame History