fix(plan): rewrite node_modules/.bin/*.cmd to powershell on Windows

[fengmk2]

Summary

Running a node_modules/.bin/*.cmd shim on Windows triggers cmd.exe's "Terminate batch job (Y/N)?" prompt on Ctrl+C, which corrupts the terminal. At plan time, when which() resolves such a shim inside the workspace and a sibling .ps1 exists, rewrite the invocation to run the .ps1 directly through PowerShell — the spawn layer stays untouched and Ctrl+C propagates cleanly.

Closes voidzero-dev/vite-plus#1176

What the rewrite does

program_path: <abs path to pwsh.exe or powershell.exe>
args:         [-NoProfile, -NoLogo, -ExecutionPolicy, Bypass, -File,
               <.ps1 path, relative to task cwd>, ...original_args]

The .ps1 path is stored relative to the task's cwd (with / separators), so SpawnFingerprint.args is portable across machines — no absolute paths leak into cache keys. PowerShell resolves -File <relative> against its own working directory (the task's cwd) and lands on the correct file.

When it fires

Only when all of the following hold:

1. Extension is .cmd (case-insensitive) — cmd-shim never emits .bat.
2. Path lives inside the workspace root — global shims like %AppData%\npm\node_modules\.bin\foo.cmd are left alone.
3. Path's last two components are .bin / node_modules (case-insensitive).
4. A sibling .ps1 exists.
5. pwsh.exe or powershell.exe is on PATH.

Any miss and the original .cmd is kept — behavior matches pre-PR.

Tests

• 6 cross-platform unit tests in vite_task_plan::ps1_shim::tests cover the pure rewrite logic: workspace root, hoisted monorepo subpackage (.. traversal), missing sibling, non-.cmd extensions, .cmd outside .bin, .cmd outside the workspace.
• Windows-only plan snapshot in plan_snapshots/fixtures/windows_cmd_shim_rewrite/ — a pnpm workspace with a sub-package. Two plan cases (dev_in_subpackage via cwd, dev_filter_from_root via --filter) produce byte-identical snapshots, proving the cache key doesn't depend on how the user navigates to the task. The harness gained a windows_only: bool flag on SnapshotsFile; redact_snapshot gained a pass that maps pwsh / powershell and their absolute host paths to <powershell> so the snapshot doesn't pin a specific runner image.

Test plan

• cargo clippy --workspace --all-targets + cargo test --workspace green on macOS
• Windows CI green
• Manual on Windows: https://github.com/Curtion/report-vite-plus-1, Ctrl+C during vp run dev leaves terminal clean
• Manual: confirm .cmd fallback on a Windows box with PATH stripped of PowerShell
• Manual: confirm a globally installed .cmd outside the workspace is not rewritten

---

Note

Medium Risk
Changes Windows command planning and spawn fingerprints by rewriting certain resolved executables and arguments, which could affect task execution and cache keys on that platform. Scope is constrained to .cmd shims under workspace node_modules/.bin with a .ps1 sibling and a detectable PowerShell host.

Overview
On Windows, planning now rewrites resolved node_modules/.bin/*.cmd shims inside the workspace to run the sibling .ps1 via pwsh.exe/powershell.exe (adding a fixed PowerShell arg prefix and recording the .ps1 path relative to the task cwd), so Ctrl+C no longer triggers cmd.exe's "Terminate batch job" prompt and cache fingerprints reflect the actual invocation.

This adds a dedicated ps1_shim module (using pathdiff) and applies it to both normal spawn commands and synthetic plan requests. Snapshot test infrastructure is updated with per-fixture platform filtering plus PowerShell path/name redaction, and a Windows-only plan snapshot fixture is added to validate stable, portable cache keys across invocation styles.

^{Reviewed by Cursor Bugbot for commit 09b4dc1. Configure here.}

[fengmk2]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 4f14ebe. Configure here.}

[fengmk2]

before

after

[fengmk2]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 3e1fc38. Configure here.}

[fengmk2]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 26021ca. Configure here.}

[fengmk2]

@cursor review

[fengmk2]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 24f2a8f. Configure here.}

[fengmk2]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 09b4dc1. Configure here.}