docs: R-168 is CLOSED — correct the stale "CI is still owed" sentence carried into the trim (R-229)
gates / gates (push) Successful in 8s
gates / gates (push) Successful in 8s
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.
This commit is contained in:
@@ -93,7 +93,9 @@ today that is all of them. **A missing gate script is a FAILURE, never a skip.**
|
||||
**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; CI
|
||||
reports rather than refuses because there is no PR to gate — R-169).
|
||||
|
||||
<!--
|
||||
WHY A RUNNER AND NOT FIVE INVOCATIONS (2026-08-02, R-29): a census of all thirteen gates across the
|
||||
|
||||
Reference in New Issue
Block a user