diff --git a/machine-docs/JOURNAL-redfix.md b/machine-docs/JOURNAL-redfix.md
index fb351f7..b7033cb 100644
--- a/machine-docs/JOURNAL-redfix.md
+++ b/machine-docs/JOURNAL-redfix.md
@@ -1044,3 +1044,33 @@ artifact and merge target have not diverged. This is expected — I have pushed
 Nothing to act on: no verdict to answer, no finding to fix, no gate to claim. Terminal condition still met
 on every clause (`## DONE` + fresh M1/M2 PASS + no standing VETO). Loop remains stopped. `main.go` still
 untracked and unexplained (wakes #10–#13) — untouched.
+
+## Wake #15 — 2026-07-09T01:26Z — consumed review(redfix)@e9bd483 (re-confirmation #13, no finding); loop stays stopped
+
+Watchdog pinged on a `review(...)` commit. Pulled and read it: Adversary post-reboot re-confirmation #13.
+Its one genuinely new check is the phase plan's **negative "nothing merged" DoD clause** — the failure mode
+every prior re-confirmation was blind to, because a Builder who self-merged `redfix-m2-harness` would leave
+STATUS-redfix.md and REVIEW-redfix.md byte-for-byte intact. A file-only predicate cannot see that violation,
+so it had to be checked against the remote. Good catch on the gap; the clause holds.
+
+Re-derived both of its claims from my own clone rather than trusting the verdict text:
+
+    git rev-parse --short origin/redfix-m2-harness            -> b5f2b10   (== M2-PASS sha; staleness clean)
+    git merge-base --is-ancestor b5f2b104e6dd… origin/main    -> exit 1    (NOT an ancestor => not merged)
+    # and, stronger than the Adversary checked: no commit in origin/main's last 20 touches any path
+    # outside machine-docs/ — main carries only review(redfix)/journal(redfix) coordination commits.
+
+The merge remains the operator's to make, as the phase plan requires. I have pushed nothing to
+`redfix-m2-harness` since the F-redfix-4 remedy.
+
+Terminal condition re-checked from artifacts, not from wake #14's summary: `## DONE` at STATUS-redfix.md:10;
+M1 PASS + M2 PASS (F-redfix-4 CLOSED); the sole `## VETO` heading is annotated CLEARED and is therefore not
+standing; no `machine-docs/BUILDER-INBOX.md`. Nothing claimed, nothing pending, no finding to fix.
+Loop remains stopped.
+
+`main.go` (repo root, untracked, 16-line "Hello, World!" Go HTTP server, mtime 2026-07-09T00:01) is still
+present and still unexplained — carried forward from wakes #10–#14. It is not mine, is not referenced by any
+recipe, harness, or Nix module, and is not a coordination file, so the FILE-LOCATION RULE does not apply to
+it. I am deliberately NOT deleting it: I did not create it, and a stray file I cannot account for is
+information, not litter. It cannot affect the DoD (untracked => absent from the Adversary's cold clone).
+Surfaced to the operator instead.