8616839cab
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>
6 lines
465 B
Markdown
6 lines
465 B
Markdown
---
|
|
type: Fixed
|
|
pr: 3291
|
|
---
|
|
**`state record-metric` and `state add-decision` no longer silently lose data** — when their target sections are missing they now auto-create the canonical scaffold (matching `state begin-phase` / `state advance-plan` DWIM behavior). `state add-blocker` receives the same fix. All three verbs now also honor `--ws <name>` to route writes to `.planning/workstreams/<name>/STATE.md` instead of always hitting root `.planning/STATE.md`.
|