PR 28487 real development environment verification
main: 5732bbee397f0a2b0e61d0c2e432f01dca6df3dc (github/main)
PR head: 823b64dca38f085932a792ea8dcf4731d33bc814

Setup: separate main worktree; vp i on both heads; one background dev server at a time.
Chrome: /usr/bin/google-chrome, Playwright 1.60.0 from repository dependencies.
Empty isolated state; project /home/user/t3code created via Add project > Local folder.
All conversations below were submitted through the web composer using Codex gpt-6.1-sol.
PR used a copy of the main dev state after stopping main; no fixtures or mocked providers.

Live WebSocket protocol, holding ACKs while a real composer/provider turn runs:
main shell: 1 chunks without ACK; 2 total after one ACK.
main thread: 1 chunks without ACK; 2 total after one ACK.
PR shell: 8 chunks without ACK; 9 total after one ACK.
PR thread: 8 chunks without ACK; 9 total after one ACK.
PR server-config: 8 settingsUpdated chunks without ACK; blocked until ACK, then remaining updates delivered. Timestamp format restored to locale.
PR byte bound: a 99,610-byte thread snapshot stopped at one chunk until ACK; the synchronized marker and turn events then arrived.

Established-session loss in the actual web client:
main: after drop, GET /api/orchestration/shell was requested again.
PR: after drop, no GET /api/orchestration/shell; subscribeShell carried its last afterSequence.

Cold/cached browser startup still fetched authoritative HTTP shell (observed).
Offline replay scenario: one browser client offline while another submitted a real Codex turn that ran timeout 10 sleep 3.
The offline client retained its previous conversation and then received the missed user message, tool work, and reply connectivity replay ok.
No shell HTTP request occurred on reconnect; subscription resumed afterSequence 181.

Nearby behavior:
- New-thread creation and real Codex turn completed.
- Settings update stream delivered real server updates; value restored.
- Settled thread moved to Settled, count 0 -> 1; Un-settle restored it, count 1 -> 0.
- Integrated terminal: typed printf command through Terminal input; saw terminal connectivity ok and the next prompt.

Remote focused checks through blacksmith-check:
vp test run apps/server/src/terminal/OutputProtocol.test.ts packages/client-runtime/src/connection/supervisor.test.ts packages/client-runtime/src/state/shell-sync.test.ts
3 files passed, 75 tests passed (14 + 52 + 9).
GitHub CI at the inspected head: all reported non-skipped checks passed.
No source changes, commits, or pushes required.

Unverified: native iOS/Android clients, Electron shell, real bad-Wi-Fi/tunnel/relay throughput, silent-socket/background recovery, server-upgrade omission changes and large-gap snapshot fallback in a real app (focused existing tests cover fallback cases).
No broad performance benchmark or mobile speedup claim.