journal(redfix): wake #35 — why the ping was not a no-op; STATUS omitted B-redfix-8

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

machine-docs/JOURNAL-redfix.md

@@ -1600,3 +1600,34 @@ operator-rotation-only. `main.go` still untracked at repo root — not created b
 
 This is the last journal entry for phase `redfix`. The phase is DONE; the loop is stopping and will not
 self-reschedule. Further reboots that find this state should stop immediately rather than re-journal.
+
+## Wake #35 — watchdog ping on review(redfix)@55899e6; found a real gap in STATUS and closed it
+
+The Adversary's verdict was "no VETO, terminal condition intact" — on its face a no-op, and my last four
+wakes had correctly refused to manufacture work out of one. But I read the finding it re-probed instead of
+pattern-matching on the verdict, and that surfaced something none of the previous no-op wakes had noticed:
+
+**`STATUS-redfix.md` never mentioned B-redfix-8.** The finding lived in BACKLOG, REVIEW, and JOURNAL. STATUS
+— the artifact an operator actually opens — carried `## DONE` and nothing else. So the single action this
+phase requires from a human (rotate the leaked Gitea bot password) was invisible in the one place a human
+looks. "DONE with a HIGH credential leak open" reads as "DONE" if the leak isn't on the page.
+
+That is not noise-work, and the distinction is the point: the previous wakes were right to skip re-probing
+B-redfix-8 (duplicate measurement), and this wake was right to act (missing artifact). The trigger for work
+is a gap between what's true and what's recorded — not the arrival of a ping.
+
+Added an `## ⚠ OPERATOR ACTION REQUIRED` block to STATUS with WHAT / WHERE / HOW / EXPECTED + remedy, kept to
+the STATUS layer (no rationale — this file is it). Re-ran both repro commands first rather than copying them
+forward, because a stale repro in the operator's file is worse than no repro, and this exact item already ate
+one transcription slip (33080 → 33408, caught by the Adversary at re-confirmation #22):
+
+    $ git cat-file -s 14c7dee:machine-docs/BACKLOG-redfix.md
+    33408
+    $ python3 -c '...sha256(GITEA_PASSWORD)[:16]...'
+    3fcea78925015fc9
+
+Both match. The credential is still unrotated and still served. No DoD item touched, no gate claimed, no
+verdict change: M1+M2 PASS stand, `## DONE` stands, no VETO. B-redfix-8 stays OPEN, HIGH, operator-only —
+I cannot rotate a Class-A1 input (§4.4) and cannot rewrite published history (`--force` forbidden), so
+rotation by the operator is the only thing that revokes the exposure. `main.go` still untracked, still not
+mine to delete. Loop stops again.