PR #32639 real development verification, 2026-11-10 UTC
main: 6c9adfb2739205244b84e607736f6fd8b4611e69
PR: 34f1734b5347d288dfa039472ff3f00c588152e4
One background dev server at a time. Separate offline linking environment via the real t3 environment CLI. Fresh pairing codes minted by the running server. No mocks or demo data.

Commands (pairing codes and tokens omitted):
node apps/server/src/bin.ts environment link --base-dir <linker-home> <dev-origin> --pairing-code <fresh-code> --access read-only
(repeated once with a fresh code)
node apps/server/src/bin.ts auth session list --base-dir <peer-home> --json
POST /mcp initialize, notifications/initialized, tools/call t3_project_list

main after one relink: 2 MCP sessions
main replaced token: MCP initialize HTTP 200; t3_project_list HTTP 200
PR after one relink: 1 MCP session
PR replaced token: MCP initialize HTTP 401
PR current token: MCP initialize HTTP 200; t3_project_list HTTP 200, includes real peer-verification git repository
PR CLI environment list: 1 link, status reachable, read-only, no error

POST /oauth/mcp/revoke:
unknown token: HTTP 200, empty body
already-replaced token, twice: HTTP 200, empty bodies
non-MCP browser session cookie: HTTP 200; /api/auth/session remains authenticated

Real provider turns on main and PR:
node apps/server/src/bin.ts thread start --base-dir <peer-home> --provider codex --model gpt-6.1-sol --wait /home/user/peer-verification "Read README.md and reply with its contents. Do not modify files."
Both completed and returned the README contents: peer relink verification

Blacksmith remote checks:
vp test run apps/server/src/peer/PeerLinks.test.ts apps/server/src/auth/McpOAuth.test.ts
2 files, 24 tests passed.

Web follow-up: clicked Submit message in the actual client using Codex gpt-6.1-sol. The agent read README.md and returned: README checked: peer relink verification