[Chore] Clarify CodeRabbit approval checks

[zoomote]

​Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• Kept title and description checks as non-blocking warnings.
• Made CodeRabbit's built-in issue assessment an enforced gate, covering both linked-issue alignment and out-of-scope changes.
• Promoted regression evidence to an intentional enforced approval gate.
• Strengthened the existing repository-wide review instruction to catch local implementations that concretely bypass or duplicate established abstractions or nearby conventions.

Why this change was made

Authors were resolving inline findings without realizing that an error-mode pre-merge check in CodeRabbit's separate Walkthrough could still prevent approval. Disabling advisory metadata checks did not address that problem, so title and description warnings are retained. PR #1505 provides concrete motivation for enforcing scope assessment: CodeRabbit identified substantial changes outside the linked issue but reported only a warning. This configuration applies to future reviews and does not retroactively change PR #1505's result. The architecture guidance separately addresses a missed reuse issue on PR #1303 while remaining general and outcome-based.

References: CodeRabbit pre-merge checks, CodeRabbit Walkthroughs, and Google's architecture-aware review guidance.

Impact

Warning-mode title and description checks remain advisory and do not block merging. Error-mode custom checks and issue assessment block approval and merging under the request-changes workflow until resolved or explicitly ignored by an eligible reviewer. CodeRabbit's schema exposes linked-issue alignment and out-of-scope changes through the same issue_assessment mode, so both are enforced together. CodeRabbit reports those results in the parent Walkthrough comment; it does not provide a documented configuration option to duplicate failed pre-merge checks as inline review comments. Reviews also receive a concise architecture-aware principle without adding another overlapping path rule.

Follow-up to #1571.

[github-actions]

Review status

This PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging.

Current step: The required review sequence passed. Remaining merge requirements apply.

Review-state labels are managed by this workflow; do not edit them manually.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[edelauna]

@CodeRabbit review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• coderabbit-review-active

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: a50902b8-aef5-4978-bccd-fbf896b102a9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 75cb715d-4acf-4b45-8318-0fed3401d85f

📥 Commits

Reviewing files that changed from the base of the PR and between 134923e and 4096613.

📒 Files selected for processing (1)

• .coderabbit.yaml

Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.

📜 Recent review details

🔇 Additional comments (1)

.coderabbit.yaml (1)

149-150: LGTM!

Also applies to: 154-154, 156-156, 158-158, 161-161

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated pre-merge validation behavior: selected checks no longer run, while regression evidence is now required for successful validation.
  • Added guidance clarifying how warning-level check failures affect merging and automatic approval.

Walkthrough

The change updates .coderabbit.yaml pre-merge check modes. It disables three checks, documents warning behavior, and changes the “Regression evidence” check from warning to error.

Changes

Pre-merge policy

Layer / File(s)	Summary
Update check enforcement modes .coderabbit.yaml	Comments explain warning behavior. The title, description, and issue_assessment checks are disabled. The “Regression evidence” check becomes a blocking error.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 40966

This updates CodeRabbit approval-gate behavior by disabling advisory metadata checks and requiring regression evidence. No current merge-blocking risk is identified.

Suggested reviewers: edelauna

🚥 Pre-merge checks | ✅ 7 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the configuration changes, rationale, and impact, but it omits required template sections. It does not link an approved GitHub issue, provide a Test Procedure, complete the Pr…	Add the required template sections. Link an approved GitHub issue, describe the test procedure and verification steps, complete the Pre-Submission Checklist, state whether documentation updates are required, and provide any required additio…

✅ Passed checks (7 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: aligning CodeRabbit approval gates. It is concise and specific.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Regression Evidence	✅ Passed	PASS. The commit changes only .coderabbit.yaml (6 additions and 4 deletions). It changes CodeRabbit check modes and adds comments. It does not change application behavior or omit a focused test for …
Security Boundaries	✅ Passed	PASS. The pull request changes only .coderabbit.yaml. It disables title, description, and issue-assessment checks, and changes Regression evidence from warning to error. The `Security boundaries…
Persistence Integrity	✅ Passed	PASS. The HEAD diff changes only .coderabbit.yaml. It changes review-check modes and adds comments; it does not change source, tests, storage, state, or persistence code. The Persistence integrity…
Lifecycle Resource Cleanup	✅ Passed	PASS: The pull request changes only .coderabbit.yaml. The diff changes CodeRabbit check modes and adds comments; it does not change any application lifecycle path or create/remove/duplicate a listen…

Full details: Description check

Explanation

The description explains the configuration changes, rationale, and impact, but it omits required template sections. It does not link an approved GitHub issue, provide a Test Procedure, complete the Pre-Submission Checklist, or address Documentation Updates and reviewer contact.

Resolution

Add the required template sections. Link an approved GitHub issue, describe the test procedure and verification steps, complete the Pre-Submission Checklist, state whether documentation updates are required, and provide any required additional notes or reviewer contact information.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/clarify-coderabbit-approval-1rw1ggqwx2zr2

---

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