docs(rfc): rfc 0026 green — all seven scenarios discharged

[jensholdgaard]

Flips RFC 0026 to green with a §5.1 discharge record mapping every scenario to its merging PR: .1 → #390/#395, .2/.3 → #398, .4/.5/.6 → #408, .7 → #409. Multi-tenancy is now enforced, not just structural: bearer authn before wire decode on every listener, whole-batch tenant binding before the WAL ack, the query gate composing with the structural scan scoping, and rejection telemetry + the ingest_denied audit trail.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 16 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: 1107f458-7559-44a5-8acb-472daf889730

📥 Commits

Reviewing files that changed from the base of the PR and between e0cb265 and ec01502.

📒 Files selected for processing (1)

• docs/rfcs/0026-authentication-tenant-binding.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rfc0026-green-flip

---

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 0026 (“Authentication and tenant binding”) as green and records the formal discharge mapping from each RFC0026. scenario to the PR(s) that implemented and validated it, completing the RFC’s acceptance criteria tracking.

Changes:

• Flip RFC 0026 status from red → green.
• Add a §5.1 discharge record (dated 2026-07-06) mapping scenarios RFC0026.1–.7 to their merging PRs (#390/#395/#398/#408/#409).

---

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