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.1 KiB
type, pr
| type | pr |
|---|---|
| Added | 3325 |
workflow.human_verify_mode = end-of-phase is now the default — the planner no longer emits <task type="checkpoint:human-verify"> tasks for new projects; verification details are embedded into <verify><human-check> blocks on auto tasks and the verifier consolidates them at end-of-phase into the existing HUMAN-UAT.md flow. The previous mid-flight behavior cost a full executor cold-start (CLAUDE.md, MEMORY.md, STATE.md, plan re-read on respawn) per checkpoint:human-verify round-trip — measured at "tens of thousands of tokens" per round-trip on real projects. Set workflow.human_verify_mode = mid-flight in .planning/config.json to restore the pre-#3309 behavior. checkpoint:decision and checkpoint:human-action are unaffected by either value. Behavior change for existing projects: the new default takes effect when .planning/config.json is rewritten (e.g. via gsd config-set or first run on a new GSD version). Existing in-flight PLAN.md files with checkpoint:human-verify tasks continue to work in either mode — the flag only changes what the planner emits next time it runs. (#3309)