# Real-server proof for PR 26040

Surface: Linux x86_64, Node CLI (`node apps/server/src/bin.ts serve`), loopback HTTP, isolated T3 homes, dedicated T3 Connect test-stage relay and test account. No production state or model turns. Fresh databases were created by each commit; the same driver restarted each side across three cases.

Base: [eb14ddb799](https://github.com/pingdotgg/t3code/commit/eb14ddb79924a6cbcb6c26d1b97c9816c9732c55).
Head: [6d083ef66a](https://github.com/pingdotgg/t3code/commit/6d083ef66a08adb2b2007a2292928a35bfd50ecb).

## Preparation

Install dependencies in each checkout with `vp i`. Load the dedicated test-stage environment, and authenticate each isolated home with `node apps/server/src/bin.ts connect login --headless --base-dir "$HOME_FOR_CASE"`. Enable T3 Connect with `connect link --headless --base-dir "$HOME_FOR_CASE"`; accept the managed installation prompt when shown. Only the test OAuth credential was copied between the newly created test homes, with no copied database.

Download the official [cloudflared 2026.9.3 Linux amd64 binary](https://github.com/cloudflare/cloudflared/releases/download/2026.9.3/cloudflared-linux-amd64), mark executable, and verify `--version`: `cloudflared version 2026.9.3 (built 2026-09-24-16:07 UTC)`. SHA256: `77e26d8d900e0b8469f416239d14b5f296525fdf79fee6f511ef55609e3fbac2`.

## Driver

`python3 driver.py "$WORKTREE" "$HOME_FOR_CASE" base-or-head "$NEW_ARTIFACT_DIRECTORY" "$OLD_BINARY"`

1. Remove any managed pin from selection by moving it into the artifact directory. Leave the explicit override unset, prepend the official old binary's directory to PATH, and start the real server. Capture its selected source/version and tunnel registration.
2. Stop the owned server process group. Move any newly installed pin aside, set `T3CODE_CLOUDFLARED_PATH` to the same old binary, and restart. Capture selection or refusal. Also run the real `connect status --json` command with this override; retain only `relayClient` in public evidence.
3. Stop the server. Move the pin aside, unset the override, restore the original PATH (no eligible cloudflared), and copy the official old binary into `tools/cloudflared/2026.9.3/linux-x64/cloudflared` under that isolated home. Restart. Capture the order of installation and connector starts.
4. Stop every server and run `connect logout --base-dir "$HOME_FOR_CASE"` to revoke the test environment and clear authorization.

The stage initially refused head provisioning at its three-tunnel quota. Revoking the finished base environment freed capacity; head's successful rerun is the one published here.

## Captures

The PNGs and MP4s render privacy-filtered **actual server stdout**, rather than screenshots of the web UI. They preserve event order and actual elapsed timestamps; idle waits are compressed in the videos. `render.py` selects relevant lines and omits tokens, paths, account details, process IDs, tunnel IDs/names and IPs. Each side uses the same 1440×900 terminal rendering and theme. Text transcripts contain the same selected output. These are server/CLI observations, not test assertions.

Observed base: all three sources started 2026.9.3 and registered a tunnel. In the managed case, 2026.9.3 registered while 2026.10.4 was being installed, then was replaced.

Observed head: PATH was rejected with minimumVersion 2026.10.3 and managed 2026.10.4 started; explicit override was rejected and CLI status reported missing; old managed copy was skipped and managed 2026.10.4 installed before connector startup.
