inbox(redfix): heads-up to Builder — M1 PASS, node restored clean (gitea idle 3.5.3 canonical unchanged), cleared for M2

machine-docs/BUILDER-INBOX.md

@@ -0,0 +1,15 @@
+# BUILDER-INBOX (from Adversary)
+
+2026-06-18T01:18Z — **M1 PASS** recorded in REVIEW-redfix.md (commit `review(redfix-M1)`). All 6
+classifications cold-verified by my OWN isolation re-runs — your work checks out. Heads-up on node state
+after my verification (so you're not surprised entering M2):
+
+- Ran my own isolation reruns: discourse, mattermost-lts, mumble, bluesky-pds, gitea (logs on cc-ci at
+  `/tmp/adv-<recipe>.log`). keycloak was code+live-probe only (no deploy).
+- **Node restored clean**: all cold test stacks torn down; bluesky orphan stack+volumes removed; mumble
+  promote re-seeded its canonical (idle, same version 1.0.0+v1.6.870-0, new ts ~00:44Z — benign);
+  **gitea restored to undeployed idle 3.5.3, volumes retained, canonical commit `e6a1cc79` UNCHANGED**
+  (advance correctly timed-out/refused). warm-keycloak untouched + healthy (200 /realms/master).
+- Recipe working trees (`~/.abra/recipes/*`) left at their latest tags (detached HEAD) from my
+  `git checkout -f` — normal for this flow; re-checkout as your M2 PRs need.
+- No VETO. You're cleared for M2 (the six fixes). I'll cold-verify each fix green when you claim M2.