golem15/msd-core
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #3499 from gsd-build/fix/3489-state-complete-phase-idempotent

Browse Source 
fix(sdk): make state.complete-phase idempotent (#3489)
This commit is contained in:
Tom Boucher
2026-05-14 10:08:49 -04:00
committed by GitHub
parent 62c64a757c beca07cf3a
commit 12accdbd02
3 changed files with 150 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.changeset/3489-complete-phase-idempotent.md Normal file
View File

@@ -0,0 +1,5 @@
---
type: Fixed
pr: 3489
---
**`state complete-phase` is now idempotent — re-invocation no longer rolls STATE.md back.** Previously, running `gsd-sdk query state.complete-phase --phase <N>` (or `gsd state complete-phase --phase <N>`) a second time on a phase that was already marked complete silently rewound STATE.md to that phase's moment-of-completion, clobbering `Status`, `Last Activity`, `Last Activity Description`, and the `## Current Position` body. Any downstream consumer trusting STATE.md (`/gsd-progress`, planner, the next phase's discuss-phase context loader) was routed back to the rolled-back phase. The handler now reads STATE.md before writing: if the canonical `Current Phase` field already names a phase distinct from the one being completed, the project has clearly advanced past it and the handler returns a no-op (`{ updated: [], phase: "<N>", idempotent: true, note: "phase already superseded; no-op" }`) without touching STATE.md. (#3489)