docs(agents): scope review focus to branch regressions

Add a guidance line to AGENTS.md and CLAUDE.md telling reviewers to
focus on behavior changes caused by the current branch and to ignore
known test flakes, environment setup issues, and nondeterministic tool
output churn unless explicitly asked to investigate them.

Author: cameroncooke

AGENTS.md

@@ -61,6 +61,7 @@ Use these sections under `## [Unreleased]`:
   - Common hang causes: locked physical device, stale simulator state, `devicectl diagnose` waiting for password, orphaned daemon process.
   - Capture what you find before killing, so the root cause can be fixed rather than papered over.
 - If physical-device snapshot tests hang after the final test summary, the likely cause is Apple post-failure diagnostics invoking `devicectl diagnose`, which may prompt for a macOS password and wedge in automated runs.
+- When asked to review changes or test failures, focus on regressions: behavior changes caused by the branch. Do not treat known/acceptable test flakes, environment setup issues, or nondeterministic tool output churn as regressions unless explicitly asked to investigate them.
 
 ## **CRITICAL** Tool Usage Rules **CRITICAL**
 - NEVER use sed/cat to read a file or a range of a file. Always use the native read tool.

CLAUDE.md

@@ -60,6 +60,7 @@ Use these sections under `## [Unreleased]`:
   - Do NOT just kill the run — first inspect the process tree (`ps -ef | grep -E "vitest|xcodebuild|simctl|devicectl"`) to identify what's stuck.
   - Common hang causes: locked physical device, stale simulator state, `devicectl diagnose` waiting for password, orphaned daemon process.
   - Capture what you find before killing, so the root cause can be fixed rather than papered over.
+- When asked to review changes or test failures, focus on regressions: behavior changes caused by the branch. Do not treat known/acceptable test flakes, environment setup issues, or nondeterministic tool output churn as regressions unless explicitly asked to investigate them.
 
 ## **CRITICAL** Tool Usage Rules **CRITICAL**
 - NEVER use sed/cat to read a file or a range of a file. Always use the native read tool.