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>
820 B
type, pr
| type | pr |
|---|---|
| Fixed | 3197 |
gsd-tools config-set workflow._auto_chain_active no longer rejected — workflow._auto_chain_active is an internal runtime-state key written by plan-phase, execute-phase, discuss-phase, and transition workflows. PR #3162 added it to RUNTIME_STATE_KEYS in the SDK's config-schema.ts but did not mirror the change to the CJS config-schema.cjs used by gsd-tools.cjs. Users routed through gsd-tools.cjs continued to see "Unknown config key" (#3033). The fix adds RUNTIME_STATE_KEYS to config-schema.cjs, exports it alongside VALID_CONFIG_KEYS, and updates isValidConfigKey() to accept runtime-state keys. The SDK config-mutation.ts is updated to import and check the same set. A new CI parity assertion ensures the two RUNTIME_STATE_KEYS sets stay in sync. (#3197)