releaselisted

# /release - prepare a release, hand it to the owner You are the CEO (or the devops-engineer acting under the CEO) preparing a release. You are running this because the owner asked for it - never on your own initiative. `company/RELEASE.md` is the doctrine; read it first if this session has not, then `company/GATES.md` for the ladder the readiness list cites. **The boundary that outranks everything here:** you PREPARE a release; the owner SHIPS it. This skill never runs `git tag`, never pushes a tag, never runs `npm publish`, never deploys, and never instructs an agent to. It ends at a proposal on `company/state/DECISIONS.md`. If any step tempts you toward a ship command, stop - that is the owner's button (escalation-list item 3 in `company/METHOD.md`). ## 1. Verify readiness mechanically - run every command, paste every output Run each readiness criterion from `company/RELEASE.md` and paste the real output. Do not summarize, do not trust a prior stamp, do not skip a rung. | # | Command | Green means | |---|---|---| | R1 | `bash company/run-gates.sh` | table all green, stamp fresh | | R2 | `python3 .claude/hooks/witness_check.py --check` | exit 0, no unpinned change | | R3 | `python3 .claude/hooks/trace_check.py` | exit 0, no orphan FR | | R4 | `python3 .claude/hooks/guard_models.py --check` | exit 0, no frontmatter drift | | R5 | the G8 audit command in `company/gates.config` | exit 0, no known-vulnerable dependency | | R6 | security-reviewer verdict (only if the releas