Perform scoped read-only adversarial audits with evidence-backed findings

When reviewing non-trivial changes, keep the audit strictly read-only: do not edit or format files, mutate VCS, access production data/services, or use the network. Stay within the explicitly assigned files and exclude areas owned by other reviewers. Investigate concrete correctness, security, portability, concurrency, accounting, fail-closed, and edge-case defects rather than offering broad commentary. Rank substantive findings by severity, cite exact file:line evidence, provide a concrete failure scenario, and suggest the smallest safe fix plus deterministic regression coverage. Regression tests should establish the real precondition, fail on the base branch, pass after the fix, and fail again if the relevant guard is removed. Use focused read-only tests only when permitted, distinguish genuine defects from already-covered behavior, and conclude with a clear merge verdict when requested.