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>
6 lines
1.4 KiB
Markdown
6 lines
1.4 KiB
Markdown
---
|
|
type: Changed
|
|
pr: 3574
|
|
---
|
|
**State commands now route through the SDK runtime bridge by default** — `gsd-tools state <sub>` (every canonical subcommand: load, json, get, update, patch, begin-phase, advance-plan, record-metric, update-progress, add-decision, add-blocker, resolve-blocker, record-session, signal-waiting, signal-resume, planned-phase, validate, sync, prune, milestone-switch) executes the same SDK handler that `gsd-sdk query state.<sub>` executes, in-process via `executeForCjs`. Output and exit-code shapes are byte-equivalent; 104 existing CJS tests pass unchanged. Two operating modes: SDK-delegation (default) and CJS-fallback (transparently used when the SDK is not loadable or when GSD_WORKSTREAM is set, since the sync bridge transport forces subprocess for workstream-scoped commands and subprocess is disabled inside the bridge). Bundles a fix for a Phase 5.0 (PR #3558) defect in `sdk/src/runtime-bridge-sync/worker.ts` that dropped `projectDir` and `workstream` from `RuntimeBridgeExecuteInput` — every sync-bridge dispatch hardcoded `projectDir = ''`, which prevented any registry handler from finding its `.planning/` files. Per-request adapter construction now closes over the correct values. Two CJS↔SDK behavioral asymmetries documented but not resolved in this PR: `state.complete-phase` remains CJS-only (no SDK handler exists yet); `state.add-roadmap-evolution` remains SDK-only (CJS router lists as unsupported). Closes #3567.
|