Security review (vpn-deploy)

The adversary controls the network path, inspects traffic metadata, and actively probes endpoints. Nodes are disposable; the repository plus SOPS secrets is the recovery key. Exposure through Git, state/plan dumps or logs can outlive the session and requires credential recovery. The hard rules in AGENTS.md define what is forbidden; this skill is how to check a diff against them.

Review everything being handed off: the committed range (git diff <base>...HEAD), staged and unstaged edits (git diff HEAD), and untracked files (git status --short). ...HEAD alone misses uncommitted work, so do not issue a verdict until all three are covered. Run the gates below that apply, and report a verdict: APPROVE, REQUEST CHANGES (fixable finding), or REJECT (the change's direction violates a hard rule, e.g. a CDN baseline, a public admin panel, or a cross-layer shortcut). Give file:line evidence for each finding.

Read the complete change in bounded pieces

First inventory each source of changes with --stat and --name-status: