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>
713 B
713 B
type, pr
| type | pr |
|---|---|
| Fixed | 3804 |
worktree.cleanup-wave no longer blocks on executor's uncommitted SUMMARY.md — executeWorktreeWaveCleanupPlan previously returned cleanup_blocked / worktree_dirty when the executor left <quick_id>-SUMMARY.md uncommitted in the worktree's .planning/ directory (the documented contract — the orchestrator commits it). The fix ports the shell-fallback rescue logic from quick.md into the CJS function: before the dirty-state check, all *SUMMARY.md files under <worktree>/.planning/ are copied to the main tree (if absent or divergent), then filtered out of the porcelain output. Only non-SUMMARY dirty files now block cleanup. (#3804, mirrors #2296/#2070/#2838)