docs: R-168 is CLOSED — the "CI is still owed" sentence was stale (R-229 part 2)

Corrected in all four instruction files across all four repos. Found while confirming this
session own push by run ID, which is precisely the check that catches it.

In felhom-agent/CLAUDE.md the sentence contradicted the same file release section, which
already said R-168 mails the failure -- a contradiction inside one instruction file, the exact
class the R-229 work exists to find.

REPORT.md deliberately NOT overwritten in the sibling repos: a one-line docs correction must not
destroy the record of their last real implementation.

CHANGELOG.md

@@ -1,3 +1,15 @@
+## docs — the "CI is still owed" claim was stale; corrected (2026-08-06, R-229 part 2) — no version bump
+
+**One sentence, no code.** This file asserted that continuous integration was still owed
+(`felhom.eu` `OPEN-ITEMS.md` R-168). **R-168 was CLOSED on 2026-08-02** — a Gitea Actions runner
+re-runs each repo's gate entry point on every push and emails the operator on failure. Found while
+confirming this session's own push by run ID, which is the check that caught it.
+
+The same stale sentence was in four instruction files across all four repos and is corrected in all
+four. In `felhom-agent/CLAUDE.md` it **contradicted the same file's release section**, which already
+said R-168 mails the failure — a contradiction inside one instruction file, which is the exact class
+the R-229 work exists to find.
+
 ## docs — expired and contradictory blocks removed from CLAUDE.md (2026-08-06, R-229) — no version bump
 
 **Documentation and gate registration only. No Go changed, nothing built, nothing deployed.**

CLAUDE.md

@@ -181,7 +181,9 @@ All shippable work commits **directly to `main`**; `main` equals what is deploye
   **The pre-push hook** (`.githooks/pre-push`) runs it with `--fast` and refuses a failing push. It
   is per-clone — switch it on once with `git config core.hooksPath .githooks`, and a manual run
   WARNS when this clone is unarmed. `git push --no-verify` bypasses it deliberately; **say so in the
-  session report when you use it.** Both facts are why CI is still owed (`OPEN-ITEMS.md` R-168).
+  session report when you use it** — CI re-runs the same entry point on every push and **emails the
+  operator on failure**, so a bypass is noticed even though it is not blocked (R-168, CLOSED
+  2026-08-02). This file already said so at the release section; the two now agree.
 - Testing doctrine (non-hollow tests, red-proofs, seams): use the `felhom-testing` skill.
 - **Logging**: the slog logger fans out to journald (configured level) + the always-DEBUG `applog.Ring`
   (remote pulls) — English, keys-never-values, durations on outcomes; full rules in