Desktop preview resize reproduction driver

Run the real desktop dev app at each commit with T3CODE_DEV_SEED=0 and
T3CODE_DESKTOP_REMOTE_DEBUGGING_PORT set to a distinct local port.
Use a fresh T3 home for each side. Add a synthetic project, then create a
Replay (dev), Question thread and leave its question unanswered.

The driver uses that thread's actual MCP endpoint and credential. Save a private
JSON file containing {endpoint, authorization}, and a separate {threadId} JSON.
The credential can be captured in the Replay agent at session/new from the
T3_ACP_MCP_ENDPOINT and T3_ACP_MCP_AUTHORIZATION entries in mcpServers.
Do not publish that private file.

Copy driver.cjs and window.ps1 to one scratch directory. From each checkout run:
node <scratch>/driver.cjs <base|head> <CDP-port> <private-MCP-JSON> <thread-JSON> <new-output-folder>

The driver starts record.ps1 on the logged-in desktop. It captures the
1920x1080 desktop with a 500ms pause between screenshots, until a file named
stop exists in its output directory. Encode frames with their actual capture
timestamps to preserve elapsed time.

The same driver on both sides opens a local 200-row page, resizes 390x844,
scrolls 3000px, resizes 1440x900, minimizes Electron, performs twelve alternating
390x844/1440x900 resizes with scrolls, then checks status/snapshot and restores
Electron. Every resize is followed by a real preview_evaluate of the page's
innerWidth and innerHeight. No app resize, painting, or MCP response is mocked.

The driver opens the Browser right panel through its real DOM control because
the native webview intercepts the pointer hit target of the floating panel
button. Resizes, scrolls, page measurements and snapshot all use the real MCP
endpoint. The native helper enumerates the checkout's windows and verifies
IsIconic=true after minimizing. The driver explicitly targets the returned tab.
