Post-merge records for #1217

[AdaWorldAPI]

Board hygiene for #1217 (b518dbf1). No code, no schema, no Cargo change.

Why this PR exists at all

#1217 was not hygiene-only — it landed a plan (the recovered SPEC v1) and a finding (E-AN-EMPTY-RANGE-AFTER-A-RESET-IS-NOT-EVIDENCE-1). The termination clause exempts a PR whose entire content is records for prior PRs; this one had content a future session needs the "why" for, so it owes an arc entry and a LATEST_STATE row.

This PR, by contrast, is hygiene-only, so the chain stops here.

What the entry records

• The mechanism. SPEC v1 was orphaned by a git checkout -B <branch> origin/main while unmerged, and the check meant to prevent that — git log origin/main..<branch> — returned EMPTY by construction, because an earlier reset had already re-pointed the branch. The symptom of the loss is indistinguishable from the all-clear. Correct check: git merge-base --is-ancestor, or the reflog.
• A retraction. board: record #1199's merge (hygiene-only — the chain stops here) #1201's own "merged MIXED" self-correction was false; it merged hygiene-only exactly as its body said.
• Three append-only readings, adjudicated against CLAUDE.md when two review bots asked for opposite changes on the same line: LATEST_STATE dated sections are historical (restore + prepend); PR_ARC_INVENTORY has its own narrower rule ("corrections append as new dated lines"); STATUS_BOARD is a live dashboard with an in-place lifecycle. CodeRabbit withdrew both findings it had raised against the latter two.
• The miss worth more than the fix. D-NGN-AUDIT lives in three files and the first pass updated two — because I was correcting whichever file each finding pointed at. A finding names a symptom; the fact has to be chased to every record that states it.

Still open, and deliberately not acted on

D-NGN-AUDIT remains HELD at Phase 2 on the F5 VIOLATES — the operator's to rule.

Banked for whoever rules it: the wave.abi path reads gz-TSV sidecar HashMaps (obo_full_edges, obo_ro_edges), not the declared edge_lanes slab and not DataFusion. E-EVERY-DOMAIN-IS-A-TABLE-AND-A-CROSSWALK-IS-A-CHAIN-OF-MASKS-1 (operator-ruled, #1218) names that class from the other end — something decided once upstream, re-derived at read time, per row — and cites obo_store.rs among its six sites. Whether that discharges F5 or merely re-describes it is not mine to decide.

Also flagged: SPEC §2's canonical_node.rs line numbers are stale after the mint_for V2/V3 drift, so Phase 3 should not be cast against v1 as written.

Method note

The branch was restarted from origin/main using the check the finding itself prescribes — git merge-base --is-ancestor confirmed the tip was fully merged before the reset, rather than reading an empty range after one.

Supersession index regenerated after the board writes; byte-identical.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EfrUJH3UNnv5NpDH4jDGHq

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 28 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 55 included PR review attempts over the past 7 days set your current allowance at 2 reviews 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: 1715293b-813f-47eb-98c8-7c3ec6dc8fef

📥 Commits

Reviewing files that changed from the base of the PR and between b518dbf and 8445b88.

📒 Files selected for processing (3)

• .claude/board/LATEST_STATE.md
• .claude/board/PR_ARC_INVENTORY.md
• .claude/board/STATUS_BOARD.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_d99c1226-4dd1-411c-8394-fe3b7cee0d28)