testing: rename vps-chi to test-us01 in tor socks5-outbound scaffold

The host (217.77.8.91:443) was renamed to test-us01 some time ago
(canonical name shared with packaging/common/hosts and the docs);
the test scaffold's alias labels and narrative comments hadn't been
updated. Pure naming cleanup, no behavior change. The continued
dependency on the live external host is tracked separately.

testing/tor/socks5-outbound/configs/node-a.yaml.tmpl

@@ -1,6 +1,6 @@
 # FIPS Tor test node A — socks5-outbound
 #
-# Connects outbound to vps-chi (217.77.8.91:443) via Tor SOCKS5 proxy.
+# Connects outbound to test-us01 (217.77.8.91:443) via Tor SOCKS5 proxy.
 # Identity generated per-run to avoid mesh clashes with parallel tests.
 
 node:
@@ -21,7 +21,7 @@ transports:
 
 peers:
   - npub: "npub1qmc3cvfz0yu2hx96nq3gp55zdan2qclealn7xshgr448d3nh6lks7zel98"
-    alias: "vps-chi"
+    alias: "test-us01"
     addresses:
       - transport: tor
         addr: "217.77.8.91:443"

testing/tor/socks5-outbound/configs/node-b.yaml.tmpl

@@ -1,6 +1,6 @@
 # FIPS Tor test node B — socks5-outbound
 #
-# Connects outbound to vps-chi (217.77.8.91:443) via Tor SOCKS5 proxy.
+# Connects outbound to test-us01 (217.77.8.91:443) via Tor SOCKS5 proxy.
 # Identity generated per-run to avoid mesh clashes with parallel tests.
 
 node:
@@ -21,7 +21,7 @@ transports:
 
 peers:
   - npub: "npub1qmc3cvfz0yu2hx96nq3gp55zdan2qclealn7xshgr448d3nh6lks7zel98"
-    alias: "vps-chi"
+    alias: "test-us01"
     addresses:
       - transport: tor
         addr: "217.77.8.91:443"

testing/tor/socks5-outbound/docker-compose.yml

@@ -1,10 +1,10 @@
 # Tor transport integration test — socks5-outbound
 #
 # Topology:
-#   [fips-a] --tor/socks5--> vps-chi (217.77.8.91:443) <--tor/socks5-- [fips-b]
+#   [fips-a] --tor/socks5--> test-us01 (217.77.8.91:443) <--tor/socks5-- [fips-b]
 #
 # Both FIPS nodes connect outbound through a local Tor daemon's SOCKS5
-# proxy to vps-chi's TCP listener. vps-chi routes between them.
+# proxy to test-us01's TCP listener. test-us01 routes between them.
 # Ping between fips-a and fips-b validates the full Tor transport path.
 
 networks:

testing/tor/socks5-outbound/scripts/tor-test.sh

@@ -2,11 +2,11 @@
 # Tor transport integration test.
 #
 # Validates end-to-end connectivity through a real Tor network:
-#   fips-a --tor/socks5--> vps-chi <--tor/socks5-- fips-b
+#   fips-a --tor/socks5--> test-us01 <--tor/socks5-- fips-b
 #
 # Both local FIPS nodes connect outbound through a local Tor daemon
-# to vps-chi's TCP listener (217.77.8.91:443). Once both are peered
-# with vps-chi, traffic between fips-a and fips-b is routed through it.
+# to test-us01's TCP listener (217.77.8.91:443). Once both are peered
+# with test-us01, traffic between fips-a and fips-b is routed through it.
 #
 # Each run generates ephemeral identities to avoid mesh clashes when
 # multiple instances of this test run concurrently.
@@ -107,7 +107,7 @@ fi
 echo ""
 
 # ── Phase 3: Wait for FIPS peers via Tor ─────────────────────────
-echo "Phase 3: Waiting for FIPS nodes to peer with vps-chi via Tor (up to ${MAX_WAIT_PEER}s)..."
+echo "Phase 3: Waiting for FIPS nodes to peer with test-us01 via Tor (up to ${MAX_WAIT_PEER}s)..."
 echo "  (First SOCKS5 attempt may timeout while Tor builds circuits)"
 
 peers_a=0
@@ -199,7 +199,7 @@ print(f'{sum(trimmed)/len(trimmed):.1f}')
 }
 
 echo ""
-echo "  Ping via Tor (routed through vps-chi):"
+echo "  Ping via Tor (routed through test-us01):"
 ping_series fips-tor-a "$NPUB_B" "A → B"
 ping_series fips-tor-b "$NPUB_A" "B → A"