# App-created T3 Connect link status proof

Built each commit with the test-stage relay and Clerk environment loaded. Used the Linux Electron desktop under headless-desktop, fresh server data directories, light theme, 1100 × 780 desktop windows. No production relay or copied database.

On each side:
1. Open Settings → Sharing & access; choose Sign in.
2. Sign into test account 1 using its email verification code.
3. Dismiss the initial setup using Not now, then Done.
4. Enable T3 Connect using its switch; accept Download and install for managed relay client 2026.10.4.
5. Wait for “This environment is available to your other devices through T3 Connect” and four QUIC connections.
6. Run the commit’s built server CLI: node apps/server/dist/bin.mjs connect status --base-dir <same isolated home>.
7. Confirm cloud-cli-desired-link.bin is absent in the isolated home’s userdata/secrets directory.

The terminal driver runs the real CLI and redacts only its local tool path. Recordings show that command against the still-running desktop host. Captures are cropped to the T3 Connect row and terminal to omit machine identifiers.

terminal-driver.py takes the desktop D-Bus launcher PID, side (base/head), and checkout directory. Set EVIDENCE_DIR and CONNECT_TEST_ENV. It opens xterm on that launcher's display, executes status, and retains the output. drive.mjs attaches to Electron's CDP endpoint (CDP_PORT), executes ACTION, then disconnects.

Cleanup: turn each app’s T3 Connect switch off, run connect logout for each isolated home, and stop the desktop sessions.