During Rust-port acceptance testing (test/e2e-browser/specs/sidebar-click-resume.spec.ts on branch feat/rust-tauri-port, commit 8d60f7e, pinned there as test.fixme), clicking a seeded Codex session in the sidebar on the LEGACY server consistently settles the new pane into content.status === 'error' with no terminalId.
Ruled out as fixture problems: a real executable CODEX_CMD override was set, and codingCli.enabledProviders explicitly included codex. The rust server on the same flow creates a live terminal (via the FreshCodex JSON-RPC path).
Repro steps:
- Seed a codex session dir
- Boot the legacy dist server with CODEX_CMD pointing at any executable
- Open the SPA
- Click the codex session in the left panel
- Observe the pane error state (no terminalId assigned, content.status === 'error')
Context: Discovered by independent review (wave-2 review, 2026-07-19) which adjudicated it 'genuine legacy defect, not a fixture limitation'.
During Rust-port acceptance testing (test/e2e-browser/specs/sidebar-click-resume.spec.ts on branch feat/rust-tauri-port, commit 8d60f7e, pinned there as test.fixme), clicking a seeded Codex session in the sidebar on the LEGACY server consistently settles the new pane into content.status === 'error' with no terminalId.
Ruled out as fixture problems: a real executable CODEX_CMD override was set, and codingCli.enabledProviders explicitly included codex. The rust server on the same flow creates a live terminal (via the FreshCodex JSON-RPC path).
Repro steps:
Context: Discovered by independent review (wave-2 review, 2026-07-19) which adjudicated it 'genuine legacy defect, not a fixture limitation'.