PR #28508 live verification, Linux / Chrome / Codex gpt-6.1-sol BASELINE $ git rev-parse github/main 7195b699547b538e49f758e314dde5c8c5d907cf $ git worktree add ../main github/main $ cd ../main && vp i $ setsid nohup vp run dev > /tmp/main-dev.log 2>&1 & Captured process-group leader: 48969 [dev-runner] serverPort=16733 webPort=8693 baseDir=/home/user/main/.t3 Through the web UI: added a real local Git repository; chose Codex GPT-6.1-Sol, Low, Full access, New worktree; sent a read-only branch/status turn and then a second turn asking git branch -m verify/renamed. $ sqlite3 -readonly .t3/userdata/statev2.sqlite Check Current Git Branch|verify/renamed|/home/user/t3code/.t3/worktrees/branch-follow-verification/t3-41e7ce76 $ git -C .t3/worktrees/branch-follow-verification/t3-41e7ce76 branch --show-current verify/renamed Sidebar row, hover card and Copy > Branch all showed/copied verify/renamed. Reloaded the web client: sidebar still showed verify/renamed. NEIGHBORING BEHAVIOR (real Codex turns in the same thread) 1. git switch -c verify/switched Provider completed. Sidebar and live Git panel followed verify/switched. 2. git switch --detach HEAD Provider completed. git status --short --branch returned ## HEAD (no branch). Read-only projection query still returned verify/switched, matching the sidebar. A detached checkout does not erase the recorded branch. 3. git switch verify/switched Provider completed and reported a clean working tree on verify/switched. Sidebar and live Git panel agreed again. CHECKS $ blacksmith-check run --id "timeout 480 vp test run apps/server/src/orchestration-v2/RunFinalizationService.test.ts apps/server/src/orchestration-v2/RunFinalizationQueue.test.ts" 2 test files passed; 11 tests passed. Worker stopped afterward. Existing CI at head 4099f5f3: 29 successful, 0 pending, 0 failing. No source edits, commits, or pushes made during verification. NOT VERIFIED Native Electron, iOS/Android, macOS/Windows, other providers, remote/relay connections, and live concurrent worktree reassignment or shared-worktree races. Temporary/shared/foreign-worktree guards have focused test coverage, but those guards were not driven through live user sessions here.