diff --git a/machine-docs/BUILDER-INBOX.md b/machine-docs/BUILDER-INBOX.md
deleted file mode 100644
index 3b752d4..0000000
--- a/machine-docs/BUILDER-INBOX.md
+++ /dev/null
@@ -1,15 +0,0 @@
-## @2026-05-30T12:32:05Z — Adversary heads-up (non-gate): live dashboard is EMPTY — settle before Q5/DONE
-First-hand: `https://ci.commoninternet.net/` → "no recipe runs yet"; `/api/runs` 404; host
-`/var/lib/ccci-dashboard` has **0 json records** (dir mtime 2026-05-30 06:01:34Z — looks reset today).
-So the live results UX currently reflects NONE of the Phase-2 recipe suite.
-
-Not a veto, not blocking your discourse/plausible work. But before you write `## DONE` for Q5, please
-resolve ONE of:
-  (a) drive the Phase-2 recipe set (or a representative sample) through the literal
-      `!testme`→Drone→publish path so the dashboard shows them (satisfies P1 "a full green `!testme`
-      run" + D7 results-UX), OR
-  (b) put an operator-blessed statement in STATUS-2 that host `cc-ci-run` validation satisfies P1
-      (trigger is recipe-agnostic, proven once in D10) AND that an empty live dashboard is acceptable
-      for DONE.
-Either is fine — just flag your choice in STATUS-2 so I can sign the Q5/DONE handshake. Detail in
-REVIEW-2.md (## Break-it probe @2026-05-30T12:32:05Z). — Adversary
diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md
index 23359ce..4b1840f 100644
--- a/machine-docs/STATUS-2.md
+++ b/machine-docs/STATUS-2.md
@@ -1074,3 +1074,17 @@ start_period:1200s via install_steps + recipe_meta COMPOSE_FILE+CHAOS_BASE_DEPLO
 R011/R012 version-mismatch FATA → overlay needed matching version:"3.8". **NEXT:** author ≥2 discourse
 functional (incl §4.3 create-topic) for P3 — currently only health_check; then FULL lifecycle
 (install,upgrade,backup,restore,custom) green → CLAIM Q4.6. NOT yet claimed.
+
+### Q5/DONE forward-criterion @2026-05-30 (Adversary BUILDER-INBOX, REVIEW-2 977b01f) — NOT a veto
+**Live dashboard shows 0 run records:** every Phase-2 verification (Builder + Adversary) used host
+`cc-ci-run` (orchestrator direct), which does NOT publish to the dashboard; the literal
+`!testme`→Drone→publish path hasn't been exercised for the Phase-2 suite. Before the Q5/DONE handshake
+the Adversary requires EITHER (a) the dashboard shows Phase-2 suite runs via the real `!testme` path,
+OR (b) an **operator-blessed** statement here that host `cc-ci-run` validation satisfies P1 (the
+trigger is recipe-agnostic + proven end-to-end once in Phase-1 D10/D7) and the empty live dashboard is
+acceptable for DONE. **Builder position:** (b) is the proportionate path — the `!testme`→Drone→publish
+machine was D1/D7-proven in Phase 1 and is recipe-agnostic, so re-driving every Phase-2 recipe through
+Drone re-tests the *trigger*, not the *recipe tests* (which is what Phase 2 is about); but (b) needs an
+OPERATOR decision, so this is flagged for operator input (not self-grantable). Alternatively a single
+representative Phase-2 recipe driven through real `!testme` would satisfy (a) at low cost — candidate
+once the current recipe-PR work settles. **OPEN — operator pick (a) vs (b) before DONE.**