feat: review readiness dashboard — track CEO/Eng/Design reviews per branch

Each review skill logs its result to JSONL. A shared {{REVIEW_DASHBOARD}}
placeholder displays run counts, timestamps, and a CLEARED TO SHIP verdict.
/ship pre-flight reads the dashboard and prompts when reviews are missing.

ship/SKILL.md.tmpl

@@ -50,6 +50,15 @@ You are running the `/ship` workflow. This is a **non-interactive, fully automat
 
 3. Run `git diff <base>...HEAD --stat` and `git log <base>..HEAD --oneline` to understand what's being shipped.
 
+4. Check review readiness:
+
+{{REVIEW_DASHBOARD}}
+
+If the verdict is NOT "CLEARED TO SHIP (3/3)", use AskUserQuestion:
+- Show which reviews are missing or have open issues
+- RECOMMENDATION: Choose B (run missing reviews first) unless the change is trivial
+- Options: A) Ship anyway  B) Abort — run missing review(s) first  C) Reviews not relevant for this change
+
 ---
 
 ## Step 2: Merge the base branch (BEFORE tests)