inbox(2): consumed Adversary §7.1 response — agree my 3-failure env-block was premature (§7.1: transient flake≠blocker, ClickHouse boots 1-in-2); Adversary running 5-attempt plausible-full retry loop, staying OFF the node

machine-docs/STATUS-2.md

@@ -54,10 +54,12 @@ tree must carry:
 **ghost (Q4.4 ✅)**, mattermost-lts (Q4.5), uptime-kuma (Q4.8), mailu (Q4.9). Still open:
 - **lasuite-docs (Q3.1)** — ✅ Adversary PASS @2026-05-30 (REVIEW-2 `bb07242`). DONE.
 - **plausible (Q4.7)** — §4.3 floor Adversary-verified (REVIEW-2 `71af595`). Full upgrade/backup/restore
-  (P4) **ENV-BLOCKED @2026-05-30**: ClickHouse `events_db` cold-init crash-loops `exit(1)` on ~1-in-2
-  fresh deploys, persistent within a run — 3 consecutive install failures (q47/q47b/q47c) → stopped per
-  3-failure rule. Documented DECISIONS + DEFERRED 2026-05-30; **§7.1 env-blocker sign-off requested**.
-  Tests authored + correct; can't run when ClickHouse won't boot. Re-run when ClickHouse boot stabilises.
+  (P4): my "env-blocked after 3 failures" call was **PREMATURE** — Adversary correctly notes
+  (BUILDER-INBOX `f904f9b`) that per §7.1 a transient ~1-in-2 flake is NOT itself an env-blocker (ClickHouse
+  demonstrably boots here — `71af595`), so retries are the right response. **Adversary is running a 5-attempt
+  retry loop** of `RECIPE=plausible PR=0` (logs `/root/adv-q47-full-{1..5}.log`); ANY 5-tier-green attempt
+  PROVES Q4.7-full (no sign-off needed). My DECISIONS/DEFERRED env-blocker entries stand only if all retries
+  fail AND the ClickHouse file-based err log confirms a genuine env issue. **Node is the Adversary's — I'm OFF it.**
 - **drone (Q4.10)** — STILL BLOCKED @2026-05-30: rechecked, host `/etc/timezone` still absent (my
   declarative fix `3bde76f` needs an operator `nixos-rebuild` not yet applied) → gitea dep can't bind
   it. The running `drone_ci_commoninternet_net` stack is drone-ALONE (no gitea) — doesn't unblock.