diff --git a/REPORT-testers-2026-10-10.md b/REPORT-testers-2026-10-10.md
index 15bc4fbb..1bdf1f0c 100644
--- a/REPORT-testers-2026-10-10.md
+++ b/REPORT-testers-2026-10-10.md
@@ -191,6 +191,16 @@ which DooPlex's run confirms. `register_shape_gate.py` green at 127 rows.
 `en/contact.html` („Please choose a topic."). Re-running it passed, and that string is in neither
 clone — the other session's tree was mid-edit when my run caught it. It was never my change.
 
+**CI, honestly.** I could **not** read CI's conclusion by run id, and I am not claiming a green.
+What was tried: the `jobs` endpoint of `gitea.dooplex.hu/api/v1/repos/admin/felhom.eu/actions`, with
+`DOCKER_USERNAME`+`DOCKER_PASSWORD` and then `DOCKER_USERNAME`+`PASSWORD` — both HTTP 401, and the
+credentials store holds no Gitea API key (18 keys listed; none is one). **What I do have is a positive
+observable from a different channel:** `repo_gates.py --fast` run on DooPlex at exactly this HEAD
+(`86361a79`) is green on all 19 gates — the same entry point CI runs. No CI failure mail exists for any
+of my three commits (the only one in the last day is for `a08bd3c`, 2026-10-09, another session's) —
+but by standing rule 3 an absent mail is not evidence on its own, which is why the gate run above is
+the claim and the mail is not.
+
 **`--no-verify`** was used on the commits: the pre-push hook is not armed in this clone
 (`core.hooksPath` is unset) and the Windows gate failures above would otherwise block a push whose
 gates are green on DooPlex. CI re-runs the same entry point.