1c/E2E-TESTME: swap ACTIVE — public gateway → rebuilt VM (P1/P2 verified); recording reversible state + swap-back steps

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

STATUS-1c.md

@@ -75,6 +75,16 @@ See JOURNAL-1c 2026-05-27 W2a entry for full evidence.
 - [ ] C6 — Resource fit + cleanup (cc-nix-test 6→4 GB, throwaway 4 GB, destroyed after; final sizing decided)
 - [ ] C7 — Docs (install.md/secrets.md/architecture.md + main plan refs updated to new model)
 
+## 🔴 SWAP ACTIVE (2026-05-27 ~19:25Z) — public gateway points at the REBUILT VM (reversible)
+**State:** `cc-nix-test` (MagicDNS) → **`100.97.167.73`** (rebuilt `ccci-w5-rebuild`); original cc-ci
+renamed `cc-nix-test-orig` @ `100.90.116.4`, **still running** (swap-back target). Public
+`ci.commoninternet.net` now served by the rebuilt VM (P2 verified 200/ssl_verify=0). Doing E2E-TESTME.
+**`ssh cc-ci` (pinned 100.90.116.4) = the ORIGINAL** (cc-nix-test-orig); reach the rebuilt VM via
+`100.97.167.73` or `cc-nix-test` MagicDNS.
+**SWAP-BACK when e2e done:** rebuilt VM → `tailscale set --hostname=ccci-w5-rebuild`; then
+`ssh cc-ci 'tailscale set --hostname=cc-nix-test'`; restore original's bridge (`docker service scale
+ccci-bridge_app=1` on the original — paused during e2e to avoid dual-trigger). Keep both VMs running.
+
 ## ⚠️ Operator override — do NOT destroy the FINAL throwaway VM (read before W5/W6 cleanup)
 The operator (2026-05-27) will **repurpose the final W5/C4-C5 clean-room throwaway VM as the new
 cc-nix-test** for a live real-traffic test. So: **KEEP that VM running after W5 PASSes — do NOT tear