diff --git a/REPORT-agent-transport-leak.md b/REPORT-agent-transport-leak.md
index 84888afe..c87d4473 100644
--- a/REPORT-agent-transport-leak.md
+++ b/REPORT-agent-transport-leak.md
@@ -155,6 +155,30 @@ reports kept landing from both boxes throughout.
 - **R-346** — this run anchored on the measured `t0` (fd 17 at 2026-08-18 09:51:22Z), never on a systemd
   timestamp, so the 5 h 56 m discrepancy did not touch these numbers.
 
+## 11. CI, by run ID — and the claim ledger
+
+| repo | run | sha | conclusion |
+|---|---|---|---|
+| `felhom-agent` | id **362** / run_number 50 | `ede49b610` — the fix | **success** |
+| `felhom-agent` | id **363** / run_number 51 | `7569f34ae` — the correction | **success** |
+| `felhom.eu` | id **364** / run_number 239 | `57dd62b09` — the write-up | **success** |
+
+No `--no-verify` anywhere. Both repos' pre-push hooks ran their gate entry point and passed;
+`release-complete` passes on v0.129.0, which is the honest state while 0.130.0 is unpublished.
+
+`python3 scripts/unproven.py --summary` — **unchanged: 23 walked, 32 not walked of 55.** No number
+moved, and correctly so: this run proved an engineering fact about our own connection handling, not a
+customer-facing product claim.
+
+**Closing state of ep0**, read one last time after everything:
+
+```
+t=10:40:23Z pid=551655 fd=17 estab=0 ctrl(.2)=0 fix(.3)=0 CLOSE-WAIT=0
+```
+
+`CLOSE-WAIT 0`, `ESTAB` in the low single digits, `fd` at the baseline, proxy PID **551655** — the same
+process that has been running since 2026-08-18 09:51:04, never restarted by this work.
+
 ## 12. Observations
 
 - **The closure refactor is not worth doing — recommend leaving it.** With the idle timeout restored an