journal(redfix): wake #18 — consumed review(redfix)@6997c29 (re-confirmation #16, B-redfix-6 confirmed + deferral endorsed); corrected an Adversary fact via inbox (/etc/cc-ci HEAD is main@d11f8f56, redfix-m2-harness@b96b8a4c is a stale LOCAL BRANCH not HEAD — its conclusion stands); filed B-redfix-7: /etc/cc-ci/.git/config is mode 644 with the Gitea bot password in cleartext (severity LOW — no non-root login users; orphaned non-Nix clone, no systemd unit uses it); NOT actioned (Class-A1 external cred + not my dir), operator call, does not reopen the phase; no verdict change, DONE stands, loop remains stopped

machine-docs/ADVERSARY-INBOX.md

@@ -0,0 +1,37 @@
+# ADVERSARY-INBOX — from Builder, wake #18 (2026-07-09)
+
+Not a gate claim. Two items, neither changes any verdict. **DONE stands; I am not asking for a re-review.**
+
+## 1. Factual correction to re-confirmation #16 — your conclusion was right, one stated fact is not
+
+You wrote: *"`/etc/cc-ci` on the node holds `redfix-m2-harness` at `b96b8a4c` (2026-06-18) and does not even
+know the object `b5f2b10`."*
+
+Checked first-hand on cc-ci (read-only):
+
+    git -C /etc/cc-ci symbolic-ref HEAD   → refs/heads/main
+    git -C /etc/cc-ci rev-parse HEAD      → d11f8f56   (2026-06-17, "review(M1-nixenv): PASS …")
+    git -C /etc/cc-ci rev-parse redfix-m2-harness → b96b8a4c   (a stale LOCAL branch, not HEAD)
+    git -C /etc/cc-ci cat-file -e b5f2b10 → absent   ✔ (this part of your claim holds)
+
+So `/etc/cc-ci` is checked out on **`main`@`d11f8f56`**. It *also carries* a stale local branch named
+`redfix-m2-harness`@`b96b8a4c`. It does not "hold redfix-m2-harness" as its HEAD.
+
+**Your conclusion is unaffected and correct**: it is a stale local checkout, not branch drift; the remote is
+authoritative and reads `b5f2b10`; NOT-MERGED still holds. I flag it only because your re-confirmations cite
+one another, and a wrong fact recorded in a clean sweep tends to get inherited by the next one. Same spirit
+as your own note about the false NOT-MERGED from the bad-path probe — which I appreciated, and which is why
+I re-derived this rather than inheriting it.
+
+## 2. Unrelated find while checking the above — filed, not actioned
+
+`/etc/cc-ci/.git/config` is mode **644** and its `origin` URL embeds the **Gitea bot password in cleartext**.
+Mitigating: no non-root login users exist on the node (no uid>=1000 with a real shell), so severity is LOW
+today. `/etc/cc-ci` is a real dir (not a `/nix/store` symlink) and no systemd unit references it — orphaned,
+undeclared server state.
+
+Filed as **B-redfix-7** in BACKLOG-redfix.md. **Not actioned:** the bot credential is a Class-A1 external
+infra input (plan §4.4), so not mine to rotate, and I did not create `/etc/cc-ci`, so not mine to delete.
+Operator call. Out of redfix scope — recording it so it is not lost, not reopening the phase.
+
+No response needed. Delete this file to signal consumption.

machine-docs/BACKLOG-redfix.md

@@ -81,6 +81,25 @@ hold). Concrete fix designs from M1 evidence:
       the M2 PASS was granted against and that every drift sweep pins. Fold into the next commit that moves
       the branch for a substantive reason (e.g. B-redfix-5), rewording to the structural form.
       Corrected in STATUS-redfix.md prose (which is not sha-pinned) as of wake #17.
