status+journal(2w): W1 gate WC2+WC3 ADVERSARY PASS @2026-05-29; advance to W2 (--quick mode)

machine-docs/JOURNAL-2w.md

@@ -250,3 +250,20 @@ bounded). Did NOT enroll a 2nd recipe yet (custom-html suffices for W2 --quick +
 
 Parked at the W1 gate. While awaiting: will do non-disruptive W0.10b (alert-relay) — NOT the traefik
 W0.10a migration (it disrupts TLS the Adversary needs to verify the data-warm round-trip through).
+
+## 2026-05-29 — W1 gate WC2+WC3 ADVERSARY PASS; advancing to W2 (--quick)
+
+Adversary cold-verified WC2+WC3 from its own clone (REVIEW-2w 0246296): 61 units; its OWN data-warm
+round-trip (deploy→write ADV marker→undeploy-keep-volume→redeploy→marker survived, Builder's known-good
+also reattached); its OWN WC3 restore round-trip (mutate→restore→exact known-good content back,
+mutation gone). Its 2 crashes were its own driver-script bugs, not product defects. Canonical left
+clean. **WC2 + WC3 PASS @2026-05-29.** Same coordination lag as the W0 claim (its watchdog pinged on a
+pre-claim read; resolved via ADVERSARY-INBOX). traefik WC1.1 (W0.10a) remains the sole tracked-open
+before DONE.
+
+**Advancing to W2 (--quick, WC4+WC7).** Design: a `--quick` opt-in path in run_recipe_ci.py that
+consumes the canonical (reattach → upgrade-to-PR-head → assert → PASS keep-volume / FAIL
+restore-snapshot, NEVER promote), tagging results mode=quick, with a clean no-canonical fallback to
+cold. Will study the existing upgrade-tier chaos-to-PR-head (HC1) mechanism, then add the quick flow +
+units + a live proof on the custom-html canonical (the deliberately-fail-restores-known-good case is
+also the WC9 rollback-proof preview).