SSH failed-launch evidence driver (synthetic data only)

Prerequisites: build each checkout with vp i and vp run build:desktop; run its web dev server with T3CODE_DEV_SEED=0 vp run dev:web. Set up an SSH user t3repro on 127.0.0.1:22 with key authentication, a trusted local host key, and a supported Node runtime on its noninteractive PATH. The same absolute path to remote-server.cjs must be readable by that SSH user.

Run the included drive.cjs under headless-desktop with arguments:
  node drive.cjs CHECKOUT WEB_PORT SERVER_PORT base
  node drive.cjs CHECKOUT WEB_PORT SERVER_PORT head

The driver launches the checkout's real Electron bundle, real bundled backend and matching web renderer against isolated state. It opens Settings > Connections, enters SSH host 127.0.0.1, username t3repro, port 22, and clicks Add environment. The source-server fixture returns HTTP 503 for every route; after 60 seconds the actual remote launcher fails and tails its log. Tokens are synthetic strings, never usable credentials. No provider model is used.

For the long-output comparison, create an empty file named long-output beside remote-server.cjs and rerun both commands with RUN_LABEL=base-long or RUN_LABEL=head-long. It adds 60 lines before the pairing details and uses qr.txt, generated with the app's renderTerminalQrCode helper against the synthetic pairing URL, exercising the same real failed-launch path with more than 4000 stderr characters.

extract.cjs RUN_DIRECTORY CHECKOUT LABEL extracts only stdout/stderr from the actual warning, the stack-free cause from the persisted command span, and the dialog text. It omits local command paths and trace IDs from the public diagnostics.

Captures: Linux Electron, 1440x1000 viewport, light theme; fresh T3 homes, no imported project/thread history. Recordings begin only after the Add environment dialog opens. No application code is changed by the driver.
