Audit Code

Find concrete failures in the requested change and its affected paths. Use security, performance, UX, DX, and edge cases as review lenses, not a requirement to launch five agents or repeat the entire audit. Prefer a few demonstrated findings over a long list of hypothetical improvements.

Scope and authority

Before reviewing, establish a compact mission contract, or reuse the current one when it covers the same scope:

• Demonstrated failure or requested outcome, acceptance criteria, and affected paths.
• Explicit non-goals and whether the task permits edits or is review/plan only.
• Expected footprint, runtime context, and evidence that requires external access.

Classify each concern: