releaselisted

# Release The self-contained release runbook. **Follow this skill directly - do not re-read `docs/release.md` for a normal release.** `docs/release.md` is the exhaustive reference; come back to it only for the edge cases flagged below (rollout tuning, retrying a failed build). This keeps a release token-light. **Default = stable patch.** "Release", "ship", "ship stable", "release otto" all mean a patch bump from the previous stable. Only run the beta path when the user explicitly says "beta". Never bump minor/major to trigger or retry a build - that needs an explicit "minor"/"major" from the user. ## The two-step safety gate (applies always) 1. **Preparation** (agent does this - local, reversible): pre-flight checks, draft changelog, sanity check. Show findings, wait. 2. **Go-ahead** (only after the user says "go ahead" / "ship it"): commit the changelog, run the release command. Invoking this skill is intent to _start_, not authorization to publish. If the user asks for a **preview**, show the prospective changelog and answer questions - do **not** commit, tag, or run any `release:*` command until they explicitly authorize. Last-minute changes always need approval. A sanity-check finding is information, not a directive - surface it, the user decides. --- ## Stable patch (the 95% path) ### 1. Pre-flight (agent, reversible) Run from a clean tree on `main`, on the exact commit to be released: ```bash npm run format && npm run lint && npm run typecheck # all green; c