# Live T3 Connect origin recovery proof

This is a server/HTTP reproduction, using the real T3 server, the authenticated test relay, and real cloudflared 2026.10.4. No service was mocked and no clocks were accelerated. The videos render the timestamped command output in session.cast; they are not browser screen recordings.

Each commit used its own checkout, installed dependencies, built web client, and fresh database. The same test account authorized each isolated environment. Both server runs listened on 127.0.0.1:3789 (3773 was already occupied). The server stayed alive throughout each observation.

1. Load the test-stage Connect variables and sign in using the CLI headless device flow.
2. Run `node apps/server/src/bin.ts connect link --headless --base-dir <isolated-home>` and accept the relay-client installation.
3. Build apps/web with the test-stage environment. Start `node apps/server/src/bin.ts serve --port 3789 --host 127.0.0.1 --base-dir <isolated-home>` with T3CODE_DEV_SEED=0.
4. Find the cloudflared metrics port belonging to the process started by that server. Wait for the remote descriptor endpoint to return 200 and four ready connections.
5. Run `PROOF_OUTPUT=<new-output-directory> node observe.mjs <isolated-home> <metrics-port> <Before-or-After> <commit>` with route.mjs beside observe.mjs.
6. The driver signs a valid origin-bound recovery proof using this isolated environment's own key and submits it with its own environment credential. It changes the live route to unused port 46169 without stopping the owner or connector. It samples ingress, readiness and remote descriptor HTTP status for about 110 seconds. HTTP 200 additionally verifies that the descriptor identifies this exact server; the descriptor body is not published because it contains the machine label.
7. Render the captured cast with `python3 render.py <output-directory>`. Videos are 1fps renderings of the recorded samples; they introduce no additional observations. The raw text and cast are included for inspection.
8. Stop each server, then run `connect logout --base-dir <isolated-home>` with the test-stage variables to revoke each test environment and remove its tunnel.

The initial setup and authentication contain secrets and are intentionally outside the recording. The preview browser returned Cloudflare 1033 despite successful command-line requests, so browser/WebSocket reconnection was not verified. The capture proves restoration of the live ingress and remote HTTP access. Failed-registration backoff and interval reset were not exercised.
