test(lifecycle): add UI surface coverage — HTTPS proxy + iframe URLs

Closes the coverage gap where existing bats suites would report green
on a node whose dashboard tiles 502 because the proxy upstream is dead.
First pass against .198 caught real prod issues immediately:
  /app/lnd/       → 502 (lnd container exited)
  /app/mempool/   → 502 (mempool container exited)
  /app/fedimint/  → 502 (fedimint container exited)
while existing tests reported only "container is up: false" with no
404/502 distinction.

* lib/ui-probes.bash — sourced helper. probe_https_200,
  probe_app_url (skip-if-container-down else assert-200),
  probe_dashboard_shell (asserts the Vue SPA HTML, not nginx default —
  catches the layout regression from feedback_release_tarball_layout.md),
  probe_dashboard_catalog (asserts /catalog.json non-empty).
* bats/ui-coverage.bats — 9 @test cases covering the dashboard +
  bitcoin-ui :8334 + the seven HTTPS_PROXY_PATHS most users hit
  (lnd, electrumx, mempool, fedimint, btcpay, filebrowser).

URL list mirrors HTTPS_PROXY_PATHS in
neode-ui/src/views/appSession/appSessionConfig.ts. Divergence between
the two is the exact bug class we're guarding against.

Loops clean under run-20x.sh. Container-state oracle is via local
podman inspect, so the suite must run on the archy host (same as
companion-survives-archipelago-restart.bats).

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

tests/lifecycle/bats/ui-coverage.bats

@@ -0,0 +1,93 @@
+#!/usr/bin/env bats
+# tests/lifecycle/bats/ui-coverage.bats
+#
+# UI surface tests — exercises the URLs a real user actually clicks
+# through, not just the JSON-RPC API. Fills the coverage gap where the
+# previous bats suites would report "container is up" while the iframe
+# behind /app/<id>/ was returning 502 because nginx had a stale upstream
+# or the proxy port was wrong.
+#
+# URL map sourced from neode-ui/src/views/appSession/appSessionConfig.ts
+# (the frontend's own resolveAppUrl). Tests here MUST stay in sync with
+# that file — divergence is the whole bug class we're guarding against.
+#
+# Each app probe is gated on its container being running:
+#   - container down  → skip (clean dependency report, no false-fail)
+#   - container up    → URL MUST return 200 with non-empty body
+#
+# Looped 20× via tests/lifecycle/run-20x.sh.
+
+load '../lib/rpc.bash'
+load '../lib/ui-probes.bash'
+
+setup_file() {
+  : "${ARCHY_PASSWORD:?Set ARCHY_PASSWORD env var to the UI password}"
+  export ARCHY_FORCE_LOGIN=1
+  rpc_login
+  unset ARCHY_FORCE_LOGIN
+  HOST="${ARCHY_HOST:-127.0.0.1}"
+  export HOST
+}
+
+teardown_file() {
+  rpc_logout_local
+}
+
+# ────────────────────────────────────────────────────────────────────
+# Dashboard shell + catalog (always required)
+# ────────────────────────────────────────────────────────────────────
+
+@test "dashboard https://host/ returns the Vue SPA shell" {
+  run probe_dashboard_shell
+  [ "$status" -eq 0 ]
+}
+
+@test "dashboard catalog endpoint responds with apps" {
+  run probe_dashboard_catalog
+  [ "$status" -eq 0 ]
+}
+
+# ────────────────────────────────────────────────────────────────────
+# Bitcoin UI — direct host port (8334), companion container
+# ────────────────────────────────────────────────────────────────────
+
+@test "bitcoin-ui is reachable on :8334 when archy-bitcoin-ui is running" {
+  probe_app_url archy-bitcoin-ui "http://$HOST:8334/" "bitcoin-ui (direct port 8334)"
+}
+
+# ────────────────────────────────────────────────────────────────────
+# HTTPS proxy paths — match HTTPS_PROXY_PATHS in appSessionConfig.ts
+# ────────────────────────────────────────────────────────────────────
+
+@test "lnd proxy https://host/app/lnd/ responds when lnd is running" {
+  probe_app_url lnd "https://$HOST/app/lnd/" "lnd (proxy /app/lnd/)"
+}
+
+@test "electrumx proxy https://host/app/electrumx/ responds when electrumx is running" {
+  # electrumx companion (archy-electrs-ui) is what serves the iframe HTML;
+  # the electrumx daemon is just the TCP backend.
+  probe_app_url archy-electrs-ui "https://$HOST/app/electrumx/" "electrumx (proxy /app/electrumx/)"
+}
+
+@test "mempool proxy https://host/app/mempool/ responds when mempool is running" {
+  probe_app_url mempool "https://$HOST/app/mempool/" "mempool (proxy /app/mempool/)"
+}
+
+@test "fedimint proxy https://host/app/fedimint/ responds when fedimint is running" {
+  probe_app_url fedimint "https://$HOST/app/fedimint/" "fedimint (proxy /app/fedimint/)"
+}
+
+@test "btcpay proxy https://host/app/btcpay/ responds when btcpay-server is running" {
+  probe_app_url btcpay-server "https://$HOST/app/btcpay/" "btcpay (proxy /app/btcpay/)"
+}
+
+@test "filebrowser proxy https://host/app/filebrowser/ responds when filebrowser is running" {
+  probe_app_url filebrowser "https://$HOST/app/filebrowser/" "filebrowser (proxy /app/filebrowser/)"
+}
+
+# ────────────────────────────────────────────────────────────────────
+# Companion-served URLs that aren't in HTTPS_PROXY_PATHS but show up
+# in the dashboard. archy-lnd-ui shares lnd's iframe path; archy-electrs-ui
+# shares electrumx's. The earlier test already covers those — leaving
+# this section for future companion-direct probes (none today).
+# ────────────────────────────────────────────────────────────────────