R-87 put back in the register; closed_register_gate.py is the 12th gate (R-405, R-406)

Records and process only. No machine contacted. No product code, no version bump,
no build, no deploy.

R-87 was moved into CLOSED-ITEMS.md by the 2026-08-22 compression sweep ef6ac6f while
its own state cell read "READY - RE-RANKED UP 2026-08-03 (R-86 closed)". R-378 records
that sweep moving six still-open rows and restoring them in the same session; this was
a seventh it missed. Nine days in the wrong file, with the register's ranking paragraph
ranking it fourth and pointing at nothing. Restored verbatim from ef6ac6f^, beside R-95
where it sat before.

The predicate is the LEADING VERDICT of the state cell, which is R-378's lesson and
decides the answer here. Measured on the file as pushed: an open word anywhere in the
state cell convicts 3 of 151 rows, two of them genuinely closed (R-224 and R-260 carry
"open"/"OPEN" inside long prose verdicts); the leading verdict convicts exactly 1; the
whole row convicts 144.

closed_register_gate.py, two rules: no open state word leading a CLOSED-ITEMS.md row's
verdict, and no R- id with a row in both registers. Red-proofed both, and negative-
controlled against the pushed pre-fix files where it convicts R-87 by name, rc=1;
restoring the planted rows leaves the file byte-identical. Registered as the 12th gate
in repo_gates.py, --fast, after it was green. Four residual holes in its docstring.

R-398 was also in both registers - a deliberate cross-reference stub. Now prose beneath
the table rather than a table row, because a row in both files is what rule 2 convicts on.

R-406 filed: two unrelated findings in OPEN-ITEMS.md both numbered R-133. The only such
collision in either register. Deliberately NOT gated - a within-register duplicate rule
would fail on a pre-existing row, and a registered-but-failing gate refuses every push.

golden-currency is RED at this commit and was already red at dddcc80 - controller
v0.230.0 released, newest golden 0.229.0. Pre-existing, not this session's debt.

Ceiling R-404 -> R-406.

scripts/CHANGELOG.md

@@ -1,3 +1,25 @@
+## closed_register_gate.py v1.0.0 — CLOSED-ITEMS.md holds closed work only (2026-08-31, R-405)
+
+**One row corrected, one gate added, no product code touched.** R-87 ("the restic tier is never
+restore-tested") was moved into `CLOSED-ITEMS.md` by the 2026-08-22 compression sweep (`ef6ac6f`)
+while its own state cell read `READY — RE-RANKED UP 2026-08-03 (R-86 closed)`. R-378 records that
+sweep moving six still-open rows and restoring them in the same session; **this was a seventh it
+missed**, and it sat in the wrong file for nine days while `OPEN-ITEMS.md`'s ranking paragraph ranked
+it fourth and pointed at nothing. The row is back beside R-95, verbatim from `ef6ac6f^`.
+
+- **The predicate is the LEADING VERDICT of the state cell** — R-378's whole lesson, and it decides
+  the answer here. Measured on the file as pushed: an open word anywhere in the state cell convicts
+  **3 of 151** rows, two of them genuinely closed (R-224, R-260 carry "open"/"OPEN" inside long prose
+  verdicts); the leading verdict convicts exactly **1**; the whole row convicts **144**.
+- **Two rules only** — no open state word leading a `CLOSED-ITEMS.md` row's verdict, and no `R-`
+  identifier with a row in both registers. Its four residual holes are in its docstring.
+- **Red-proofed both rules**, and negative-controlled against the pushed pre-fix files, where it
+  convicts R-87 by name and rc=1. Restoring the planted rows leaves the file byte-identical.
+- **`R-398` was also in both registers** — a deliberate cross-reference stub. It is now prose beneath
+  the table rather than a table row, because a row in both files is what rule 2 convicts on.
+- Registered as the **12th** gate in `repo_gates.py`, `--fast` (two file reads), **after** it was
+  green.
+
 ## check_skills.py v1.0.0 + five process-domain skills (2026-08-25)
 
 **Five new skills under `skills/`, one new checker under `scripts/`, no product code touched and