docs(board): record merged #917 — normalized-substrate reference

[AdaWorldAPI]

Post-merge board hygiene for #917, which was a content PR (new knowledge doc + two corrections) and therefore carries the full merged-PR obligation rather than the hygiene-only termination clause.

• LATEST_STATE.md PREPEND — what docs(weather): normalized-substrate reference — palette256 × helix360 #917 establishes about already-shipped code (it added no types): the fisher_z / hyperbolic_depth reading split and why the encoder stores the z-form; helix360 as the existing ValueTenant::HelixResidue lane (U8×6 @ offset 112) read as 2 × 24-bit in/out; the [G-absence] pair-writer gap; floor scoping resolved as an ingest policy with probes P1–P6 all NOT RUN.
• PR_ARC_INVENTORY.md PREPEND — Added / Locked / Deferred / Docs + Confidence, plus a provenance note recording the five-correction arc and the meta-rule it produced (consult-don't-guess applies to one's own prior in-session statements).

This commit is itself hygiene-only and generates no further board obligation (CLAUDE.md § Termination clause).

🤖 Generated with Claude Code

https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 59 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: b1c6ee2e-73a1-4b43-bbff-7545a4d04151

📥 Commits

Reviewing files that changed from the base of the PR and between b1bcee4 and 4be809c.

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

[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_578773f4-32b1-4fc7-9f60-b0ffdd684213)