review(2): break-it probe — LIVE dashboard has 0 run records (data dir empty, mtime 06:01Z); D7/P1 forward-looking criterion for Q5/DONE; NOT a veto; corrects earlier garbled api/runs line

machine-docs/REVIEW-2.md

@@ -1958,3 +1958,33 @@ so a blanket "§4.3-floor is all we can do, env-blocked" sign-off is **not** jus
 HELD pending my 5-attempt cold retry loop: if ANY attempt's first ClickHouse boot wins the race and
 the run goes 5-tier green, Q4.7-full is **PROVEN** (best outcome). If all 5 fail, the required path is
 the Q4.7b recipe-PR (cache+retry+un-silence), NOT a §8 deferral. Will finalize on loop completion.
+
+## Break-it probe @2026-05-30T12:31:32Z — LIVE results dashboard has ZERO run records (D7/P1 forward-looking; NOT a gate verdict, NOT a veto)
+No gate claimed (discourse Q4.6 still authoring per HEAD d822550; plausible Q4.7 recipe-PR pending).
+Cold first-hand check of the live results UX via the SOCKS proxy + host inspection.
+
+**VERIFIED FACTS (first-hand, my own commands):**
+- `GET https://ci.commoninternet.net/` → HTTP 200, body table = `<td colspan="5">no recipe runs yet</td>`.
+- `GET /api/runs` → HTTP 404 "not found" (the dashboard is server-rendered HTML via dashboard/app.py,
+  NOT a JS/SPA + /api/runs endpoint).
+- No secrets in the dashboard HTML (trivially — no runs rendered).
+- On host: `ccci-dashboard.service` active, `CCCI_DASHBOARD_DATA=/var/lib/ccci-dashboard`; that dir has
+  **0 `*.json` records** (empty), dir mtime `2026-05-30 06:01:34Z`. dashboard/app.py `_load_runs()`
+  reads per-recipe JSON from that dir → empty dir ⇒ "no recipe runs yet".
+
+**INTERPRETATION (clearly labeled as inference, not verified):** the data dir was cleared/reset ~06:01Z
+today (mtime), so the dashboard currently reflects nothing. Phase-1 D7 PASS was legitimate when made
+(6 recipes published via real `!testme`, Drone build #s in Phase-1 STATUS); the *current* emptiness is
+the go-forward concern, not a retroactive D7 failure.
+
+**Forward-looking Q5/DONE criterion (on record pre-DONE; raised to Builder via inbox):** before I sign the
+Q5/DONE handshake I will require EITHER (a) the live dashboard shows the Phase-2 recipe suite's runs
+(i.e. recipes were driven through the literal `!testme`→Drone→publish path, satisfying P1 "a full green
+`!testme` run" + D7 results-UX), OR (b) an operator-blessed statement in STATUS-2 that host `cc-ci-run`
+validation satisfies P1 (trigger is recipe-agnostic, proven end-to-end once in Phase-1 D10) and that the
+empty live dashboard is acceptable for DONE. Not blocking any in-progress work; not a veto.
+
+**Harness caveat for this session:** tool-output has been intermittently garbling/duplicating and even
+injecting phantom interpretive prose into results. Every fact above was re-confirmed via write-to-file →
+Read. (An earlier same-session "D6 sweep CLEAN / api/runs 18-runs" line I reasoned over was garbled
+fabrication — it never reached the repo; confirmed absent. This entry supersedes/corrects it.)