docs: retire the last two false gate-enforcement claims; scope the ranking heading

Closes the record-hygiene rider. Part 3 of the spec (documenting a
ROADMAP/OPEN-ITEMS state convention) is deliberately NOT done — its stated
evidence is false; see REPORT-record-correction-2026-07-29.md.

- CONTEXT.md:540 — "scripts/hub_confirm_gate.py enforces" was present tense
  about a gate invoked by nothing. Now says it asserts but is not enforced
  (R-29). Third instance of the class after :564 and configs.go:27.
- REUSE.md:62 — same claim, "enforces zero". The RULE stays (never native
  confirm()/prompt() is correct guidance and this is a reuse-reference row);
  only the enforcement claim changes, and it now says the rule holds only as
  long as you keep it.
- OPEN-ITEMS.md:4 — root REPORT.md is the overwritten per-session file;
  REPORT-<topic>.md is the non-clobbering sibling form (CLAUDE.md:82-87), of
  which 14 exist. The prohibition on durable content living only there stays.
- OPEN-ITEMS.md:55 — "Why the READY rows rank this way" promised a complete
  ordering and listed 5 of ~15 open rows. Scoped to TOP, with a half-sentence
  saying it is deliberately not a full ordering. No row added to the list.

hub/internal/web/configs.go:27 left alone (R-94 leg (b), needs a hub build).
No gate wired, run or fixed. Documentation only, no version bump, no CHANGELOG.

CONTEXT.md

@@ -537,7 +537,8 @@ the guest it backs up. Gaps minted the same session: **R-102 … R-108**.
   CLOSED (reset-request response carries the rotated code hash — ACK shape/guarantee — emailed
   codes work immediately; live 1 s apply + first-try accept on Viktor's exact failure path) and
   F-16 CLOSED (zero native `confirm()` in the hub UI — `inline_confirm.html` partial, Igen/Mégse
-  inline two-step, `scripts/hub_confirm_gate.py` enforces; danger-zone typed-confirm untouched;
+  inline two-step, asserted by `scripts/hub_confirm_gate.py` — **which exists but is NOT enforced:
+  it is invoked by nothing** (R-29); danger-zone typed-confirm untouched;
   live: offsite re-issue completed under browser automation without freezing). Operator resend
   keeps the ACK lag — flash says so. Take-two §4 dispositions updated (F-15/F-16/zero-toggle obs
   → SHIPPED). Remaining from take-two: **F-14** (needs operator ruling: auto-Reissue re-adopt vs