fix: route through cmd /c on Windows to fix ENOENT when spawning claude

[zerojarvis]

Problem

On Windows, child_process.spawn('claude', ...) fails with ENOENT because npm installs claude as a .cmd batch file that Node cannot execute directly without shell: true.

ClawdCommit shows this error in VS Code:

"claude" CLI not found. Install Claude Code and ensure it is in your PATH.

...even when claude is correctly installed and works in the terminal.

Root cause

npm on Windows creates three shims for any global package:

File	Type	spawn usable?
claude	Unix shebang script	No - Windows cannot exec shebang scripts
claude.cmd	CMD batch file	No - requires shell:true or cmd /c
claude.ps1	PowerShell script	No - .PS1 not in default PATHEXT

Node's spawn (without shell:true) finds the extensionless Unix script and fails with ENOENT.

Fix

On Windows, route through cmd /c claude instead of spawning claude directly. This lets cmd.exe resolve the .cmd shim natively. Arguments are still passed as a discrete array (not a concatenated shell string), which avoids the quoting and newline pitfalls of shell: true.

Tests

• Added routes through cmd /c on Windows test that stubs process.platform to win32
• Updated the platform-agnostic spawn-argument tests to use expect.any(String) for the command name so they pass on both Windows and non-Windows CI
• All 106 existing tests continue to pass

Verified on

Windows 11, Node v24.16.0, Claude Code CLI v2.1.177

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.