PR: https://git.cafe/pingdotgg/t3code/pulls/21771
GitHub: pingdotgg/t3code#21771
Head: 6a7743ef2ad7496d289eed6ac5aed72dd30a41cb
Main: f120c51134c6
Environment: Linux x64 Boat VM; real Electron desktop bootstrap fd3; dev web client driven by repository Playwright and /usr/bin/google-chrome; real Codex gpt-6.1-sol through configured local proxy.

Setup: real git repository /home/user/path-repair-verification, added through web client's Add project > Local folder. Login shell /bin/bash, inherited PATH=/usr/bin:/bin. A temporary bash login profile sleeps 8 seconds on the first interactive login only, then loads the existing real profile on subsequent probes. No provider mocks or executable stand-ins.

Main: desktop logged DesktopShellEnvironmentCommandTimeoutError (5000ms). Exactly one login shell: pid=110899, desktop parent=110853. Actual bundled server pid=110994 ran apps/server/dist/bin.mjs --bootstrap-fd 3. Web client displayed: "Could not start Codex CLI (`codex`). Check Settings → Providers → Codex → Binary path on the server."

PR: same desktop timeout. Two shells: pid=117350, desktop parent=117241; pid=117946, server parent=117930. Actual bundled server pid=117930 ran apps/server/dist/bin.mjs --bootstrap-fd 3. Web client discovered Codex. Real gpt-6.1-sol turn executed terminal commands and returned:
PATH_REPAIR_CODEX_OK
/home/user/.local/bin/codex
/home/user/path-repair-verification

Same-thread follow-up real gpt-6.1-sol turn executed terminal command and returned:
FOLLOWUP_CODEX_OK

Remote Blacksmith focused checks:
vp test run apps/desktop/src/shell/DesktopShellEnvironment.test.ts apps/desktop/src/backend/DesktopBackendConfiguration.test.ts apps/server/src/os-jank.test.ts
3 files passed; 36 tests passed.

Neighbor: successful first login-shell capture. Scenario pr-success had exactly one probe: shell pid=122257, desktop parent=122210. No shell timeout. Actual gpt-6.1-sol turn after desktop restart returned SUCCESSFUL_CAPTURE_CODEX_OK. Existing project/thread and earlier outputs survived restart.

Neighbor: first login shell exits 17. Desktop logged DesktopShellEnvironmentCommandError, exitCode=17. Clean retry scenario pr-retry-nonzero had two probes: shell pid=124934 with desktop parent=124842, then shell pid=124989 with bundled-server parent=124968. Server listened on 13773 and the real Codex turn returned NONZERO_RECOVERY_CODEX_OK after restart/resume.
One rapid restart attempt was discarded: the server ownership guard rejected startup while the prior server shut down. Retried after port release; no source change.

Evidence: main and PR screenshots were inspected full-size; uploaded images decoded at 945x889. Follow-up recording inspected as frames and played through from start to end in Chrome; playback and seeking also exercised in T3's background preview player.
Unverified: native macOS/Windows; macOS launchctl fallback; packaged Electron distribution; iOS/Android; other providers; persistent shell timeout where server retry also fails. Linux Electron dev bootstrap and its actual fd3/server/client/Codex path were exercised.