PR #33898 real dev verification Baseline: github/main 8df455c09b, /home/user/main; installed with vp i. Candidate: 7078ae28d248f6c7b7ec64cee152d3aef534ed1a, /home/user/t3code; installed with vp i. Linux x64, Node v24.22.1, /usr/bin/google-chrome, repo Playwright. One dev server at a time; baseline stopped by captured process group. Candidate uses explicit --home-dir /home/user/t3code/.t3, no seeded data. 1. Import boundary reproduction (runtime module-resolution trace, not a timing benchmark) Command: node --experimental-loader /tmp/import-boundary-loader.mjs /tmp/terminal-import.mjs file:////apps/server/src/terminal/Manager.ts Loader logs resolved modules; entry imports Manager.ts and lets loader messages flush. Main loaded: apps/server/src/provider/ProviderInstanceRegistryHydration.ts apps/server/src/provider/Drivers/ClaudeDriver.ts apps/server/src/provider/Drivers/CodexDriver.ts packages/provider-cursor/src/server/driver.ts packages/provider-fx/src/server/driver.ts packages/provider-grok/src/server/driver.ts packages/provider-opencode/src/server/driver.ts packages/provider-muse/src/server/driver.ts packages/provider-pi/src/server/driver.ts packages/provider-kiro/src/server/driver.ts Candidate loaded these same heavy paths: 0 Both imports completed. Lightweight home/environment helpers and an ACP registry import remain; no claim that every provider-related module disappears. 2. Running server protocol, actual PTYs Project and thread created in web UI, project rooted at /home/user/t3code, a real repository. The browser called server.updateSettings, terminal.open, terminal.write, terminal.attach and terminal.close over authenticated /ws, using the app's RPC protocol. Configured a Codex instance with real local config, changed its sensitive environment variable and homePath between terminal opens. Values below are task-created settings, not credentials. Baseline output: [ { "stage": "original", "secretRedacted": true }, { "stage": "original", "status": "running", "output": "BOUNDARY_RESULT secret=boundary-original override=provider terminal=terminal home=/home/user/.codex" }, { "stage": "refreshed", "secretRedacted": true }, { "stage": "refreshed", "status": "running", "output": "BOUNDARY_RESULT secret=boundary-refreshed override=provider terminal=terminal home=/home/user/boundary-codex-home" }, { "missingProvider": "TerminalProviderInstanceNotFoundError" } ] Candidate output: [ { "stage": "original", "secretRedacted": true }, { "stage": "original", "status": "running", "output": "BOUNDARY_RESULT secret=boundary-original override=provider terminal=terminal home=/home/user/.codex" }, { "stage": "refreshed", "secretRedacted": true }, { "stage": "refreshed", "status": "running", "output": "BOUNDARY_RESULT secret=boundary-refreshed override=provider terminal=terminal home=/home/user/boundary-codex-home" }, { "missingProvider": "TerminalProviderInstanceNotFoundError" } ] Disabled configured instances resolve for terminals as on main; missing IDs return TerminalProviderInstanceNotFoundError. 3. Real client/provider path On both versions: selected GPT-6.1-Sol in web composer and sent 'Reply with exactly: provider boundary verified. Do not edit files or run commands.' Both streamed and completed: provider boundary verified. On candidate: enabled Boundary Codex, selected its GPT-6.1-Sol entry, and completed a provider handoff and additional real turns through the local proxy. A real shell tool checked the configured home and environment without printing the sensitive value. Observed: provider_env home=/home/user/boundary-codex-home override=provider secret_refreshed=yes Ordinary web terminal: PR_PTY_OK cwd=/home/user/t3code 4. Focused checks through Blacksmith vp test run apps/server/src/terminal/Manager.test.ts apps/server/src/serverSettings.test.ts apps/server/src/provider/ProviderInstanceRegistryHydration.test.ts 3 files passed, 159 tests passed. vp test run apps/server/src/peer/RemoteDelegation.test.ts apps/server/src/peer/PeerForwarding.test.ts apps/server/src/mcp/toolkits/orchestrator/tools.test.ts 3 files passed, 36 tests passed. GitCafe status at head 7078ae2: 33 successful checks, 0 failing, 0 pending. No source edits, commits or pushes. Not verified: Windows/macOS, native desktop/mobile clients, other real providers, remote/relay/tunnel connections, packaged or large-data startup, end-to-end performance or memory improvements.