Ng command ran from angular/cli MCP server is failing on windows.

### Command

version

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

I am just reporting a bug I experienced on windows when trying the new experimental tools of the angular/cli mcp server.

On the latest angular/cli 21.1.2 when using the mcp server with experimental tools like modernize or build the mcp server fails to run the "ng" command on windows.
I don't experience any issues on linux systems.

The ng command is working fine in cmd or powershell with local or global angular/cli installation.

I asked my AI agent for feedback on the actual error and i got this :

```
{
"status": "failure",
"logs": [
"Process failed with error: spawn ng ENOENT"
]
}
```

It seems to be related to the spawn method not working properly on windows when shell option is set to false.

I hope it helps.

### Minimal Reproduction

Use experimental tools with the angular/cli mcp server that involves the ng command with spawn (like modernize or build) on windows.

### Exception or Error

```text
{
"status": "failure",
"logs": [
"Process failed with error: spawn ng ENOENT"
]
}
```

### Your Environment

```text
Angular CLI : 21.1.2
Node.js : 24.12.0
Package Manager : npm 11.6.2
Operating System : win32 x64
```

### Anything else relevant?

_No response_