Relax reviewer scope enforcement to allow necessary related

Tinker

Home Epics Relax reviewer scope enforcement to allow necessary related changesEdit

Relax reviewer scope enforcement to allow necessary related changes

Cancel

Title *

Project *

Description

## Problem

The reviewer is currently rejecting PRs for "scope creep" when workers include necessary related changes that are required to make the app actually work. This causes friction because:

1. **Fixing the app often requires touching multiple areas** - A single ticket's work often requires changes across multiple files
2. **Dependencies are interconnected** - Removing a feature (like CodeDiff) requires updating all references, not just files "in scope"
3. **Strict scope enforcement blocks necessary fixes** - Workers are forced to create multiple tiny PRs instead of one working change

## Example Issue

PR #24 (rename `api_key_plaintext` to `api_key`) included necessary cleanup from PR #56 (CodeDiff removal). The reviewer flagged this as "out of scope" but these changes were **required** for specs and the app to work.

## Current Behavior

Reviewer returns PRs with:
> "Out-of-Scope Changes (Should Be Separate Tickets)"
> "Action Required: Create a focused PR with ONLY the [ticket scope] changes"

## Desired Behavior

The reviewer should:
1. **Allow necessary related changes** - If a change is required for the app to work, it's in scope
2. **Focus on correctness over bureaucracy** - Does the change break anything? Is it well-tested?
3. **Use judgment** - Distinguish between "unrelated feature work" vs "necessary cleanup/fixes"

## Acceptance Criteria

- Reviewer prompt updated to allow necessary related changes
- Focus on: Does code work? Are tests passing? Is it secure?
- Only flag truly unrelated new features as scope issues
- If a change is needed for the ticket's work to function, it's in scope