test(rfc0029): red — all seven §5 stubs land, status specified→red

[jensholdgaard]

Moves RFC 0029 (OIDC bearer layer) specified → red on the usual cadence (the #412 pattern, in the post-RFC-0028 tests/it harness shape).

• All seven RFC0029.1–.7 scenarios land as #[ignore]d todo!() stubs in crates/ourios-server/tests/it/rfc0029_oidc.rs; each ignore reason names the green slice that will discharge it (config / verifier / binding / dex acceptance).
• Default runs stay green: cargo test -p ourios-server --test it → 26 passed, 12 ignored (7 new). cargo fmt --check + clippy -D warnings clean.
• Invariant §3.7 (multi-tenancy): no behavior change — stubs only; the enforcement contracts they pin are RFC 0026's, unchanged.

🤖 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: 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: b563ac77-517d-4803-b049-c0db6177bf02

📥 Commits

Reviewing files that changed from the base of the PR and between 47fa28f and 2c5f12e.

📒 Files selected for processing (3)

• crates/ourios-server/tests/it/main.rs
• crates/ourios-server/tests/it/rfc0029_oidc.rs
• docs/rfcs/0029-oidc-bearer-layer.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rfc0029-red

---

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

Moves RFC 0029 (OIDC bearer layer) from specified to red by landing the standard set of compiling, ignored todo!() scenario stubs in the tests/it integration harness.

Changes:

• Flip docs/rfcs/0029-oidc-bearer-layer.md frontmatter status to red.
• Add seven #[ignore]d todo!() stubs for RFC0029.1–RFC0029.7 in crates/ourios-server/tests/it/rfc0029_oidc.rs.
• Register the new RFC0029 test module in crates/ourios-server/tests/it/main.rs.

Reviewed changes

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

File	Description
docs/rfcs/0029-oidc-bearer-layer.md	Updates RFC status to red to reflect the new red-gate test stubs landing.
crates/ourios-server/tests/it/rfc0029_oidc.rs	Adds the seven RFC §5 scenario stubs as ignored todo!() tests with greppable scenario doc comments.
crates/ourios-server/tests/it/main.rs	Includes the new RFC0029 module in the consolidated integration test harness.

---

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