PR 27413 real dev verification, Linux, 2026-11-01 UTC main: github/main 5732bbee39, /home/user/main PR: 2553b5ebb8212f54606ce4ab6ff76659acb0d628, /home/user/t3code Commands: git worktree add ../main github/main vp i (both checkouts) main: setsid nohup timeout 6500 vp run dev --no-seed PR: setsid nohup timeout 5700 vp run dev --home-dir /home/user/t3code/.t3 --no-seed Chrome: /usr/bin/google-chrome; Playwright 1.60.0 from repo dependencies main server stopped by captured process group before PR startup. One PR startup initially defaulted to ~/.t3; stopped before browser verification, then restarted with explicit isolated home. All reported PR scenarios use .t3. Data created through the real web UI separately on each version: Add project > Local folder > /home/user/snapshot-verification (real git repo) Select Codex GPT-6.1-Sol, submit: Read README.md using a shell command. Reply with its exact contents. Do not change any files. Provider executed cat README.md; both clients displayed: shell snapshot verification Chrome DevTools Protocol Network timestamps (seconds, browser monotonic clock): Main, browser reload: /ws handshake response, status 101: 944.286246 GET /api/orchestration/shell?omitIdleSubagents=1&omitOlderSettled=1 starts: 944.321310 HTTP response status 200: 944.356736 Shell request starts 35.064 ms AFTER socket opens. PR, browser reload: GET /api/orchestration/shell?omitIdleSubagents=1&omitOlderSettled=1 starts: 1111.411193 /ws handshake response, status 101: 1111.445360 HTTP response status 200: 1111.572880 Shell request starts 34.167 ms BEFORE socket opens. These prove request ordering through the real client/server path, not an end-to-end speedup claim. Neighbor: HTTP failure fallback Chrome Network.setBlockedURLs blocked */api/orchestration/shell* (no fabricated response). Browser reload requested shell HTTP; request failed with blockedReason=inspector. Actual outgoing websocket orchestration.subscribeShell payload: {"requestCompletionMarker":true,"omitIdleSubagents":true,"omitOlderSettled":true} No afterSequence: client requested the full socket snapshot. Existing project, conversation and provider output rendered successfully. Removed network block afterward. Neighbor: real server disconnect/reconnect Stopped PR dev process group using its captured PID. Restarted the same head, port and isolated home; existing browser recovered persisted thread. Submitted through composer: Read README.md again using a shell command. Reply exactly: reconnect verified: followed by the contents. Do not change files. Real Codex GPT-6.1-Sol ran cat and completed: reconnect verified: shell snapshot verification Shared clip shows the post-restart turn at 2x speed; server startup downtime removed. Focused checks, via task-owned Blacksmith worker: vp i && vp test run packages/client-runtime/src/state/shell-sync.test.ts PASS: 1 file, 11 tests, including superseded loads and live/cached config mismatch. Worker stopped after checks. GitCafe reports 30 successful checks, zero failing/pending, for the exact PR head. Not verified: Native Electron, iOS, Android; macOS/Windows; relay/tunnel; end-to-end reconnect latency savings. Superseded route attempts and live/cached capability mismatch covered by focused tests, not independently forced in the real client. No source edits, commits or pushes were needed.