board: post-merge hygiene for #1185 (D-OIF-1 ruled SUPERSEDED)

[AdaWorldAPI]

Board only. Discharges the merged-PR obligation for #1185 (f8b629a3): a PR_ARC_INVENTORY prepend and a LATEST_STATE table row.

Per CLAUDE.md's termination clause this PR is hygiene-only and generates no further arc entry and no further LATEST_STATE row — the chain stops here.

What the entries record

• D-OIF-1 ruled A, SUPERSEDED, D-OIF-1-DEC withdrawn. No hash was chosen because no hash is built: ColumnMaskRewriter's only non-test constructor in nine scanned repos sits behind a default-off feature no Dockerfile enables, behind a query flag, ending in a decoder stub that returns None — and it redacts above the scan rather than pruning the projection. policy.rs and rls.rs are frozen grace-period, not removed.
• The cross-repo reachability law, and the three verdicts it struck. The first census read zero call sites inside lance-graph as production absence for a deliberately cross-repo substrate, the same error lance-graph-java Claude/qwen claude reverse eng v hu hv #76 had just corrected for WideFieldMask. Rubicon (bardioc substrate-b), ogar-loco (blockly-rs) and ogar-r2il (the R2IL→loco bridge over r2sleigh) are all production; the RBAC zero-caller finding is now scoped to the nine repos rather than stated globally.
• kanban_actor.rs is live, not a tombstone: the actor was deleted, the file is read-only meta-awareness consumed by cycle_driver.rs and named as precedent by rubicon_witness.rs and rung_horizon.rs.
• The pin catch-up after D-LNC-3: lance 10 → 11, lancedb 0.37.1 → 0.38.0 (probe-gated) #1190, plus the honest open item: field-level authorization still has no enforced owner on any scanned production path.

Gates

append_only_gate 9/9, citation_decay --since origin/main 0 new, plan_dids clean, supersession index regenerated last.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DCfrD5y19cvFc4AoyydXYv

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 5 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 70 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 81058665-87a8-412b-a208-e9e9b8418573

📥 Commits

Reviewing files that changed from the base of the PR and between f8b629a and 0963523.

📒 Files selected for processing (2)

• .claude/board/LATEST_STATE.md
• .claude/board/PR_ARC_INVENTORY.md

---

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_5821d034-4110-4c2e-adc8-d8091d1c7999)

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.