board: PR #42 arc entry + backfill the twenty missing arc entries

[AdaWorldAPI]

Board hygiene only — no code, no types, no plan. Per the termination clause this PR generates no arc entry of its own.

What

PR_ARC_INVENTORY.md had entries for #1–#12, #14, #16, #18, #20 and #32, and nothing else. This adds #42's entry (missed at open) and backfills the twenty that were absent.

The gap, enumerated

present	#1–#12, #14, #16, #18, #20, #32
missing → backfilled	#13, #22–#31, #33–#41
absent and correctly so	#15, #17, #19, #21 — each is itself an arc-entry-only PR, exempt under the termination clause
stale	#32 read (draft, opened 2026-08-25) with no merge sha — now names its merge, and that it reached main only via #33

This corrects my own first count on this branch, which said nineteen and read the gap as starting at #21. Both wrong: it is twenty, and it starts at #13, well inside the range the first count read as complete. A range subtraction over a file with holes; enumerating is what found the difference.

Method — the point, not an aside

Each entry drafted from that PR's own body and diff: five parallel agents, four PRs each, none permitted to work from a later session's recall. Every backfilled entry's **Confidence:** bullet ends

Backfilled 2026-08-27 from the PR body and diff, not written at merge time.

so a reader can tell at a glance which entries were written at merge time and which were reconstructed. Several state plainly which of their claims are the PR body's own and were not re-verified.

Machine-checked before commit, not eyeballed: every cited sha resolves in git (35/35), every header date equals its commit date (20/20), and every merge vs squash label matches the commit's parent count (20/20).

Four things the backfill turned up

Each recorded in the entry it belongs to, not only in the issue:

• board: record R6–R8 and the twice-repeated measurement-ledger defect #25's body asserts "no code, no reproducer changes" — its own diff contradicts it, a second commit landed on the branch after the body was written.
• lgj-abi: hop sweeps the store ONCE, not 32 times — 3.5× at scale #39 left its lgj_hop doc comment describing the pre-change design; caught one PR later, by lgj-abi: hop gathers instead of sweeping — the predicted crossover does not exist #40.
• R12 — the Ghidra seam is an interface, and its P-code vocabulary cannot flatten #34's banked evidence file did not identify its own JDK (it captured JAVA_TOOL_OPTIONS instead); corrected same-day by R12-observed's JDK line said the tool options, not the JDK #35.
• [DO NOT MERGE AS-IS] hop as AND over a memoised per-facet mask — measured, conditional #41 is on main while its own title reads [DO NOT MERGE AS-IS] — recorded as unresolved disposition, not an endorsement.

Issue

ISS-LGJ-ARC-INVENTORY-STOPPED-AT-32 → RESOLVED, carrying the corrected count and the standing rule restated: the entry goes in at open, in the PR's own commit. The backfill is the repair, not the process.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 087dd0c0-8899-40f5-b335-917f272513a1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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_a4ddab8b-52fd-4446-b8ae-a165fed0874e)