docs: R-168 is CLOSED — correct the stale "CI is still owed" sentence carried into the trim (R-229)

Found by the checklist's own last item (confirm your push's CI run by run ID). Corrected here and
in the three sibling repos. Ledger J2 records the two lessons: a trim is a VOLUME operation and
carries stale claims forward unless each is re-checked, and the gate cannot catch this class --
"this register item is closed" is not mechanically checkable from the instruction file.

REPORT-instruction-trim-part2-2026-08-06.md

@@ -140,6 +140,22 @@ only the six Google auth stubs. Per §5 that means **write nothing**. The Go cod
 either: one direct dependency in `felhom-agent`, and the hub and controller are stdlib-only by
 standing rule.
 
+## 12b. A stale claim the checklist caught — corrected in all four repos
+
+Confirming this session's own push by run ID (checklist's last item) surfaced that **four instruction
+files claimed CI was still owed** (R-168) — and **R-168 was CLOSED on 2026-08-02**. CI exists, runs
+`repo_gates.py --fast` on every push, and emails on failure; this session's commits produced runs
+117 (`success`) and 118.
+
+One of the four was `felhom.eu/CLAUDE.md`, where **this session carried the stale sentence forward
+through the trim**. `felhom-agent/CLAUDE.md` **contradicted itself** — its release section already
+said R-168 mails the failure. Corrected in all four, pushed.
+
+**Two lessons about this task, not about CI:** a trim is a *volume* operation and carries stale
+content forward unless each claim is re-checked; and the gate cannot catch this class — "this
+register item is closed" is not mechanically checkable from the instruction file. The thing that
+caught it was the checklist item demanding a **run ID** rather than a memory.
+
 ## 13. Registers
 
 - **R-229** re-scoped — legs (a) and (c) **CLOSED**; (b) remains; (d) moved to R-230.