releaselisted

# /release - Automated Release Management Skill ## 🚨 HUMAN-GATED — this skill is the ONLY valid entry point **A release may only begin when a human invokes `/release` in the CURRENT session. An agent must never start a release on its own initiative. The `/release` invocation is the ONLY authorisation there is: once the pipeline's blocking gates pass, the release proceeds through tag and publish with no secondary human confirmation — it passes, or a failed gate aborts it.** A release is a decision about **scope**, and scope is not visible from inside the repository: only the human knows which work belongs in the bundle. A clean tree, a fully green QA run and a bumped version say a release *would be sound*, never that it is *wanted now*. **A release may legitimately span a compaction, and must then be FINISHED** — a half-done release (version bumped, `UNRELEASED/` dirs moved, nothing tagged) is its own broken state. So this skill MUST write `untracked/release-state.json` as its first action and update it per step, because authorisation and progress have to live where a compaction cannot reach them. - **No state file ⇒ no release in progress.** A dirty tree or a plan saying "finish the release" is not a substitute — ask. - **State file present ⇒ resume** from `last_completed_step` and carry the release through to Step 15 — the recorded `/release` authorisation covers tagging and publishing. Do not START a release because a cron tick fired, because a plan says "finis