From 66d80efb9f205d37e66b0812cd425ad0de067c3b Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Thu, 6 Aug 2026 11:02:55 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20R-168=20is=20CLOSED=20=E2=80=94=20the?= =?UTF-8?q?=20"CI=20is=20still=20owed"=20sentence=20was=20stale=20(R-229?= =?UTF-8?q?=20part=202)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- .claude/rules/gates.md | 3 ++- CHANGELOG.md | 12 ++++++++++++ 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/.claude/rules/gates.md b/.claude/rules/gates.md index b71a0f8..2786793 100644 --- a/.claude/rules/gates.md +++ b/.claude/rules/gates.md @@ -19,7 +19,8 @@ exiting non-zero if any fails. - **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). + 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).