Local Adversarial Review Gauntlet

Falsify one immutable change through two independent perspectives, then return a bounded, mechanically assembled report within ten minutes. Greptile, Bugbot, and other remote PR reviewers remain outside this local gate.

Boundaries

• Start only from an explicit user request or a computa-please packet naming the risk, specialist lens, fixed point, target, Proof attestation, and prerequisite-commit authority.
• An explicit gauntlet request authorizes one prerequisite local commit for intended review-scope changes. A computa-please packet carries that authority; otherwise ask before committing. No invocation authorizes push, PR, remote comment, merge, or finding repair.
• The complete local operation, including preflight, reviewer termination, cleanup, and report assembly, has a 600-second wall-clock ceiling. Invoke the supervisor through a shell tool with a 600-second process-tree timeout; its internal deadline is 570 seconds.
• Run the supervisor once. It uses no Task jobs, nested reviewers, retries, or multipass Autoreview. A larger or deeper review is a separate explicit workflow.
• Treat every finding as a candidate until the caller verifies it against the code or a deterministic reproducer. Report-only execution leaves the target unchanged.

Freeze Target And Proof

1. Load vcs-detect; inspect status, staged and unstaged diffs, untracked files, branch, recent log, and Graphite state when available.
2. Select Git or Graphite through the repository workflow. Stage only the intended scope and create the authorized prerequisite commit when needed. The resulting commit is the target.
3. Resolve the fixed point and target to commit SHAs, compute their merge-base, record the target tree with git rev-parse <target>^{tree}, and stop when the triple-dot diff is empty.
4. Bind already-observed deterministic Proof to that exact target and tree in an owner-only temporary JSON file. Do not rerun fresh checks merely to populate the file; return to the Execution Gate when Proof is stale or incomplete.
5. Record the stated intent, applicable spec or contract, and one specialist lens: architecture, compatibility, reliability, or security. Material trust or security risk selects security; otherwise select the highest-consequence unresolved risk.