docs: multinode pass — cleared .198 preconditions, hit a real hardware blocker

Reset-failed 2 stale dead-unit records on .198, confirmed nginx lnd proxy
target is correct. Hit a genuine blocker needing a user decision: .198's
448GB disk is below the 1TB archival threshold so it runs pruned bitcoin,
currently only 21% through IBD — the multinode plan's precondition requires
pruned:false + fully synced.

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

docs/UNIFIED-TASK-TRACKER.md

@@ -64,12 +64,28 @@ those are marked ✅ below with the commit that did it, so we stop re-litigating
       sites for no concrete payoff. If boilerplate ever bothers us, extract a
       `usePolling()` composable instead — much cheaper than a query-cache migration.
 
-## Tier 2 — High effort, unblocked (the actual next exit criteria)
+## Tier 2 — High effort, mostly unblocked (the actual next exit criteria)
 
-- [ ] **Multinode test pass** (`docs/multinode-testing-plan.md`) — per-node
-      preconditions on .198 + rest of fleet, then 5× on-node gate per node, then
-      cross-node federation/mesh/transport suites. This is the literal "next exit
-      criterion" called out in `CLAUDE.md`.
+- [~] **Multinode test pass** (`docs/multinode-testing-plan.md`) — worked the
+      preconditions on .198 2026-07-01:
+  - ✅ cleared 2 stale failed-unit records (`archy-mempool-db.service`,
+    `meshtastic.service` — both `not-found`/dead since 6 and 5 days ago, harmless
+    bookkeeping, `systemctl --user reset-failed`).
+  - ✅ 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
+    "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
       2026-07-01). Flip needs: re-test on a healthy idle legacy node, then flip the