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.0 KiB
type, pr
| type | pr |
|---|---|
| Fixed | 3577 |
Phase 6 config-* SDK port parity carve-outs — restored the legacy contract for four CLI tests broken by the Phase 6 router migration. config-ensure-section no longer routes through the new SDK configEnsureSection handler (which expected a positional <section> arg the CLI never passes) and instead keeps the cmdConfigEnsureSection → ensureConfigFile → buildNewProjectConfig CJS path that produces the full default .planning/config.json. The SDK configNewProject defaults now match sdk/shared/config-defaults.manifest.json (commit_docs: true, parallelization: true) and report the project-rooted relative path .planning/config.json to mirror the CJS shape. SDK error vocabulary is aligned with CJS: Unknown config key: <key> (no quotes), and config-get's malformed-JSON error is led by Failed to read config.json: so legacy regression tests keep matching. Closes the Usage: config-ensure-section <section> regression seen in tests/{config,agent-skills,ai-evals}.test.cjs.