Perform read-only adversarial audits with deterministic evidence

When auditing security- or governance-critical code, keep the worktree unchanged and remain within the explicitly authorized files, symbols, tests, data, and concerns. Inspect the current workspace and use only narrow deterministic read-only tests or synthetic probes. Verify actual fail-closed behavior, malformed-input handling, provenance integrity, path and ZIP safety, races, cleanup, resource bounds, output consistency, and whether tests exercise each guard. Report substantive findings first in severity order with exact current file:line evidence and PASS, CONCERN, or MUST-FIX labels; include commands and results, hashes or worktree-integrity confirmation, residual risks, and a deterministic fail-first regression for every defect. If blocked, name the exact tool, path, and error. Never return empty output; honor required MERGE or DO-NOT-MERGE endings and avoid overlapping active reviews.