PR 30059 live verification, 2026-11-03, Linux Boat VM
main: cefb544af3; PR: aa9502d82055f3c3cff6187bed1c17756883a55d

Started one dev server at a time using setsid/nohup vp run dev.
main server/web: 16733/8693; PR server/web: 13773/5733.
Browser: repo Playwright with /usr/bin/google-chrome.
App-created project and threads; actual Codex gpt-6.1-sol provider turns created
the Git repositories, advanced the remote, and created a divergent branch.
No source changes, mock provider, fake Git command, or database fixtures.

Actual Git daemon served the bare remote over TCP. A transparent TCP forwarder
held four unrelated remote connections for 12 seconds to occupy all four status
fetch slots. This is controlled transport delay, not a typical-network benchmark.
The target remote remained responsive. Its checkout started one commit behind:
0709628bf296838d4cfa01c0cec2cd8746a776ef ->
1671bd595d8e6bfe088d68648b2b8e0d39b0df35.

Main UI: 11:56:10.618 Pull clicked; 11:56:22.472 Pulled visible (11,854 ms).
PR UI: 11:59:43.221 Pull clicked; 11:59:43.660 Pulled visible (440 ms).
Both reached the expected remote SHA. PR completed before blocker transports
were released. These are observed UI runs, not medians; the PR button became
available later in the queue window than main's button.

PR queued-success RPC, same live server/client protocol:
12:04:27.597 vcs.refreshStatus started for target, fetch queued behind blockers.
12:04:27.997 vcs.pull started.
12:04:28.252 vcs.pull succeeded: pulled (255 ms).
12:04:28.472 original status waiter succeeded: ahead=0, behind=0 (875 ms).
Git trace: zero standalone background fetches for the claimed target remote.

PR running-fetch neighbor:
12:00:58.685 target status-fetch transport connected, held for 12 seconds.
12:00:59.517 vcs.pull started.
12:01:10.686 existing fetch transport forwarded.
12:01:10.748 pull's transport connected, after the existing fetch.
12:01:10.851 vcs.pull succeeded: skipped_up_to_date (11,334 ms).

PR divergent-pull fallback:
12:03:08.672 target status request queued behind four running fetches.
12:03:09.071 vcs.pull started.
12:03:09.306 failed as expected: GitCommandError, exit 128 (234 ms).
HEAD stayed 8d0bb324f375716480329061f100097c04c141b8.
12:03:20.286 Git trace recorded exactly one fallback command:
git --git-dir /home/user/pull-verification/.git fetch --quiet --no-tags
  --no-auto-gc -- queued-failure
Fallback exited 0. Subsequent live status: ahead=1, behind=1, clean worktree.

Blacksmith checks:
vp test run apps/server/src/vcs/GitVcsDriverCore.test.ts -t pullCurrentBranch
16 passed.
vp run check:changed github/main
format, lint, both knip passes, server GraphQL, 3 package typechecks passed;
241 tests in 2 existing files passed.
The worker initially lacked a merge base; fetched and unshallowed actual PR/main
history, then reran successfully.

Not exercised: native desktop/mobile clients, macOS/Windows, remote/relay/tunnel,
external hosted remotes under organic network load, real pull interruption
or process-spawn failure. Existing focused tests cover the latter failure cases.