fix(tools): resolve PowerShell ENOENT by using full path on Windows

[octo-patch]

Fixes #12079

Problem

On Windows, the run_terminal_command tool fails with spawn powershell.exe ENOENT for all terminal commands (even simple ones like echo "test"). File creation/editing tools work fine, but nothing that uses the terminal works.

The root cause is that the VSCode extension host process may run with a minimal PATH that does not include %SystemRoot%\System32 (e.g. C:\Windows\System32), where powershell.exe lives. When child_process.spawn("powershell.exe", ...) is called without a full path, Node.js fails to locate the executable.

Solution

Replace the bare "powershell.exe" shell name with the full absolute path constructed from the SystemRoot environment variable, which is always present on Windows:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

SystemRoot is a guaranteed Windows environment variable that points to the Windows installation directory (typically C:\Windows). Using it avoids any dependency on the PATH being set correctly in the extension host.

Testing

• On non-Windows systems: no change in behavior (the else branch handles Unix/macOS).
• On Windows: powershell.exe is now resolved via the full path from SystemRoot, bypassing PATH lookup issues.
• Existing test suite covers the runTerminalCommandImpl function and should continue to pass.

---

Summary by cubic

Fixes Windows terminal commands failing with "spawn powershell.exe ENOENT" by invoking PowerShell via its absolute path built from the SystemRoot env var (fallback to C:\Windows) instead of relying on PATH. No behavior change on macOS/Linux.

^{Written for commit 8bdb84d. Summary will update on new commits.}

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

octo-patch seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[cubic-dev-ai]

No issues found across 1 file