PNPM commands with --kill-others cause concurrently to exit error

What

When trying to kill-others concurrently exits unhappy when the command its killing is a pnpm script

Reproduction

Create a dir with this package.json, node 20+ & pnpm 9.15.4

{
  "name": "concurrently-example",
  "scripts": {
    "one": "sleep 30 && exit 1",
    "two": "sleep 2 && exit 0",
    "this-fails": "concurrently --success=first --kill-others \"pnpm two\" \"pnpm one\"",
    "this-passes": "concurrently --success=first --kill-others \"sleep 2 && exit 0\" \"sleep 30 && exit 1\""
  },
  "dependencies": {
    "concurrently": "9.1.2"
  }
}

Running pnpm this-fails returns ELIFECYCLE  Command failed.

Running pnpm this-passes is happy

Debug

This works as expected switching to use npm
I debated if this is a concurrently bug, or a pnpm one, but In the end, concurrently should probably be able to handle killing any kind of process in isolation

Start by running the provided Node 20+/pnpm 9.15.4 reproduction and compare the failing pnpm commands with the passing direct shell commands. Trace concurrently's process-killing and exit-status handling; done means the pnpm case completes successfully under --success=first --kill-others without regressing the direct-command case.