docs(rfc): flip RFC 0046 to green and RFC 0045 to superseded

[jensholdgaard]

Flips RFC 0046 to green — all eleven §5 criteria pass in #702 (merged 2026-08-17) — and, per the RFC README rule that supersessions are recorded in both frontmatters, marks RFC 0045 superseded with superseded-by: RFC 0046 (its green status block is kept below the new one as the record).

No thesis-gate applies (validated vacuous, RFC 0008/0044 precedent); accepted is a maintainer flip.

Doc-only; tracks #700.

🤖 Generated with Claude Code

https://claude.ai/code/session_01A6zqjWChsuUiahj3WB5s3H

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 4 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a5b0843b-c556-4592-8af0-f81e3d43fb2c

📥 Commits

Reviewing files that changed from the base of the PR and between 5e7b31b and 234d44f.

📒 Files selected for processing (2)

• docs/rfcs/0045-composite-tenant-derivation.md
• docs/rfcs/0046-out-of-band-tenancy.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.}

[Copilot]

Pull request overview

This PR updates RFC documentation state to reflect the completion and supersession outcome of the out-of-band tenancy work: RFC 0046 is flipped to green, and RFC 0045 is marked superseded by RFC 0046, with the historical green block retained as a record.

Changes:

• Update RFC 0046 frontmatter status to green and expand the status block to record the “all §5 criteria pass” outcome and implementation reference.
• Update RFC 0045 frontmatter status to superseded and set superseded-by: RFC 0046, adding a supersession status block while retaining the prior green record.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
docs/rfcs/0046-out-of-band-tenancy.md	Flip RFC 0046 to green and update the status block narrative to reflect passing §5 criteria and implementation landing.
docs/rfcs/0045-composite-tenant-derivation.md	Mark RFC 0045 as superseded by RFC 0046 and add a supersession status block while keeping the earlier green record.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.