PR #23763 live verification, Linux Boat VM, 2026-10-28 UTC
Head: 6e53cf3b7bfb9329f706ceaa4ff57ca723955a53
Baseline github/main: f17c9d202b
No source edits, commits, or pushes were needed.

Baseline setup:
git worktree add ../main github/main
cd ../main && timeout 600 vp i
setsid nohup timeout 7000 vp run dev --no-seed > /tmp/main-dev.log 2>&1 &
actual dev-runner ports: web 8693, server 16733
Using real Chrome and Playwright: Settings > Providers > Add provider > Codex
Configured Codex, Codex two, Codex three to use the installed npm Codex binary.
All three available at v0.164.0. Restarted main with these settings.

Observed real HTTP client spans in the running server trace:
GET https://registry.npmjs.org/%40openai%2Fcodex/latest
main startup, three calls (all HTTP 200):
2026-10-28T08:42:19.291Z
2026-10-28T08:42:19.326Z
2026-10-28T08:42:19.329Z
All overlap, reproducing the duplicate lookup bug.
Stopped main by its captured process group before running the PR.

PR setup:
git fetch github pull/23763/head
git switch --detach FETCH_HEAD
rev-parse HEAD: 6e53cf3b7bfb9329f706ceaa4ff57ca723955a53
timeout 600 vp i
Copied only the provider settings created through the app into isolated PR state.
setsid nohup timeout 6000 vp run dev --home-dir /home/user/t3code/.t3 --no-seed > /tmp/dev.log 2>&1 &
actual dev-runner ports: web 5733, server 13773

PR startup, one real HTTP 200 for the same three instances:
2026-10-28T08:44:32.981Z
All three available at v0.164.0 with update advisories.
Settings > Refresh provider status: one additional npm request, all three remain available.
Repeated manual refreshes during capture also each made one additional request.
Opened update advisory: correct npm command for @openai/codex, without installing an update.

Created project through Add project > Local folder > /home/user/t3code.
Selected GPT-6.1-Sol in the real web composer.
Submitted read-only request to run git rev-parse --short HEAD.
Real Codex app-server tool turn completed: 6e53cf3b7b provider-path-ok
Resumed that same thread on GPT-6.1-Sol: returned follow-up-ok.
No files changed. No mock, replay, fixture, or demo provider was used.

Existing tests, executed remotely through blacksmith-check:
vp test run packages/provider-core/src/server/ProviderLatestVersions.test.ts packages/provider-core/src/server/maintenanceResolver.test.ts
2 files, 57 tests passed (5 shared-lookup cases; 52 maintenance-resolver cases).
PR checks observed at head: 28 successful, 0 pending, 0 failed.

Not verified:
Native desktop, iOS/Android, macOS/Windows, remote/tunnel client modes,
actual Homebrew/pnpm installations, hourly TTL expiration, update installation,
and real provider turns on other adapters. Failure/interruption paths were
covered by existing focused tests, not injected into the live provider.
No startup latency or speedup claim.