Correctness and security review passes

Run adversarial correctness and security/pentest as distinct passes so one discipline cannot obscure the other. Correctness review is mandatory for non-trivial work and every correctness-critical sync, hashing, lifecycle, or migration change; security review covers injection, credentials, privacy, protocol, authorization, and privilege escalation when the risk profile warrants it. Use real source and tests, break-state and failing-first regressions, apply/revert mutants, property tests ×10, hash equivalence, frozen-array mutation, and stale-cache checks. Report severity-ordered file:line PASS/FAIL/CONCERN/MUST-FIX evidence; frozen merge reviews end exactly MERGE or DO-NOT-MERGE.