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>
617 B
617 B
type, pr
| type | pr |
|---|---|
| Fixed | 3679 |
gsd-executor no longer force-commits .planning/ artifacts when commit_docs: false — the executor agent prompt now explicitly handles the SDK's {committed:false, skipped:true, reason:'skipped_commit_docs_false'} envelope and is forbidden from falling back to raw git add / git add -f / git commit. The SDK's cmdCommit now sets skipped: true on both skip paths (commit_docs:false and .planning gitignored) so agents see the skip as a first-class signal. A structural regression test bans git add -f / git add --force from any agent or workflow body. (#3678)