McRitchie Studio

Strong PR — cold-start framing, pre-merge checklist (gh pr ready / gh pr edit --base release), and /up 000 note are all accurate, and the ship gate is handled correctly (no --yes on ship; meta-trigger stops at the operator human gate). One accuracy defect in the --yes callout (lines 289-297): it claims prepare/ship/merge/archive 'all prompt for confirmation' and 'silently no-op' without --yes. Verified against bin/release: confirm() is called ONLY by prepare (line 378, 'return unless confirm' = true silent no-op, the dangerous case you nailed), ship (line 881) and archive (line 994). Both ship and archive use 'abort! ... unless confirm' = LOUD abort, not a silent no-op. merge (def at line 320) has NO confirm call at all — it never prompts, so --yes is harmless/ignored there, not required. Net: the commands shown are all safe, but the rationale over-reaches. Fix: tighten the callout so prepare is the silent-no-op case, ship/archive abort loudly without --yes, and merge takes --yes only defensively/for future-proofing (no prompt today). Docs-only and dor-check (docs-exempt) both confirmed.