diff --git a/machine-docs/REVIEW-redfix.md b/machine-docs/REVIEW-redfix.md
index 46dcca5..87554ae 100644
--- a/machine-docs/REVIEW-redfix.md
+++ b/machine-docs/REVIEW-redfix.md
@@ -753,3 +753,40 @@ 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.
+
+### Post-reboot re-confirmation #14 @2026-07-09T01:33Z — DONE stands, no VETO. **All-five-ref drift sweep: clean**
+
+Terminal predicate re-checked from artifacts, not from a prior wake's summary: `## DONE` @2026-07-09T00:18Z
+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.** Prior wakes staleness-checked the *recipe* branches (#4, 2026-07-08) and the
+*harness* branch (#12/#13, 2026-07-09) on different days — never both in one pass, so a same-day divergence
+between them had never been excluded. Swept all five refs cold from my own clone in a single pass:
+
+    mattermost-lts ci/pg-restore            4ca7f4182d837b1c73632841cf883fd9c0ba241b   == pinned 4ca7f418 ✔
+    gitea          ci/app-ini-writable      a0f2db8872a30a87443f4224956049d70c6139ad   == pinned a0f2db88 ✔
+    bluesky-pds    ci/warm-routing-alias    4987ba91c7bd716a988382a36fbb7c818044b729   == pinned 4987ba91 ✔
+    discourse      discourse-official-image ede639916c1f08e098767178e444f5edd8668363   (sha pin rotted — expected)
+    cc-ci          redfix-m2-harness        b5f2b104e6dd41f57521f98f2f8793ab523c6e6d   == the M2-PASS sha ✔
+
+**discourse re-verified by CONTENT, not sha** (per the STATUS evidence addendum: a later phase force-pushed
+the shared branch, so `9ff5e19`/`53ba0910` no longer resolve). I did not take the addendum's recorded
+re-check on trust — I re-ran the durable assertion cold against the live tip `ede63991` in a throwaway
+shallow clone:
+
+    git show FETCH_HEAD:compose.yml            | grep -m1 'image:.*discourse'  → image: discourse/discourse:3.5.3
+    git show FETCH_HEAD:compose.smtpauth.yml   | grep -c sidekiq               → 0
+
+Both hold: the official-image migration (M2's claim) and the F-redfix-1 orphaned-sidekiq removal are still
+present at the current head. Later-phase drift extended the branch without retracting either redfix fix.
+
+**"Nothing merged" clause re-verified:** `git merge-base --is-ancestor b5f2b10 origin/main` → exit 1, so the
+harness work is still unreachable from `origin/main`; `origin/main` carries only the two loops' coordination
+commits. The operator-gated merge has not happened.
+
+**Verdict: no new finding. DONE stands, no VETO.** Nothing claimed, nothing pending. Node untouched (all
+checks read-only: `ls-remote`, shallow fetch into scratchpad, `merge-base`; probe clone removed).
+B-redfix-5 remains open, deferred, non-blocking.
+
+Terminal condition met (DONE + fresh PASS on every gate + no VETO). Loop stopped.