Waits attach to any record, not just findings

Adopting a rule is nobody's finding; neither is registering a canon kind
or publishing a document. Each obligation that lived outside the
mechanism was invisible to it. RISK-WP-0001 now carries both of its
custodian waits, and the escalation-rule one has the register's most
uncomfortable default pointed inward: unadopted by 2026-09-17 means
recorded as de facto in force but unratified, said on the face of every
escalation sent under it. A draft that quietly governs is exactly what
this register exists to notice.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tools/register_check.py

@@ -124,8 +124,9 @@ def main() -> int:
     # Waits: typed, dated, and defaulted (docs/method/dependencies.md).
     waiting, due_defaults, deep = [], [], []
     # A closed finding can still owe something — RISK-F-0001 is `fixed` and
-    # still waiting on its publication entry. Waits outlive statuses.
-    with_waits = [f for f in lib.findings() if f.get("waiting_on")]
+    # still waiting on its publication entry. Waits outlive statuses, and they
+    # are not a findings-only idea: adopting a rule is nobody's finding.
+    with_waits = lib.records_with_waits()
     waiting_ids = {f["id"] for f in with_waits}
     for f in with_waits:
         for w in (f.get("waiting_on") or []):