chore(release): v0.20.0

[arantespp]

Version bump only: 0.19.2 → 0.20.0 across all six packages, plus generated changelogs. No source changes.

Why minor, not major

#880 carries a BREAKING CHANGE: footer (the GuardrailVersion response moved document → config.document), and .claude/rules/release.md does not cover what a breaking change does at 0.x. #883 flagged this as something to verify rather than assume. pnpm lerna version --dry-run resolves it to 0.20.0 — the conventional-changelog-angular preset treats a breaking change below 1.0.0 as a minor bump — which matches the requested bump, so there is no discrepancy to reconcile.

What ships

• feat feat(orchestrations): give durable runs an identity and fail soat calls loudly #879 — durable run identity for orchestrations; loud failures on soat calls
• feat feat(server): extract a shared resource-versioning engine #880 — shared resource-versioning engine (breaking, see below)
• fix fix(orchestrations): pin a run to the graph it started on #892 — pin an orchestration run to the graph it started on (closes [bug] Orchestration graphs are not versioned — editing an orchestration mutates in-flight runs (orchestrations) #872)
• fix fix(workflows): pin a task to the state machine it entered on #895 — pin a task to the state machine it entered on (closes [bug] Workflow state machines are not versioned — editing a workflow mutates in-flight tasks #882)
• fix fix(workflows): give a workflow-dispatched agent the same run identity a run has #891 — a workflow-dispatched agent gets the same run identity a run has
• fix fix(tests): make the sonnet-workflows tutorial CI-viable #881 — make the sonnet-workflows tutorial CI-viable

#892 and #895 complete the code work tracked by epic #883.

Breaking change in this release

GuardrailVersion responses no longer carry a top-level document; the archived policy is at config.document, alongside the new id, label and created_by fields. Guardrail versions now share one shape with agent versions.

Deployment note

The guardrail_versions.document → config rename is applied by sync --alter, which does not migrate existing row data. Deployments that need pre-0.20.0 archived guardrail documents to remain readable should run:

UPDATE guardrail_versions SET config = jsonb_build_object('document', document);

New versions archive in the correct shape from the first write, so this is only relevant where that history matters. #892 and #895 need no backfill: their tables and columns are new, existing orchestrations get version = 1 and existing runs/tasks get a null pin, which is the documented degradation path (in-flight work continues on the live definition).

Merge instructions

Squash and merge, keeping the chore(release): title. Every job in main.yml re-checks startsWith(head_commit.message, 'chore(release):'); a default merge commit is titled Merge pull request #NNN from … and would silently skip the tag push, the npm publish and the Docker build while still showing green.

After merging, confirm the main.yml run actually started for the merge commit rather than being skipped.

Notes

• The branch name is this session's designated branch rather than release/v0.20.0. Nothing is gated on it — lerna.json allows claude/*, and both the PR-skip logic in pr.yml and the release gate in main.yml key off the commit/PR title.
• pr.yml skips build-test-and-deploy, smoke-test and tutorials-test for chore(release): titles by design; these commits were validated on main before the bump. all-checks treats skipped as success.
• No local v0.20.0 tag is left behind: the engines-restore amend orphaned the tag lerna created, so it was deleted. push-release-tag creates the real tag from the merged commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01867f4gq1du8pH2odz4qsB3

---

Generated by Claude Code