docs: multinode pass swapped to .5, 5x gate launched

.198 IBD/pruned blocker → user chose swap over wait/hardware. .116 ruled
out (no bitcoin container), .120 ruled out (reserved for another dev). .5
(archy-x250-beta) is fully synced despite also being sub-1TB/pruned;
bootstrapped bats+jq and launched the 5x destructive gate there.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

docs/UNIFIED-TASK-TRACKER.md

@@ -74,17 +74,18 @@ those are marked ✅ below with the commit that did it, so we stop re-litigating
   - ✅ nginx `/app/lnd/` proxy target confirmed correct (→ `18083`, matches the
     running `archy-lnd-ui` port) — the plan's "stale proxy target" concern doesn't
     apply here.
-  - ⛔ **HARD BLOCKER, needs your decision**: .198 has only 448GB disk — below the
-    1TB threshold the bitcoin container hardcodes for archival mode — so it runs
-    **pruned**, and is only **21% through IBD** (507,516/956,238 blocks) as of
-    2026-07-01. The plan's precondition requires `pruned:false` + fully synced.
-    Options: (a) add storage to .198 and let it resync archival, (b) let it finish
-    pruned IBD and treat the multinode gate's bitcoin precondition as
-    pruned-acceptable for this node specifically, or (c) pick a different second
-    node for the multinode pass. **I can't decide this for you** — it's a
-    time/hardware tradeoff.
-  - Once unblocked: run the on-node gate 5× on .198, then the rest of the fleet,
-    then the cross-node federation/mesh/transport suites. This is the literal
+  - ⛔ .198 disk (448GB) is below the 1TB archival threshold + was only 21%
+    through IBD — user chose to **swap in a different node** rather than wait/add
+    storage. **.116 ruled out** (no bitcoin container installed at all, just the
+    UI companion). **.120 ruled out** (reserved for another developer). **.5**
+    (archy-x250-beta, Tailscale `100.72.136.5`) chosen: also sub-1TB (472GB, so
+    still pruned — that ceiling is shared by every non-.228 node), but **fully
+    synced** (`ibd:false`, blocks==headers 956,240). Bootstrapped bats 1.11.1 +
+    jq 1.7.1 onto it 2026-07-01 and **launched the 5× destructive gate
+    (`ARCHY_ITERATIONS=5 ARCHY_ALLOW_DESTRUCTIVE=1`) — running now**, log at
+    `/tmp/gate.log` on .5, background poller watching for the `RESULTS` banner.
+  - Once .5's gate reports: bring the rest of the fleet to precondition, then the
+    cross-node federation/mesh/transport suites. This is the literal
     "next exit criterion" called out in `CLAUDE.md`.
 - [ ] **Phase-3 Quadlet default-flip** — code is validated + opt-in via
       `ARCHIPELAGO_USE_QUADLET_BACKENDS=true` on .228/.198 already (confirmed live