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>
1.2 KiB
1.2 KiB
type, pr
| type | pr |
|---|---|
| Fixed | 3183 |
Unblock v1.50.0-canary.2 release — three deterministic test gates failed during the canary publish attempt (run 25451329660). All three are content/structure gates surfaced by the MVP umbrella integration:
get-shit-done/workflows/help.mdnow documents/gsd-mvp-phase— the help.md ↔ commands/gsd parity test (tests/bug-2954-help-md-slash-command-stubs.test.cjs) requires every shippedcommands/gsd/X.mdto have a/gsd-Xmention in help.md. PR #3180 added/gsd-mvp-phaseto docs/COMMANDS.md but missed the in-product help that AI agents themselves load. New entry placed directly before/gsd-plan-phase(matches the user mental model: convert to MVP, then plan).tests/workflow-size-budget.test.cjsXL_BUDGET raised 1700 → 1800 —execute-phase.md(1727 lines) andplan-phase.md(1714 lines) absorbed MVP-mode verb-call additions from #3178 and exceeded the 1700-line cap. Bumped budget with comments noting the values and pointing at the structural follow-up. The proper fix is to extract MVP bodies to<workflow>/modes/mvp.mdper thediscuss-phase/modes/precedent — tracked as a follow-up after canary cycles. Bumping unblocks canary.2 today.