review(redfix): re-confirmation #12 — merge-target staleness check, redfix-m2-harness tip == b5f2b10 (the M2-PASS sha); no finding, DONE stands, no VETO

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GUpGa1j9eAQ5jBLFdqFevZ

machine-docs/REVIEW-redfix.md

@@ -697,3 +697,25 @@ untouched (read-only `find`/`head`; probe worktree removed). B-redfix-5 remains
 non-blocking — unchanged by this probe.
 
 Terminal condition met (DONE + fresh PASS on every gate + no VETO). Loop stopped.
+
+### Post-reboot re-confirmation #12 @2026-07-09T01:18Z — DONE stands, no VETO. Merge-target staleness check: **clean**
+
+Re-checked the terminal predicate from artifacts, not from a prior wake's summary: `## DONE` present in
+STATUS-redfix.md; M1 PASS @2026-06-18T01:18Z + M2 PASS @2026-07-09T00:18Z; the `## VETO` heading is
+annotated CLEARED (F-redfix-4 CLOSED); no `machine-docs/ADVERSARY-INBOX.md`; no newer redfix phase plan.
+
+**New check this wake (not previously run): merge-target staleness.** The one way this terminal state could
+rot without any file changing is the Builder pushing to `redfix-m2-harness` *after* the M2 PASS was given
+against `b5f2b10` — the STATUS merge target would then name a sha that is no longer the branch tip, and the
+tip would carry unreviewed commits. Verified cold against the remote:
+
+    git ls-remote origin | grep redfix
+    → b5f2b104e6dd41f57521f98f2f8793ab523c6e6d  refs/heads/redfix-m2-harness
+
+The tip **is** `b5f2b10`, the exact sha the M2 PASS was given against and the exact sha STATUS-redfix.md
+names as the merge target. No post-PASS commits. The verified artifact and the merge target have not
+diverged.
+
+**Verdict: no new finding. DONE stands, no VETO.** Nothing claimed, nothing pending.
+
+Terminal condition met (DONE + fresh PASS on every gate + no VETO). Loop stopped.