fix(cli): resolve Windows Alchemy executable shims

[AmanVarshney01]

Problem

Composer only looked for node_modules/.bin/alchemy. Windows package managers can install alchemy.exe or alchemy.cmd without that extensionless file, so Composer incorrectly reports DEPLOY.ALCHEMY_BIN_MISSING before launching anything.

Fix

Resolve the nearest installed Windows executable in order: alchemy.exe, alchemy.cmd, then the extensionless shim. Continue searching ancestors for hoisted installations; POSIX behavior is unchanged. No PATH/global fallback, application workaround, or dependency change. Update the deployment guide and core-concepts skill with the resolution contract.

Verification

• Local CLI typecheck passed.
• Local resolver/runner tests: 12 passed; 2 Windows-only regressions skipped on macOS.
• Windows regressions cover cmd/exe-only installations and execution of a cmd shim with spaces and a literal ampersand in argv through the existing cross-spawn runner.
• The existing Windows CI matrix is running; native Windows verification is still pending. No new workflow.

Related owning-repo fix

prisma/prisma-cli#250 fixes the consolidated CLI adapter that launches the resolved command. Its native Windows regression reproduced spawn EINVAL on npm.cmd before the fix.

Limits

This does not claim all Windows assembly or deployment failures share this cause, or enable local Windows dev support. No production deployment was performed for this change.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@280

npm i https://pkg.pr.new/@prisma/composer-cli@280

npm i https://pkg.pr.new/@prisma/composer-prisma-cloud@280

commit: 9f85af1