Relax reviewer scope enforcement to allow necessary related changes

## Code Review: PASS ### Changes Reviewed **Files Modified:** `agents.rb` and `agents/reviewer.md` **New "SCOPE ENFORCEMENT GUIDELINES" Section Added:** - Key Principle: **Focus on CORRECTNESS over bureaucracy** **ALLOWED (In Scope):** - ✓ Necessary related changes required for ticket to function - ✓ Cleanup of dependencies, unused code, deprecated features - ✓ Test updates to match implementation changes - ✓ Config/infrastructure changes needed for feature to work - ✓ Bug fixes discovered during implementation - ✓ Refactoring within the affected domain **NOT ALLOWED (Out of Scope):** - ✗ Entirely new features unrelated to the ticket - ✗ Separate capabilities that could be their own tickets - ✗ Major architectural changes not required for the ticket **Concrete Examples Provided:** - ALLOWED: Renaming api_key_plaintext includes removing CodeDiff references (necessary for app to work) - NOT ALLOWED: "Fix login bug" includes adding a new dashboard export feature (unrelated) **Review Focus Emphasized:** 1. Does the code work? (tests passing, app functional) 2. Is it secure? (no vulnerabilities, proper validation) 3. Is it well-tested? (appropriate coverage) 4. Are related changes truly necessary for this ticket to work? ### Acceptance Criteria Met - ✓ Reviewer prompt updated to allow necessary related changes - ✓ Focus on: Does code work? Are tests passing? Is it secure? - ✓ Only flags truly unrelated new features as scope issues - ✓ If a change is needed for ticket's work to function, it's in scope ### Code Quality Notes - Both agents.rb and agents/reviewer.md updated consistently - Guidelines are clear and actionable - Concrete examples help reviewers make good judgments - Shift from bureaucratic scope enforcement to correctness-focused review