plates: adopt KIT-TAVERN v1 — certified-chain replication proof (#83)

[100yenadmin]

Second room through the certified chain, hours after the first: seg gate 100.00% on the FIRST build (0/154 — zero builder iteration; the correctness lives in the builder + gates now), flux base 0.974+ on kit depth, Gemini 3 Pro edit with the furniture-identity grounding clause (c1 scored 6/Δ−2.0 without it, c2 hit 7 vs 8, Δ−1.0 in-band with it — the clause is load-bearing and recorded in provenance), phase-corr aligned dx=0, seg-mask void composite. Collision truth unchanged. Evidence: qa/evidence/kit-tavern/ + #83 round log.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 13 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: ASSERTIVE

Plan: Pro Plus

Run ID: 19673941-965a-4fc3-9087-65ab5fc9131d

📥 Commits

Reviewing files that changed from the base of the PR and between ec4671a and cfae731.

⛔ Files ignored due to path filters (2)

• extensions/renderers/unity/plates/tavern_kit_v1_registered.png is excluded by !**/*.png
• qa/evidence/kit-tavern/seg_100pct.png is excluded by !**/*.png

📒 Files selected for processing (2)

• extensions/renderers/unity/plates_manifest.json
• qa/evidence/kit-tavern/seg_registration.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tavern-kit-plate

---

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

[evaos-code-review-bot]

evaOS review status: closed or merged before review

PR: #1689 - plates: adopt KIT-TAVERN v1 — certified-chain replication proof (#83)
Head: cfae731665d6db3721be5feeb6c004d18ef627ae
Updated: 2026-07-22T19:54:07.447Z

evaOS review stopped because the PR closed or merged before this queued head could be reviewed.

Automation note: agents should wait for this comment to reach completed, stale_head, closed_or_merged_before_review, skipped, or failed before treating evaOS review as settled for this head. provider_deferred means evaOS still intends to retry.

PR URL: #1689