SPIKE ep0 connections: CI green by run id (360/237, 19672e685)

REPORT-spike-ep0-connections.md

@@ -154,6 +154,20 @@ the window's 46.2 hours; the first 9.6 h rests on ep0's own evidence.
   including the **pre-registered Phase C prediction**, committed before the mutation exists.
 - `documentation/backlog/OPEN-ITEMS.md`, `STATUS.md` — as above.
 
+## CI, checked by run ID
+
+**id `360` / run_number `237`, `head_sha 19672e685`, conclusion `success`**, started 2026-08-20 08:41:50Z
+— this run's own push. The four runs before it (ids 356–359) are also `success`, so the "green since run
+356" baseline in the spike prompt holds and nothing was inherited red.
+
+*Numbering note:* the API exposes two numbers per run and they differ by 123 here. The prompt's "run 356"
+matches the **`id`**, not the `run_number`; both are recorded in `evidence-…/ci-run-by-id.txt` so the
+reference is unambiguous.
+
+The pre-push hook ran `repo_gates.py --fast` and reported **all 10 gates OK** before the push proceeded —
+including `due-checks`, which convicted at Part 0 and passes now that the row is properly cleared. **No
+`--no-verify` was used**, and none was needed.
+
 ## What is inconclusive
 
 **Q3 is unmeasured**, by design. Everything stated about proportionality is a labelled prediction. Also

documentation/audits/evidence-ep0-established-connections-2026-08-20/ci-run-by-id.txt

@@ -0,0 +1,20 @@
+=== CI runs, checked by run ID ===
+auth: gitea user 'admin' from the git credential store
+captured: 2026-08-20T08:42:30.162205+00:00
+pushed head_sha: 19672e685ed478a7b3d6d2fa861b566a81b939b2
+
+   run   head_sha       status   conclusion  started
+   237  19672e685    completed      success  2026-08-20T08:41:50Z
+   236  848368ec3    completed      success  2026-08-18T17:33:13Z
+   235  104ef34f5    completed      success  2026-08-18T17:32:41Z
+   234  c03f629d4    completed      success  2026-08-18T17:28:50Z
+   233  ab2262c91    completed      success  2026-08-18T17:27:41Z
+
+NOTE on numbering: the spike prompt says 'CI has been green since run 356'.
+The API exposes TWO numbers per run. Both are printed so the reference is unambiguous:
+    id  run_number   head_sha  conclusion
+   360         237  19672e685     success
+   359         236  848368ec3     success
+   358         235  104ef34f5     success
+   357         234  c03f629d4     success
+   356         233  ab2262c91     success