docs(board): #717 post-merge hygiene — triangle value-tenant half MERGED

[AdaWorldAPI]

What

Post-merge board hygiene for #717 (D-TRI-1 value-tenant half — the autopoiesis triangle, merged to main at 74d16f92):

• LATEST_STATE.md: the feat(contract): D-TRI-1 value-tenant half — autopoiesis triangle (3 SoA lanes) #717 entry flipped IN PR → MERGED.
• PR_ARC_INVENTORY.md: prepended the feat(contract): D-TRI-1 value-tenant half — autopoiesis triangle (3 SoA lanes) #717 entry (Added / Locked / Deferred / Docs / Confidence).

Keeps the board live per the P0 board-hygiene rule now that #717 is on main.

Next (deferred — the classid half of the batched mint)

The autopoiesis-triangle substrate is now on main (3 SoA lanes, accessors, auditor LAYOUT-CLEAN). The remaining D-TRI-1 work is the classid half, an OGAR-originated batched mint (never solo):

• chess domain 0x06 (confirmed free in ogar-vocab — Unassigned spans 0x03–0x06, 0x10+): the DecisionEpisodeV1 concepts (episode / candidate / iteration / event) → feeds the chess-as-teacher arc (P5).
• Tasks-SoA cognitive-task concepts (fan-out / counterfactual / synthesis / inference / deduction / extrapolation / syllogism — operator-ruled canonical).
• BoardAggregates value tenant @ row_offset 188 (W2a).

Each originates in ogar-vocab, mirrors into lance-graph-contract::ogar_codebook with parity tests, and lands its BUILTIN_READ_MODES entry. Then P4 wires the ancestry-pipeline gems into the triangle lanes (triangle_for/set_style_lane), honoring the two TD-TRI-1-P4-OBLIGATIONS.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Awg6TXocHcwTtc6eGsHcdD

---

Generated by Claude Code

[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_f638e016-1675-4e76-809a-6078b76a4461)

[coderabbitai]

Warning

Review limit reached

@AdaWorldAPI, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0faec0b5-2a7e-40bc-b1b9-f5d7089e35b1

📥 Commits

Reviewing files that changed from the base of the PR and between 74d16f9 and 580d8d2.

📒 Files selected for processing (2)

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

---

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.}