# ForgeFlow 0.3.1 release notes

## Windows environment-doctor hotfix

Version 0.3.1 fixes a Windows-only false negative in the environment doctor.
The setup script could invoke npm successfully, install all dependencies and then
report `spawn npm ENOENT` from Node.js. Windows exposes npm through a command
shim (`npm.cmd`), which cannot always be executed directly through
`child_process.execFile`.

The doctor now:

- uses `npm_execpath` through the active Node executable when launched by npm;
- falls back to `cmd.exe /c npm --version` on Windows;
- continues to invoke npm directly on Linux and macOS;
- reports which safe invocation path succeeded;
- reads its displayed application version from `package.json` instead of a
  duplicated hard-coded value.

Three regression tests cover npm-script execution, the Windows command-shim
fallback and the normal non-Windows path.

The npm deprecation messages printed during dependency installation are warnings
from transitive build-tool dependencies. They were not the cause of the setup
failure and do not prevent ForgeFlow from starting.