diff --git a/machine-docs/JOURNAL-redfix.md b/machine-docs/JOURNAL-redfix.md
index 1d19cc7..0fbaf51 100644
--- a/machine-docs/JOURNAL-redfix.md
+++ b/machine-docs/JOURNAL-redfix.md
@@ -2100,3 +2100,26 @@ Left untouched: I did not create it, so per the guardrails I neither commit nor
 **Nothing for the Builder to do.** All three outstanding actions are the operator's: merge
 `redfix-m2-harness` @ `b5f2b10`, merge the four recipe PRs, and rotate `GITEA_PASSWORD` + strip the userinfo
 via `git remote set-url origin` (do not re-embed). Loop remains stopped.
+
+## Wake #52 — 2026-07-09 — Builder reboot on closed phase; terminal state re-verified; loop STOPPED
+
+Third consecutive watchdog reboot onto a phase that is already closed (cf. wakes #50, #51). Re-verified
+the terminal state cold before acting, rather than assuming the prior wakes' conclusions:
+
+- `grep -c '^## DONE' machine-docs/STATUS-redfix.md` → `1`.
+- `grep -c '^## VETO' machine-docs/REVIEW-redfix.md` → `2`, which on inspection are **both historical**:
+  L553 `## VETO [CLEARED @2026-07-09T00:18Z … NOT standing]` and L649 `## VETO CLEARED @2026-07-09T00:18Z
+  (F-redfix-4)`. **No standing VETO.** Noting this because a naive `grep -c '^## VETO'` on this file returns
+  a non-zero count forever — any future automated stop-condition check must read the headings, not count them.
+- M1 PASS @2026-06-18T01:18Z, M2 PASS @2026-07-09T00:18Z; Adversary closed its own loop at wake #49.
+- Working tree clean but for the untracked `main.go`, already flagged in STATUS as unexplained/inert and
+  left in place per guardrails (do not delete/commit files I did not create).
+
+Open items (**operator-only**, neither blocks `## DONE`, no DoD item depends on them):
+A-redfix-1 + B-redfix-8 — one live push-capable Gitea credential exposed two ways; sentinel
+`3fcea78925015fc9` last probed unrotated. Merge target is `redfix-m2-harness`@`b5f2b10`, never `07fc6d4`.
+
+Per the standing rule "Stop the loop only when STATUS.md says ## DONE" — it does, with a fresh Adversary
+PASS on every DoD item and no standing VETO. Re-waking cannot advance operator-only work. **Stopping the
+loop via ScheduleWakeup(stop) instead of scheduling wake #53.** Nothing further to build; a future merge or
+new phase should start a fresh loop that cold-verifies against the then-current tree.