releaselisted

# /release Cut a release. Version bump, changelog finalization, tag, deploy. ## When to use - Release readiness gates pass - Time to ship ## Workflow 1. **Phase 1 — Load context.** Read CHANGELOG.md, recent merged PRs, any open release-blocker issues. 2. **Phase 2 — Confirm readiness.** Run gates `ED-RELEASE-READINESS` + `QL-RELEASE-READINESS` from `.claude/docs/agent-gates.md` in parallel. The context to pass: - Release scope (PRs since last tag — see `git log <last-tag>..HEAD`) - CI status on main - Open release-blocker issues - Audit reports for the release window (`/audit-security`, `/audit-perf`, `/audit-a11y`, `/audit-seo` — required by the `full` profile where applicable) - Test coverage report (for `QL-RELEASE-READINESS`) Apply the **strictest-wins rule** across both gates: - `REJECT` → block the release; resolve blockers, re-run Phase 2; do not advance to Phase 3 - `CONCERNS` → `AskUserQuestion`: `Revise flagged items` / `Accept and proceed` / `Discuss further`. If `Accept and proceed` is chosen, record every open concern as a known issue in `CHANGELOG.md` or `.studio/state/blockers.md` before Phase 3 begins. Silent acceptance is not allowed — the written record is the gate. - `APPROVE` → proceed to Phase 3 **Gate:** `REJECT` is an absolute block. On `CONCERNS`, the written record of accepted risks is required before advancing. Append catalogue-format status trailers to `CHAN