CLI proof driver for T3 Connect Cloudflare error 1016

Requirements: two checkouts at the base and head, dependencies installed with vp i, Node, Python 3, headless-desktop, GNOME Terminal, ImageMagick and ffmpeg. Supply the test-stage T3 Connect environment variables; never use production.

For each checkout, choose a fresh isolated home, then run:

```
node apps/server/src/bin.ts connect login --headless --base-dir <home>
node apps/server/src/bin.ts connect link --headless --base-dir <home>
T3CODE_DEV_SEED=0 headless-desktop python3 record-cli.py --checkout <checkout> --home <home> --output <new-output-directory> --port <unused-port>
```

Keep both Python files together. Run recordings sequentially. The driver starts the real server, waits for a reachable tunnel, calls the real relay's environment-link DELETE with this test home's credential, waits for the real 530/1016 response, prints the real CLI status, restarts once, and prints the resulting status. It permits either a reachable endpoint or 1016 after restart because CLI startup can reconcile the desired link. The comparison is the diagnostic after revocation, before any restart.

The wrapper records an Xvfb GNOME Terminal and takes two identical screenshots 500 ms apart before retaining each still. Paths and test-account identity are omitted from displayed output; diagnostic wording is unchanged. Recordings are real terminal captures, not recreated UI. Captures published for this proof were cropped equally to the terminal content. Private server logs are not published because startup prints pairing credentials.

After recording, remove this test environment and tunnel and sign out:

```
node apps/server/src/bin.ts connect logout --base-dir <home>
```

No application code or test doubles are used by this driver. No provider turn is needed for this server/CLI diagnostic.
