Pulse v0.3.1-beta

Hotfix over 0.3.0-beta.

Release-blocking fix

PulseMCP no longer requires a system Node.js installation.

0.3.0-beta shipped PulseMCP.cmd that resolved node from PATH. Clean machines failed immediately with “Node.js is required”. That violated the M7 productization requirement.

This release

• Ships PulseMCP.exe — thin launcher with job-object child lifetime
• Bundles a private Node.js 20.19.4 runtime under runtime\node.exe
• Keeps PulseMCP.cmd as a compatibility launcher (same private runtime)
• Installer / Uninstall cleanup prefer PulseMCP.exe
• Packaging verifies PulseMCP starts with PATH stripped of system Node
• PulseMCP product version 0.7.1

End users do not install Node.js.

Upgrade from 0.3.0-beta

1. Install Pulse-Setup-0.3.1-beta-windows-x64.exe
2. Open Settings → AI Integration
3. Unregister then Register Cursor (and Claude if used) so the launch command points at PulseMCP.exe
4. Enable Start Pulse MCP automatically with Pulse if desired
5. Restart Cursor

Artifacts

• Pulse-Setup-0.3.1-beta-windows-x64.exe
• Pulse-0.3.1-beta-windows-x64.zip
• SHA256SUMS-0.3.1-beta.txt

Everything else from v0.3.0-beta (MCP M2–M7 surface) remains.