episodic-memory MCP server fails to start/connect in Claude Code on Windows with nvm

Issue Description:
Environment:

OS: Windows
Claude Code version: [run claude --version to get this]
Node.js version: v24.11.1 (via nvm)
Plugin version: 1.0.15

Problem:
The episodic-memory MCP server fails to start with status "✘ failed" when running in Claude Code.
MCP Server Details (from /mcp command):

Status: ✘ failed
Command: node
Args: C:\Users\Godswill\.claude\plugins\cache\superpowers-marketplace\episodic-memory\1.0.15/cli/mcp-server-wrapper.js
Config location: Dynamically configured

Node.js Setup:
I have two Node.js installations:

1. nvm: C:\Users\Godswill.nvm\versions\node\v24.11.1\bin\node.exe (v24.11.1)
2. System: C:\Program Files\nodejs\node.exe

bash$ node --version
v24.11.1

$ where node
C:\Users\Godswill\.nvm\versions\node\v24.11.1\bin\node.exe
C:\Program Files\nodejs\node.exe

**Steps Taken:**
- Tried reconnecting multiple times via Claude Code UI
- Verified Node.js is accessible from command line
- Restarted Claude Code multiple times
- Added nvm path to System PATH

**Error Output:**
Failed to reconnect to plugin:episodic-memory:episodic-memory

Questions:
Are there any logs I can check to see the actual error?
Is there a known issue with nvm on Windows?
Can I manually run the MCP server to debug the issue?

Additional Context:
Other MCP servers (tailwindcss-mcp-server, context7, prisma-local) work fine with the same Node.js setup.

Start with cli/mcp-server-wrapper.js, using the Command and Args shown in the /mcp output to run the MCP server directly under the nvm and system Node installations. Check Claude Code's reported version and capture the actual startup error. Done means the server starts and connects in Claude Code on Windows, with a regression test or documented reproduction if the repository provides one.