PR 32623 real environment verification, 2026-11-10 UTC

Baseline github/main: 6c9adfb2739205244b84e607736f6fd8b4611e69
Candidate: 40042be522787aea59c801b435b83bcf9e07a59e (unchanged)
Linux, Node v24.22.1, /usr/bin/google-chrome, repository Playwright.

Setup commands (sequential dev servers, isolated data):
  git worktree add ../main github/main
  cd ../main && vp i
  setsid nohup timeout 7000 vp run dev --no-seed > /tmp/main-dev.log 2>&1 &
  stop captured main process group before candidate starts
  git switch -c maria/takeover-pr-32623 40042be522787aea59c801b435b83bcf9e07a59e
  vp i
  setsid nohup timeout 7000 vp run dev --home-dir /home/user/t3code/.t3 --no-seed > /tmp/dev.log 2>&1 &

Real peer: separate source-main t3 serve, isolated /tmp/pr32623-source-peer, port 4101.
Fault injection: reverse proxy 4102 forwards to that real peer; 307 target 4103 also forwards to the real peer.
Only /mcp gets redirected. No mocked MCP responses, fixtures, demo data, or database writes.
Playwright clicks enabled Labs, paired/linked the real peer, added /home/user/main as a project, selected Codex GPT-6.1-Sol, and submitted real turns.

Baseline: normal remote and local t3_project_list succeeded. With tools/call redirected:
{"time":"2026-11-10T05:45:32.076Z","port":4102,"method":"POST","path":"/mcp","rpc":"tools/call","tool":"t3_project_list","authorization":true,"mode":"tools/call"}
{"time":"2026-11-10T05:45:32.079Z","port":4103,"method":"POST","path":"/mcp","rpc":"tools/call","tool":"t3_project_list","authorization":false,"mode":"tools/call"}
Observed client error: capability_denied, link no longer accepts this link.
The cross-origin redirected POST contained the tool call, though fetch stripped authorization.

Candidate initialization redirect:
{"time":"2026-11-10T05:49:19.579Z","port":4102,"method":"POST","path":"/mcp","rpc":"initialize","authorization":true,"mode":"all"}
Observed client error: The linked environment refused to start an MCP session (HTTP 307).
Candidate established-session redirect:
{"time":"2026-11-10T05:50:44.528Z","port":4102,"method":"POST","path":"/mcp","rpc":"tools/call","tool":"t3_project_list","authorization":true,"mode":"tools/call"}
Observed client error: The linked environment answered HTTP 307.
Redirect-target requests across all candidate cases: 0.

Neighbors: two normal remote calls reused one initialized MCP session; normal remote and local calls succeeded after removing the redirect.
Peer restart: first attempt encountered temporary instrumentation proxy downtime; after restarting the proxy, automatic session recovery succeeded:
tools/call: HTTP 404
initialize: HTTP 200
notifications/initialized: HTTP 202
tools/call: HTTP 200
No provider retry or relinking was required for the successful recovery call.

Checks through blacksmith-check:
  vp test run src/peer/PeerMcpClient.test.ts src/peer/PeerLinks.test.ts: 19 passed
  vp run check:changed 25bf84ab07f53f141c20239c63e383823a9d5ea0:
  format, lint, knip, GraphQL generation check, typecheck (3 packages), 21 tests passed.
  The remote shallow snapshot initially lacked the merge base; deepened the exact-head public fetch by one commit and reran successfully.

Not exercised: native desktop/Electron, iOS/Android, external-network peers, relay/tunnel/Tailscale, HTTPS downgrade, status codes other than 307, redirect on initialized notification.
No source changes or pushes.