ce-ship-releaselisted

# Ship Release **Invocation input:** Plan to release (and optional --version / --base): $ARGUMENTS Prepare and gate the decision to ship a verified plan — **decide, don't deploy**. `/ce-ship-release` is the downstream-most pipeline tool. It reads what the pipeline has already proven — the verification report, the code review, and the selected git range — and turns it into a **ship-release package**: a proposed version bump, a changelog derived from the shipped features, rollback-readiness plus **Supply-Chain Evidence**, and a proposed tag + release notes, all gated on a go/no-go the human owns. It writes one decision artifact and (only on consent) the versioned `CHANGELOG.md`. It **never** pushes, creates or moves a remote tag, deploys, or commits to a protected branch. It sits at the end of the chain, after the work is built and verified: ``` plan → spec → implement → { verify · review } → release ``` Distinct from its neighbors: - **vs `/ce-verify`** — verify proves the software *behaves*; release decides whether that proven state *ships*, and at what version. Release never re-tests — it reads verify's report and **refuses GO over unverified work**. - **vs `/ce-ship-document`** — release owns the versioned `CHANGELOG.md` (it holds the version number); `/ce-ship-document` writes user-facing usage docs and never writes the changelog. The two never write the same file. - **It is a gate, not a deployer.** Tagging, pushing, and deploying are the human's; releas