diff --git a/machine-docs/REVIEW-redfix.md b/machine-docs/REVIEW-redfix.md
index 3e52d04..46dcca5 100644
--- a/machine-docs/REVIEW-redfix.md
+++ b/machine-docs/REVIEW-redfix.md
@@ -719,3 +719,37 @@ 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.
+
+### Post-reboot re-confirmation #13 @2026-07-09T01:23Z — DONE stands, no VETO. **"Nothing merged" DoD clause verified cold — holds**
+
+Terminal predicate re-checked 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): the phase plan's "nothing merged" DoD clause.** Every prior
+re-confirmation exercised the *fix* clauses (recipes fixed, verified green, no standing exception) and the
+merge-target-staleness clause. None had ever falsified the negative clause — that the operator, not the
+Builder, does the merge. A Builder who self-merged `redfix-m2-harness` would leave STATUS-redfix.md and
+REVIEW-redfix.md word-for-word intact while violating the DoD, so the file-only predicate cannot see it.
+Verified against the remote from my own clone:
+
+    git ls-remote origin refs/heads/redfix-m2-harness
+    → b5f2b104e6dd41f57521f98f2f8793ab523c6e6d      (still the M2-PASS sha; staleness still clean)
+
+    git merge-base --is-ancestor b5f2b104e6dd… origin/main
+    → exit 1  ⇒  NOT an ancestor
+
+`b5f2b10` is **not** reachable from `origin/main`. Nothing from the redfix work has been merged; `origin/main`
+carries only the two loops' coordination commits (`review(redfix)` / `journal(redfix)`), no recipe or harness
+code. The DoD clause holds.
+
+**Corroborating disk check (re-run of #11's probe against REAL cc-ci state).** STATUS-redfix.md asserts
+"MIGRATION: none required … `ls -A /var/lib/ci-warm/keycloak/` → `last_good` only". Confirmed over ssh:
+`/var/lib/ci-warm/keycloak/` contains exactly `last_good`, and `/var/lib/ci-warm/` has no `canon-keycloak`
+entry yet (20 slots, none of them the new namespace). So the `canonical_ns` re-keying moves no existing file
+between slots, and the first post-merge keycloak run creates `canon-keycloak/` fresh. The migration-none
+claim is true against the live machine, not just against the code.
+
+**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.