PR #21337 real environment verification, 2026-10-27, Linux x64
baseline: github/main 4914cdd98f3d15ab2ddef34f0af70d3d68a2d8e5
candidate: a9a8940888f24fb82ace41abf76f1f07217be20e

Installed both checkouts with vp i. Started background dev servers.
main ports: server 16733, web 8693; isolated /home/user/main/.t3
PR ports: server 13773, web 5733; explicit isolated /home/user/t3code/.t3
Browser: repository Playwright 1.60.0 + /usr/bin/google-chrome.
Created project through Add project > Local folder, pointing to a real local clone.
Selected New worktree and Codex GPT-6.1-Sol; submitted actual provider turns.
Main: worktree created, provider returned MAIN_WORKTREE_OK, clean status +0/-0.
PR: worktree created, provider returned WORKTREE_OK, clean status +0/-0.
Both checked out identical committed tree 4914cdd98f3d15ab2ddef34f0af70d3d68a2d8e5.

GIT_TRACE excerpt from user-triggered create, after branch comparison config:
main:
20:19:00.755295 git config branch.t3/904c04d9.t3-merge-base-ref refs/remotes/origin/main
20:19:00.759136 git rev-parse --git-common-dir
20:19:00.764132 git rev-parse --show-toplevel
20:19:00.766170 git symbolic-ref --quiet --short HEAD
20:19:00.771287 git config --get branch.t3/904c04d9.t3-merge-base
PR:
20:28:33.942205 git config branch.t3/7d42f7a0.t3-merge-base-ref refs/remotes/origin/main
20:28:33.946466 git rev-parse --git-common-dir
20:28:33.950745 git config --get branch.t3/7d42f7a0.t3-merge-base

This observes removed root/branch discovery at creation finalization in the running
client/server path. Later metadata reads still perform ordinary discovery.
No percentage speedup claim: VM load and cache conditions were uncontrolled.

Blacksmith:
vp test run apps/server/src/vcs/GitVcsDriverCore.test.ts: 180 passed.
vp run check:changed 7d3208cbea86b91574366bb6e87d05f93c975127:
format, lint, knip 1/2, knip 2/2, graphql, affected typecheck, adjacent tests passed.
Initial runner sync disconnected; retry succeeded. History fetched for merge base.
GitCafe reports 31 successful checks, 0 failing, 0 pending on exact candidate SHA.

Neighboring client behavior: sent a second real Codex GPT-6.1-Sol message in the
new worktree. Provider returned FOLLOWUP_OK. Thread kept t3/worktree-ok and
client showed clean Changes +0/-0. The session survived browser re-pair/reload.
Manual refs-dropdown interaction was not completed; no claim of dropdown coverage.