2 Commits

Include renames

Author	SHA1	Message	Date
archipelagoandClaude Opus 5	b2c7592840	security: parameterize node addresses; drop dead APP_URLS config ... Keeps the dev and test tooling an outside contributor would want, and takes our node addresses out of it. Scripts that silently defaulted to one of our nodes now require an explicit host and exit 2 without one: smoke-test.sh, trust-archipelago-cert.sh, dev-container-test.sh (which also derives its RPC and health URLs from the SSH target instead of a second hardcoded copy), and image-recipe/dev-branding.sh. A default that points at a machine the user does not own is worse than no default: it fails confusingly, or reaches a stranger's device. Usage examples, mock data and test fixtures move to the RFC 5737 documentation range (192.0.2.0/24). CGNAT test values stay inside 100.64.0.0/10 so the range-check semantics they exercise still hold, and 192.168.1.0/.1/.254 are left alone — those are gateway logic and UI placeholders, not our addresses. Playwright and the perf spec defaulted their baseURL to one of our nodes; they now default to localhost:8100, the local dev server. Removed neode-ui APP_URLS entirely. It is dead code — exported, never imported — and it pinned fedimint's *prod* launch URL to 192.168.1.228:8175. Had anything consumed it, every user's node would have tried to reach an address that on their LAN is either nothing or someone else's machine. Deleting beats sanitizing dead config. Verified: frontend 868/868 vitest across 108 files; archipelago-container 75/75; mesh tests 9/9; audit-secrets 5/5. Zero node addresses and zero node names remain in tracked files. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-07 10:53:25 -04:00
archipelagoandClaude Fable 5	380f4f1947	fix(tests): stop committing node passwords + bound multinode RPC calls (§H) ... - multinode suites no longer carry real node passwords as defaults: *_PW vars are required, auto-loaded from git-ignored tests/multinode/.env (lib sources it; .env.example documents the shape). Suites fail fast with a clear message when unset. - node_login/node_rpc get --connect-timeout 10 --max-time 120 (override: MULTINODE_RPC_TIMEOUT) so one hung server-side RPC can't stall the whole suite. Verified live: login+rpc against .116 OK; unroutable node fails in 10s instead of hanging. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-08 19:08:55 -04:00