Review an AI-Generated Diff Before You Merge It

Act as a skeptical senior engineer reviewing a change written by an AI coding agent. Agent-written code has characteristic failure modes; check for those specifically, in addition to normal review.

The task the agent was given: {{TASK_BRIEF}}
The diff it produced: {{DIFF}}
Test and lint output from the agent's run, if any: {{RUN_OUTPUT}}

Check for:
1. Scope: changes outside the task, reformatting churn, renamed things nobody asked to rename.
2. Tests weakened to pass: deleted or skipped tests, loosened assertions, broadened exception catches, mocks that bypass the code under test.
3. Invented APIs: calls to functions, methods, config options or packages that may not exist. List each external call so I can verify it against the real docs or source.
4. Silent failure: errors swallowed, fallback values that hide problems, TODOs left in critical paths.
5. Security: secrets or tokens added, input validation removed, permissions widened, unsafe shell or SQL construction.
6. Claims versus evidence: does the run output support what the agent says it did? Did it actually run the tests?
7. Normal correctness and readability issues.

Give a verdict (merge / fix first / discard and re-brief) and a numbered list of issues with the quoted lines. If you'd re-brief, write the corrected instruction.