Real-server watch proof driver

Use independent checkouts at base b23f1e8af9b13af2c4aa1ba8e0d6987550688645 and head c8c420b6da7037a67e0de58e9e6cdc06082ce7e1; vp i in each.
Set PROOF_DIR to a new scratch directory, BASE_CHECKOUT and HEAD_CHECKOUT to the two checkouts.
Enable providerInstances.opencode={driver:"opencode",enabled:true} in each fresh home's userdata/settings.json.
Start each checkout's real server with T3CODE_DEV_SEED=0 node apps/server/src/bin.ts serve --base-dir "$PROOF_DIR/base-home" --port 38555 (head-home,38556 on head).
Run python3 driver.py base and python3 driver.py head. It creates synthetic git projects, idle threads, and calls the real HTTP MCP watch tool against the live GitHub PR. token.mjs issues a scoped full-access MCP session using the same auth service as the CLI; no auth is mocked.
Record with headless-desktop bash capture.sh base (then head).
Also run each checkout's CLI: node apps/server/src/bin.ts thread start --base-dir <home> --provider opencode --model opencode/big-pickle --title 'Watch passing checks' --wait --json <project> '<prompt below>'.
Prompt: Call the T3 tool watch_pull_request with url https://github.com/pingdotgg/t3code/pull/40645. Report its exact JSON result. Follow its returned next instruction if present, otherwise end your turn to wait. Do not call any other tool.
After at least six minutes, use thread show --json and read only the corresponding isolated database's orchestration_events for thread.pull-request-synced and thread.pull-request-link-updated. Confirm the base baseline cleared, passed=true, wakes=0, runCount=1 and pending monitor.
Captures are actual GNOME Terminal output on a 1920x1080 virtual display; they are not web UI screenshots.
