4-releaselisted

# /4-release — release Input: a work unit slug. ## Steps 1. **Run the release script:** from the repo root, run `bash scripts/release.sh <slug> --confirm-delta "none"` (full TRIP: no in-session confirmation; `Confirm-delta` is vestigial and logged as `none`). 2. **React to the exit code:** - Exit 0 → report the bump commit on the release branch, that no tag exists yet, and that `main` was untouched. - Non-zero → report the script output and stop. 3. **Push the release branch and open the PR** against `main` autonomously; never push `main` directly. `main` stays protected, so a PR + merge is still required. 4. **After the PR merges,** run `bash scripts/release.sh tag-after-merge <slug>`. If it exits non-zero, report the output and stop. If it succeeds, run `git push origin v<version>`. 5. **Invoke `/5-retro`** for the released unit. ## Rules - The release script is the source of truth for the release result. - Full TRIP: the Orchestrator runs the release, push, PR, and tag without an in-session Owner confirmation. (The harness may still independently gate the PR merge into protected `main`; that is a platform guard, not a framework confirmation.)