Problem
`cc-switch start claude` and `cc-switch start codex` currently only work on Unix-like systems. On Windows, the temporary launch path (`claude_temp_launch.rs` / `codex_temp_launch.rs`) lacks the necessary Windows-specific process spawning, shell shim handling, and cleanup logic required to correctly start, manage, and tear down child CLI processes.
Goal
Enable fully functional `cc-switch start claude/codex` on Windows, including:
- Correct spawning of `.cmd`/`.bat` npm shims via `cmd.exe /c`
- Job Object integration so child processes are killed when the parent exits
- Graceful fallback when the parent is already inside a nested Job Object
- Secure temporary file/directory creation with owner-only ACLs
- Orphan scan that accurately detects whether a child process is still alive
Problem
`cc-switch start claude` and `cc-switch start codex` currently only work on Unix-like systems. On Windows, the temporary launch path (`claude_temp_launch.rs` / `codex_temp_launch.rs`) lacks the necessary Windows-specific process spawning, shell shim handling, and cleanup logic required to correctly start, manage, and tear down child CLI processes.
Goal
Enable fully functional `cc-switch start claude/codex` on Windows, including: