# Managed tunnel status proof

Run independently in a checkout of each commit, after `vp i`, with a new isolated base directory and `T3CODE_DEV_SEED=0`. Load the provided T3 Connect test-stage environment; no production relay or real user data was used.

1. Run `node apps/server/src/bin.ts connect link --headless --base-dir <data>`, install the managed relay client when prompted, and approve its device login in the browser using the test account.
2. Run `node apps/server/src/bin.ts serve --base-dir <data> --port <port>`. Wait for four registered QUIC connections and the server's reachable message.
3. Stop that server without releasing its tunnel configuration (SIGKILL to its verified port-owning PID), then stop the exact relay child PID recorded in its log. A graceful stop releases the tunnel and removes its runtime config, which does not reproduce the reported starting state.
4. Move aside only `userdata/secrets/cloud-cli-desired-link.bin` and `userdata/secrets/cloud-cli-oauth-token.bin`. Leave the linked user id, relay credential, endpoint runtime configuration and confirmed origin in place.
5. Restart the same serve command and wait for four registered QUIC connections plus the server's reachable message.
6. Run `node apps/server/src/bin.ts connect status --base-dir <data>` and the same command with `--json` while that server remains running.

The screenshots and recordings are real GNOME Terminal sessions on Xvfb, 1920x1080, the same light terminal theme and 160x48 geometry. `capture.py` prints selected actual restart log lines, then executes both status commands live. It replaces only the isolated data path and test account id for privacy. Output fields and status wording are unchanged. The two final screenshots taken 500 ms apart had zero differing pixels on each side. Video frames and both final stills were inspected before upload.

`record-portable.sh` is the recording wrapper, with its scratch path made portable; `capture.py` is the actual capture driver. Pass side, checkout, relative data-directory name, relative restart-log name, and full commit SHA. Both files live beside the data and logs. The capture driver writes the transcript next to itself. No scenario was used because this is server/CLI output, not a web-client defect.

Base: ff8a83106773936314e527f116255e66df426a1f.
Head: bc4450a999a3f9903c5644a59565be6466990ac1.

After capturing, stop both servers, revoke both test environment links with `connect unlink`, restore the moved CLI token only for `connect logout`, then remove isolated data and checkouts.
