docs(rfc): RFC 0032 green — all six §5 scenarios discharged

[jensholdgaard]

What

RFC 0032 status red → green. All six §5 scenarios are discharged on main:

Scenario	What it pins	PR
.1 listed and readable	exactly two resources, application/json, §3.2 keys, three tools unchanged	#518
.2 content matches running config	configured promoted keys appear deduped/ordered; default = service.name; different configs → different bodies	#518
.3 severity correctness	bands equal SeverityName::floor/ceil, never literals	#519
.4 cost-tier stability	bloom claims checked against blooms harvested from a real writer footer; severity = statistics; no cost numbers	#519
.5 tool-description placement	URI exactly once per description; no tier tokens/digits/promoted keys	#519
.6 read-only contract	populated store serves bytes identical to empty store; unknown URI errors; RFC 0027 suite green	#519

All scenarios are local tests, green on main — unlike the RFC 0033 case, no pending measurement gates this flip. One-line frontmatter change; mdbook build clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WQY9wfrfRggqSpMLH8Xj3Y

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 22 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e0422c8e-87bc-4f75-be71-f5493132efe7

📥 Commits

Reviewing files that changed from the base of the PR and between 77ae4b4 and b9cd0c0.

📒 Files selected for processing (1)

• docs/rfcs/0032-query-schema-cost-model-resource.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rfc0032-status-green

---

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

[Copilot]

Pull request overview

Marks RFC 0032 as green by updating its frontmatter status now that all six §5 scenarios are discharged on main.

Changes:

• Update RFC 0032 frontmatter status from red to green.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.