PR 30099 runtime verification, 2026-11-03, Linux x86_64
main: cefb544af3c98224874419198c0359b652ca3c94
PR:   0ff2a8002a0fe16d873a7e2c72335a8abf945817

Both launchers packaged from their exact source using:
node scripts/build-npm-launcher.ts --version 0.1.6 --output-dir <main-or-pr>
Both downloaded the official GitHub v0.1.6 linux-x64 archive with the launcher SHA256SUMS verification. No substituted executables or release fixtures.

MAIN: docker node:22-alpine, fresh isolated T3CODE_HOME
node main/t3/bin/t3.mjs --version
v22.23.4
3.24.3
t3: spawn /evidence/alpine-home/runtime/versions/0.1.6/t3 ENOENT
launcher_exit=1
/evidence/alpine-home/runtime/versions/0.1.6/.install-complete
0.1.6

PR: same container image and official release, fresh isolated T3CODE_HOME
node pr/t3/bin/t3.mjs --version
t3: could not run T3 Code 0.1.6 for linux-x64: spawnSync /evidence/pr-alpine-home/runtime/versions/0.1.6.staging-GhkBMO/t3 ENOENT
The Linux release requires glibc; musl-based systems such as Alpine are not supported. Use a glibc-based Linux environment.
launcher_exit=1
remaining_versions:
old_cache_attempt:
t3: could not run T3 Code 0.1.6 for linux-x64: spawn /evidence/alpine-home/runtime/versions/0.1.6/t3 ENOENT
The Linux release requires glibc; musl-based systems such as Alpine are not supported. Use a glibc-based Linux environment.
launcher_exit=1
0.1.6

PR: old main-created cache, docker --network none, two attempts
offline_old_cache_attempt=1
t3: could not run T3 Code 0.1.6 for linux-x64: spawn /evidence/alpine-home/runtime/versions/0.1.6/t3 ENOENT
The Linux release requires glibc; musl-based systems such as Alpine are not supported. Use a glibc-based Linux environment.
exit=1
offline_old_cache_attempt=2
t3: could not run T3 Code 0.1.6 for linux-x64: spawn /evidence/alpine-home/runtime/versions/0.1.6/t3 ENOENT
The Linux release requires glibc; musl-based systems such as Alpine are not supported. Use a glibc-based Linux environment.
exit=1
0.1.6

PR: glibc Linux, fresh download then cached reuse
t3 v0.1.6
first_exit=0
t3 v0.1.6
cached_exit=0
0.1.6

PR: glibc cached reuse with T3CODE_RELEASE_BASE_URL=http://127.0.0.1:1
t3 v0.1.6

CLIENT/PROVIDER:
Main dev: vp i; background vp run dev, ports 8693/16733, isolated /home/user/main/.t3.
PR dev: exact head above; vp i; background vp run dev, ports 5733/13773, explicit isolated /home/user/t3code/.t3.
Main stopped by captured process-group PID before PR dev started. PR dev stopped before launcher runtime started.
Created project /home/user/t3code and threads through actual web UI using repository Playwright and /usr/bin/google-chrome.
Real Codex gpt-6.1-sol turns read package.json and returned its package name plus LAUNCHER-VERIFY-30099 on both main and PR.
PR follow-up returned the package name plus FOLLOWUP-30099.

ACTUAL NPM LAUNCHER -> SERVER -> WEB CLIENT -> CODEX:
Fresh isolated T3CODE_HOME, changed PR launcher packaged for official v0.1.6:
node pr/t3/bin/t3.mjs serve --host 127.0.0.1 --port 17777 --no-browser
Completed onboarding, detected local Codex authentication, added real git repo through UI, selected gpt-6.1-sol.
Real first turn read package.json and returned its package name plus NPM-LAUNCHER-30099.
Reloaded client; a follow-up retained context and returned CACHE-FOLLOWUP-30099.

CHECKS:
Blacksmith focused launcher tests: 2 passed.
Blacksmith vp run check:changed cefb544af3c98224874419198c0359b652ca3c94: format, lint, both knip checks, scripts typecheck, and both launcher tests passed.
Explicit base used after fetching PR/main history because the task snapshot initially had no merge base.
GitCafe CI at verified head: 29 successful, 0 failing, 0 pending.

NOT EXERCISED:
Native desktop/mobile clients, macOS, Windows, Linux arm64, other providers, external remote/tunnel connection modes.
Real official binary did not hang; timeout/signal/nonzero validation branches covered only by existing focused subprocess tests on Blacksmith, not by modified real binaries.
No source changes needed.