docs(r3): §1.8 #83 single ledger status (DECLARED until Gap-4 F-γ.2) + cross-row sync

[briansrls]

Summary

Keep §1.8 row #83 lens_capability_register_zero_proxy_zero_stub on a single canonical closure track: ledger Status stays DECLARED — full scope IN R3 until the post-all-four-BEHAVIORALLY-COMPLETE register cascade (Gap-4 / Cluster F F-γ.2). Document lens_register_correspondence_test.rs only as supporting CI evidence (regen↔register, PROXY/STUB-zero slice, Band-C md↔lens_capability_register_rows projection) — necessary, not sufficient — so INVARIANTS P2 is not diluted by a parallel "narrow PASSING" row state.

Touches: docs/r3-program-plan.md, docs/r3-structure.md, docs/r3-actual-close-plan.md (Gap 4), docs/design-section-1-8-acceptance-aggregator-pattern.md, docs/audit/r3-close-predicate-execution-2026-05-13.md.

Not in this PR: worker brief path docs/briefs/r3-f-gamma-2-post-merge-capability-register-sync-worker.md (dispatch title only; file not added here).

Test plan

• Docs-only; no Rust changes. Spot-checked lens_register_correspondence_test.rs test names against the doc citations.
• CI: fmt + ci + v3 on this branch (see Actions on the PR).

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 5ee1490f · Trigger: schedule
• Thinking: 154s wall

---

BLOCKING (1)

Root Cause

• docs/r3-actual-close-plan.md The PR introduces a “split status at HEAD” for #83 instead of keeping the §1.8 Status at DECLARED with the narrow ratchet recorded as partial evidence → keep the canonical gate status tied to the full F-γ.2 predicate, or give the narrow ratchet a distinct non-closure view/receipt.

⚠️ The narrow receipt framing is useful, but the canonical ledger cannot mark the gate PASSING while its own full predicate remains downstream.

[briansrls]

BLOCKING: The canonical §1.8 row marks #83 CONSUMER_LANDED + PASSING for a narrow PROXY/STUB-zero ratchet while the same row says the full F-γ.2 §1.8 predicate remains downstream, creating two closure states for one gate and violating INVARIANTS P2 single-authority/no-dilution.

[briansrls]

Re BLOCKING (inline + codex) on dual closure state for §1.8 #83:

Verified: Marking the canonical §1.8 ledger row as CONSUMER_LANDED + PASSING for the narrow ratchet while the full Gap-4 / F-γ.2 Pass stayed downstream did read as two closure states for one gate id and conflicted with INVARIANTS P2 single-authority framing.

Fix (HEAD): §1.8 row #83 Status is back to DECLARED — full scope IN R3 with a single canonical Pass (= post-all-four-BEHAVIORALLY-COMPLETE / F-γ.2). lens_register_correspondence_test.rs is documented only as supporting CI evidence (necessary not sufficient) in that row, §1.7 “Status at HEAD”, the R4-carved paragraph, r3-structure.md §Acceptance, Gap 4, the §1.9 Cluster F precondition note, and r3-close-predicate-execution-2026-05-13.md (row #83 back to N/A_NOT_PASSING with explicit DECLARED + partial-harness explanation).

No Rust/test changes.