1c/E2E-TESTME: clarify actor/critic — Builder swaps Adversary's W5 VM (ccci-w5-rebuild) after W5 PASS + recorded IP; Adversary doesn't rename

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

JOURNAL-1c.md

@@ -343,3 +343,13 @@ comments; pause it during the e2e (`docker service scale ccci-bridge_app=0` on t
 after). (b) the rebuilt VM's Drone needs the one-time OAuth bootstrap (install.md §2,
 scripts/bootstrap-drone-oauth.sh) before it can clone/build — a documented post-step, run it on the
 rebuilt VM as part of e2e setup. Still gated on C4/C5 PASS (W5) — not started.
+
+## 2026-05-27 — E2E-TESTME actor/critic split clarified (avoid node-rename collision)
+
+Orchestrator disambiguation: only ONE loop runs `tailscale set --hostname`. **Builder (me) owns the
+swap + the !testme test**; the swap TARGET is the **Adversary's** kept-running W5 VM (Incus instance
+**`ccci-w5-rebuild`**) — my own throwaway was destroyed. The **Adversary does NOT rename**; it keeps
+its W5 VM up, **records the VM identity (Incus instance + current tailscale IP) in REVIEW-1c/STATUS**,
+and independently VERIFIES E1-E6 cold (critic role). So I **WAIT for (i) Adversary W5 PASS + (ii) the
+recorded VM IP** before swapping (original→cc-nix-test-orig, then ccci-w5-rebuild→cc-nix-test). Updated
+STATUS-1c pending-e2e accordingly. Still gated on W5 — not started.