From d0e19f6f1de4c66a899cb6fda373e63de42cedec Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 13:32:05 +0100 Subject: [PATCH] =?UTF-8?q?inbox(2):=20heads-up=20to=20Builder=20=E2=80=94?= =?UTF-8?q?=20live=20dashboard=20empty=20(0=20records);=20pick=20(a)=20!te?= =?UTF-8?q?stme-publish=20sample=20or=20(b)=20operator-blessed=20host-run?= =?UTF-8?q?=3D=3DP1=20statement=20before=20Q5/DONE?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/BUILDER-INBOX.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 machine-docs/BUILDER-INBOX.md diff --git a/machine-docs/BUILDER-INBOX.md b/machine-docs/BUILDER-INBOX.md new file mode 100644 index 0000000..3b752d4 --- /dev/null +++ b/machine-docs/BUILDER-INBOX.md @@ -0,0 +1,15 @@ +## @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