McRitchie Studio

Acceptance Criteria

• Release#reopen! moves an active release assembled→assembling (re-QA after new work is added), guarded against terminal states
• bin/release prepare is additive find-or-create: extends the active release (reopen! if assembled) else opens a new one, adds reviewed task(s), merges members, re-assembles to an assembled RC (QA auto-deploy tracked as a follow-up)
• bin/release ship promotes the assembled RC to prod (ff main, deploy, smoke /up, stamp deployed_sha, ship!) and refuses a non-assembled RC (release-notes posting tracked as a follow-up)
• the /deployments + /stages kickoff commands map to bin/release prepare / ship in the devops-cycle-design.md §1.4 runbook

Expected Test Plan

• unit: Release#reopen! + transition guards
• integration: Release::Conductor prepare!/ship! lifecycle across the model + DB (additive find-or-create, reopen-to-add, idempotent membership)

Checks Run

• [review] Avi SHIP — Conductor correct/idempotent/atomic, CLI safety rails hold (dry-run gating, --prod heroku-run quoting verified, no injection); applied should-fixes: ship assembled-guard + atomic prepare!; QA-deploy + release-notes filed as follow-ups; CI 4/4 green