lazycodex-ai doctor fails on Windows: spawn codex ENOENT (npm .cmd/.ps1 shims not resolvable without shell)

[innopoiesis]

Environment

• Windows 11 Pro (10.0.26200), Node v24.13.1, npm 11.12.1
• lazycodex-ai@4.19.0, Codex CLI 0.144.1 installed globally via npm (codex.ps1 / codex.cmd shims on PATH)

Symptom

> npx --yes lazycodex-ai@4.19.0 doctor
spawn codex ENOENT
(exit 1)

codex itself runs fine from PowerShell/cmd/Git Bash.

Root cause

On Windows, npm global installs expose codex only as codex.cmd / codex.ps1 shims. child_process.spawn("codex", ...) without shell: true (or without resolving the full shim path / using where codex) cannot execute .cmd/.ps1 files and fails with ENOENT. Doctor therefore cannot produce its health report on Windows even when Codex is correctly installed.

Suggested fix

Resolve the executable first (e.g. try codex.cmd on process.platform === "win32", or use a cross-platform launcher such as cross-spawn), or spawn with { shell: true } for the doctor probe.

[code-yeongyu]

Fixed on dev by code-yeongyu/oh-my-openagent#6280 (merge commit).

lazycodex-ai doctor now spawns codex through the package's existing Windows shim convention (codex added to WINDOWS_CMD_SHIM_COMMANDS), so on win32 it runs cmd.exe /d /s /c codex.cmd exec ... instead of a bare spawn("codex") that ENOENTs against the npm .cmd/.ps1 shim. Non-Windows behavior is unchanged and it is the only bare-codex spawn in the package. Locked with a given/when/then test over the platform seam. Thanks for the crisp root cause, @innopoiesis. Ships in the next stable lazycodex release; closing as fixed on dev.