McRitchie Studio

Acceptance Criteria

• A release can include gem-repo tasks (studio-engine, solana-studio) as first-class members; Release::Conductor.prepare! no longer breaks the assemble step on a member that has no app branch in the release repo.
• Run Deployment (bin/release ship) processes members producer-first: gem members are published (PR merge + version bump + RubyGems push) BEFORE any app member deploys, honoring task dependencies (producer before consumer).
• The gem-publish step is approval-gated — an explicit confirm like the prod-deploy confirm, never a silent gem push.
• DOCS (the priority): devops-cycle-design.md + deployment.md document gem members + gems-first Run Deployment + the gem-release lifecycle; the board/in-app per-task action reflects gem vs app instead of offering an app-release button for a gem task.
• Tests: Conductor producer-first ordering + gem-vs-app member classification covered at unit + integration tiers.

Expected Test Plan

• [unit] repo classification (gem vs app) + Conductor producer-first member ordering
• [integration] prepare! on a mixed gem+app release assembles without merging the gem branch and orders gem members first

Checks Run

• [unit] bin/rails test test/models/release/repos_test.rb test/models/task_test.rb test/models/release/conductor_test.rb — repo gem/app classification, Task#release_repo/gem_release?, producer-first ordering + member_plan
• [integration] bin/rails test test/integration/release_flow_test.rb — mixed gem+app release: member_plan gem-first, gem kind+version / app branch, dependencies honored
• [unit] bin/rails zeitwerk:check clean; full suite 849 runs, 0 failures, 0 errors (4 pre-existing skips)