feature: unified-shell-resolution (4/4)

[myk1yt]

Stack Position

• Feature Branch: feature/unified-shell-resolution
• Stage: 4/4
• Depends on: feature: unified-shell-resolution (3/4) #37

Description

Full Feature Description

• Feature Branch: feature/unified-shell-resolution
• Feature Name: Unified Shell Resolution
• Purpose: Resolves the problem where shell selection, profile interpretation, argument assembly, and terminal reuse differ across command execution paths. Unifies the priority among user-configured shell, VS Code default profile, OS default, and safe fallback into a single typed resolution pipeline. This ensures that the same user settings produce a predictable execution environment across Windows Command Prompt, PowerShell, WSL, and macOS/Linux POSIX shells, reducing cases where the entire task fails in unclear ways due to misconfiguration.
• Full Change Description: B04 defines the shared shell settings types and the UI using local cached state before saving. B05 resolves settings and platform information into an executable, shell family, source, and argument array, preserving argument boundaries instead of string concatenation. B06 manages command queue, terminal lifecycle, registry, reuse, trace, cancellation, and disposal. B07 connects the resolver and lifecycle to the task, command tool, extension API, and webview message paths.
• Impact Scope: Affects the shared contracts terminal.ts, global-settings.ts, vscode-extension-host.ts, the settings UI TerminalSettings.tsx and SettingsView.tsx, the backend terminal layer src/integrations/terminal, and the task/tool/API wiring Task.ts, ExecuteCommandTool.ts, api.ts.
• Errors and Edge Cases: If an explicit user override is invalid, returns a typed rejectable error. If an automatic candidate is invalid, proceeds to the next candidate. Timeout, user cancellation, non-zero exit, and terminal disposal are kept as distinct outcomes. Shell path and command arguments are never combined into a single unescaped string. Inputs in SettingsView.tsx bind to cachedState, not live extension state.
• Testing Method: Run B04's contract and settings component tests, B05's Windows/POSIX/WSL resolution and invocation tests, B06's queue/reuse/cancellation/disposal tests, B07's task/tool/message tests and terminal-profile.test.ts. Manually run the same command in default, PowerShell, Command Prompt, and where available WSL/POSIX profiles, comparing the selected executable, output, exit code, cancellation, and cleanup.

Why Split Into 17 PRs

Instead of submitting this feature as a single unified PR, it was split into individual PRs because as code size grows, safely reviewing a PR becomes very difficult. The feature was broken into mutually exclusive individual PRs so that each can be reviewed independently.

What This PR Specifically Changes

Connects settings to command environment to lifecycle in Task.ts, ExecuteCommandTool.ts, ClineProvider.ts, and api.ts, and verifies E2E profile behavior. Does not add new primitives.

Included Files

• src/core/task/Task.ts
• src/core/webview/ClineProvider.ts
• src/core/tools/ExecuteCommandTool.ts
• src/extension/api.ts
• Direct tests for terminal message/fallback/execute-command
• apps/vscode-e2e/src/suite/tools/terminal-profile.test.ts

Exclusion Scope

• New resolver or lifecycle primitives
• Duplicate B04-B06 implementations
• Task/provider changes unrelated to shell integration
• All items in the common removal rules

[myk1yt]

Closing to recreate with main as target base branch. This PR had stale base branch references after fork sync.