pr #24480 live verification
main: 32ecd71726fee16f335484c1f95cbce126d461f6 (github/main fetched 2026-10-30)
pr: d5039d89c0ba5a21acc34ab8c19bbe32eed6d213

commands: vp i; setsid nohup vp run dev (main); setsid nohup vp run dev --home-dir /home/user/t3code/.t3 (pr)
main was stopped before starting pr. both used isolated state.
client: repo Playwright 1.60.0, /usr/bin/google-chrome, actual web app + authenticated /ws RPC
provider: actual Codex 0.164.0, gpt-6.1-sol through local proxy
no mocks, replay provider, fixtures, code changes, or runtime monkeypatches

replacement race:
20 settings saves per revision, real Codex shadow-home creation from existing ~/.codex.
60 provider.auth.subscribe RPC requests per save.
read-only fs.watch records actual shadow-home symlink creation.
only requests sent AFTER first link and completed BEFORE final initial link (thread_history_1.sqlite-wal) count as inside construction.
registry code closes the old scope before creating the new home.

main: 13 bounded requests
{"This provider does not support sign-in in T3 Code.":13}
example: creation 2026-10-30T11:31:46.800Z .. 2026-10-30T11:31:46.831Z
request 2026-10-30T11:31:46.810Z .. 2026-10-30T11:31:46.818Z
This provider does not support sign-in in T3 Code.

pr: 15 bounded requests
{"This provider instance is no longer available.":15}
example: creation 2026-10-30T11:33:42.658Z .. 2026-10-30T11:33:42.668Z
request 2026-10-30T11:33:42.663Z .. 2026-10-30T11:33:42.666Z
This provider instance is no longer available.

main returned the old instance (unsupported auth), despite replacement construction being underway.
pr rejected the retired instance (no longer available).
normal direct Codex instances do not offer T3 sign-in; this error difference observes live registry lookup without modifying credentials.

real model turns:
main gpt-6.1-sol completed: sol baseline verified.
pr after 20 replacements completed: replacement recovery verified.
pr UI settings save completed at 2026-10-30T11:36:25.911Z.
unchanged sibling real sol run: requested 11:36:23.736Z, completed 11:36:56.340Z; status completed.
{"threadId":"mcp:dd61b25a-7b4f-44a9-be84-88f878cdefc9","runId":"run:thread:mcp%3Add61b25a-7b4f-44a9-be84-88f878cdefc9:ordinal:3","status":"completed","reply":"sibling continued across settings save.","error":null}

removal neighbor through server.updateSettings:
{
  "create": "Success",
  "before": {
    "_tag": "Failure",
    "cause": [
      {
        "_tag": "Fail",
        "error": {
          "_tag": "ProviderSetupError",
          "instanceId": "verifyRemoval",
          "operation": "subscribe",
          "detail": "This provider does not support sign-in in T3 Code."
        }
      }
    ]
  },
  "remove": "Success",
  "after": {
    "_tag": "Failure",
    "cause": [
      {
        "_tag": "Fail",
        "error": {
          "_tag": "ProviderSetupError",
          "instanceId": "verifyRemoval",
          "operation": "subscribe",
          "detail": "This provider instance is no longer available."
        }
      }
    ]
  },
  "sibling": {
    "_tag": "Failure",
    "cause": [
      {
        "_tag": "Fail",
        "error": {
          "_tag": "ProviderSetupError",
          "instanceId": "verifySibling",
          "operation": "subscribe",
          "detail": "This provider does not support sign-in in T3 Code."
        }
      }
    ]
  }
}

focused checks through blacksmith-check:
vp test run apps/server/src/provider/ProviderInstanceRegistry.test.ts apps/server/src/orchestration-v2/ProviderAdapterRegistry.test.ts apps/server/src/provider/ProviderRegistry.test.ts
3 files, 53 tests passed.

not verified: exact model-turn admission inside the millisecond replacement gap; native desktop/mobile, macos/windows, remote relay/tunnel, other providers.
the race itself was observed through authenticated provider RPC, and real Codex turns separately proved normal operation and recovery.