Exact-candidate validation, adversarial review, and merge workflow

For every candidate review or scoped validation, freeze and record repository/worktree identity, immutable base/head/parent and ancestry, conflicts, changed-file scope, plain diff, supplied-file SHA-256s, artifact hashes, and workspace workers. Recheck afterward; mismatches, background edits, partial inspection, or unrestored mutations invalidate evidence. Stay read-only: no edits, formatting, VCS mutation, network/services, production data, or unapproved tests; use the temporary test database and jj in .jj/ repositories. Inspect every changed line and perform separate correctness and security/privacy passes across lifecycle, compatibility, rollback, cancellation, persistence, cleanup, accounting, and limits. Run prescribed focused-to-broad checks with sufficient timeout; use deterministic fail-first and targeted mutation regressions, restore mutations byte-for-byte, and verify hashes. Report substantive findings with exact evidence, smallest fixes, residual risks, and accurate infrastructure failures. Merge reviews require Burak Yigit Kaya’s authorization and must end exactly MERGE or DO-NOT-MERGE.