PR 30838 real dev verification, 2026-11-04, Linux
main: 9e85538535c8553901351112ab02dd1dd62db5ee
PR: a95349e3d9437cd16e6d6146fa000bc5228c24e3
Git 2.43.0; Google Chrome 151; repo Playwright 1.60.0

Both checkouts: vp i, then background vp run dev. Only one dev server at a time.
Isolated .t3 homes; no copied database, mocks, fixtures, or Replay provider.
Project/repository/thread created through web UI. Real Codex gpt-6.1-sol turns
created and committed README.md, then verified the same commit on PR.

Main dev ports: server 16733, web 8693.
PR dev ports: server 13773, web 5733.

Playwright click: Version Control > Git action options.
Observed real client Request: vcs.refreshStatus, cwd = verification repository.
Observed real server Exit: Success; isRepo=true, refName=main, clean tree.
Git's GIT_TRACE2_EVENT recorded subprocess starts between click and RPC exit.
Three warm menu opens on the same clean repository:
                direct git config starts    direct git remote starts
main run 1                19                           8
main run 2                19                           8
main run 3                19                           8
PR run 1                   0                           2
PR run 2                   0                           2
PR run 3                   0                           2
These counts cover the menu-triggered refresh work, not a single driver call.
Other app paths still execute remote commands. No wall-clock speedup claim.

Real Codex turn created a local bare remote and an included remote config,
fetched locally and configured branch tracking. No external remote was pushed.
Relative include: correct values through safe command fallback.
Absolute include: warm refreshes returned correct values with 0 config starts.
After warming the cache, real Codex turns edited only the included file:
  branch.main.t3-merge-base-ref = refs/heads/verification-neighbor
  next observed vcs.refreshStatus: branchChanges.baseRef = same full ref
  branch.main.t3-merge-base-ref = refs/heads/main
  next observed vcs.refreshStatus: branchChanges.baseRef = refs/heads/main
.git/config's SHA-256 and complete stat were identical across these edits.

Neighboring behavior exercised in the running app:
- Actual branch picker: main -> verification-neighbor -> main.
- Provider appended two README lines; status reported dirty README.md, +2/-0.
- Changes opened the actual diff with the added text and selected base ref.
- Provider committed only README.md. Final RPC: clean tree, upstream present,
  aheadCount=1, behindCount=0, baseRef=refs/heads/main, zero diff totals.

Blacksmith focused checks:
vp test run apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/vcs/gitConfigSnapshot.test.ts
2 files passed, 274 tests passed, 1 skipped (case-insensitive filesystem case).

Blacksmith changed checks (after restoring shallow history):
vp run check:changed github/main
format, lint, knip (both), graphql, typecheck (3 packages): passed.
test (3 files): 276 passed, 1 skipped. Overall passed.
GitHub CI: all applicable checks passed at the unchanged head.

Not exercised: native desktop/mobile clients, Windows/macOS filesystem behavior,
Git older than 2.42 fallback in a live server, ACL-only changes, live ownership or
permission transitions, remote/relay/tunnel clients, and external forge APIs.
No PR source edits, commits, pushes, labels, merge, close, rebase or force push.