docs(rfc): RFC 0032 specified — §5 criteria declared complete

[jensholdgaard]

What

RFC 0032 status drafted → specified (status-only flip, the RFC 0033 #507 precedent).

The gate condition holds as merged in #515: all six §5 scenarios (RFC0032.1–.6) are Given/When/Then-testable against the RFC 0027 in-process MCP harness pattern, and the one touched hazard — #6, the DSL surface must not leak the raw Parquet schema — is covered by the fields-are-DSL-productions scenarios (.1/.4) plus the §3 design rule.

Next ladder step: red (stubs land, status specified→red).

Checks run

mdbook build clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WQY9wfrfRggqSpMLH8Xj3Y

[Copilot]

Pull request overview

Advances RFC 0032 (“Query-schema and cost-model resource for the MCP surface”) from drafted to specified, reflecting that §5 acceptance criteria are declared complete and test-turnable per the RFC ladder process.

Changes:

• Flip RFC 0032 frontmatter status from drafted to specified.

---

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 34 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: 0dd469cc-cc0e-4b52-93a2-eabaabc2ba78

📥 Commits

Reviewing files that changed from the base of the PR and between 7c949d1 and 817cd2e.

📒 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-specified

---

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