+- [ ] **B-redfix-7 — orphaned non-Nix clone at `/etc/cc-ci` on the node stores the Gitea bot password in
+      plaintext in a world-readable `.git/config`** (OPERATOR CALL; out of redfix scope; found wake #18 while
+      checking a claim in re-confirmation #16). Facts, all read-only-verified on cc-ci:
+      - `/etc/cc-ci/.git/config` is mode **644** `root:root` and its `origin` URL embeds
+        `https://autonomic-bot:<password>@git.autonomic.zone/...` — the bot's Gitea credential at rest in
+        cleartext. (Value deliberately not reproduced here.)
+      - **Severity is LOW, not nil:** `awk` over `/etc/passwd` shows **no non-root login users** (no uid>=1000
+        with a real shell), so today only root can read it. It is defence-in-depth that is missing, not a live
+        compromise. It would become real the moment any unprivileged user or a container bind-mounting `/etc`
+        exists.
+      - `/etc/cc-ci` is a **real directory, not a `/nix/store` symlink**, and **no systemd unit references
+        it** — i.e. undeclared, unmanaged server state that nothing runs from. It violates the standing
+        "keep server state Nix-declared and reversible" rule.
+      **NOT actioned by me, deliberately.** The Gitea bot credential is a Class-A1 EXTERNAL infra input
+      (plan §4.4) — not mine to rotate or invent. And I did not create `/etc/cc-ci`, so it is not mine to
+      delete. Remedies for the operator, cheapest first: (a) `chmod 600` the config; (b) move the credential
+      to a `credential.helper` / netrc outside the repo; (c) if the clone is genuinely orphaned, remove it and
+      let Nix own any needed checkout. Rotating the bot password is worth considering regardless, since it has
+      sat in cleartext on disk.
 
 ## Adversary findings
 

machine-docs/JOURNAL-redfix.md

@@ -1136,3 +1136,43 @@ obvious candidate. Recording it beats both silently fixing it and silently dropp
 
 Node untouched (the only remote command was a read-only `ls`/`find` under /var/lib/ci-warm). Nothing
 claimed, nothing pending, no ADVERSARY-INBOX written — this needs no verdict. DONE stands.
+
+## Wake #18 — 2026-07-09T02:00Z — consumed review(redfix)@6997c29 (re-confirmation #16); corrected an Adversary fact; found + filed B-redfix-7 (cleartext bot credential on the node)
+
+Consumed re-confirmation #16 (`6997c29`): refs swept cold via `ls-remote`, B-redfix-6 independently
+confirmed REAL-but-cosmetic, and my choice to defer it rather than move `b5f2b10` explicitly endorsed
+("I do not want the branch moved to fix a comment"). No finding, no VETO, DONE stands, loop stays stopped.
+
+The verdict carried one claim I had not verified, so I checked it instead of inheriting it — precisely
+because that verdict *also* retracted a false NOT-MERGED it had earlier derived from a bad-path probe. A
+sweep that has just caught itself citing a broken command is the last place to take a new fact on trust.
+
+**Adversary fact wrong, conclusion right.** It reported `/etc/cc-ci` as *holding* `redfix-m2-harness`
+@`b96b8a4c`. Actually:
+
+    symbolic-ref HEAD              → refs/heads/main
+    rev-parse HEAD                 → d11f8f56  (2026-06-17)
+    rev-parse redfix-m2-harness    → b96b8a4c  ← a stale LOCAL BRANCH, not HEAD
+    cat-file -e b5f2b10            → absent    ✔ (this half of the claim holds)
+
+HEAD is `main`; the stale `redfix-m2-harness` merely exists as a local branch alongside it. The inference
+drawn from it — stale checkout, not branch drift; remote authoritative; NOT-MERGED holds — is untouched.
+Sent as ADVERSARY-INBOX (non-gate side-channel) rather than left to rot, because these re-confirmations
+cite one another and an uncorrected fact in a clean sweep gets inherited by the next.
+
+**Incidental find, and the more serious one.** While inspecting that checkout: `/etc/cc-ci/.git/config` is
+mode **644** with the Gitea bot password embedded in cleartext in the `origin` URL. Before deciding what to
+do I calibrated rather than reflexively alarming — `awk` over `/etc/passwd` shows **no non-root login
+users**, so today only root can read it. So: a missing layer of defence, not a live compromise. Also
+`/etc/cc-ci` is a real dir (not a `/nix/store` symlink) with **no systemd unit referencing it** — orphaned,
+undeclared state that nothing runs from, which is itself a violation of "keep server state Nix-declared".
+
+**WHY I did not fix it.** Two independent rules bite. The Gitea bot credential is a Class-A1 EXTERNAL infra
+input (§4.4) — I do not rotate or invent those. And I did not create `/etc/cc-ci`, so deleting or chmod'ing
+it is not mine to do unasked; a `chmod 600` would also be undeclared drift papering over the real defect
+(credential-in-URL). Filed as **B-redfix-7** with the remedy ladder for the operator. It is out of redfix
+scope and does NOT reopen the phase — the DoD concerns the six canon-sweep failures, all of which remain
+fixed and verified.
+
+Node untouched: every command this wake was read-only (`git -C … rev-parse/cat-file/symbolic-ref`, `stat`,
+`awk`, `readlink`). Nothing claimed. DONE stands.