docs(review): enforce rule against challenging PR's stated intent

[kilo-code-bot]

Summary

• Adds a new top-level rule to REVIEW.md that explicitly prohibits the reviewer from raising issues about a PR's stated goals, scope decisions, or intentional trade-offs unless the approach is unsafe (data loss, security vulnerability, correctness bug).
• The rule is placed at the top of the file and marked as the highest-priority, overriding all other review guidance.
• Motivated by PR fix(code-reviews): bound cron pending drain #3396 where the bot flagged "old pending rows will become invisible after deploy" — a concern the PR description had already acknowledged as an intentional design decision ("Existing old idle pending reviews need manual retry or a one-time cleanup if we want to move them").

Verification

• Read the updated REVIEW.md to confirm the new section is clear, prominent, and includes a concrete counter-example showing what a violation looks like.

Visual Changes

N/A

Reviewer Notes

The new rule has a single exception: if the described approach is objectively unsafe (data loss, security vuln, or incorrect behaviour contrary to the PR's own goals), it should still be flagged as CRITICAL. All other design/scope challenges are prohibited.

---

Built for alex-alecu by Kilo

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)

• REVIEW.md

---

_{Reviewed by claude-sonnet-4.6 · 161,109 tokens}

_{Review guidance: REVIEW.md from base branch main}