Don’t treat a user-scope jevmem plugin as dormant. I compared the v0.5.0 and v0.5.1 launchers; I did not run jevmem. Tagged v0.5.0 finds Node and execs dist/cli.js with no jevmem.config.json check. CHANGELOG 0.5.1 says that install ran in every project Claude Code opened and sent those prompts to TypeSafe.

v0.5.1 exits before it looks for Node unless the project has jevmem.config.json. npm never published 0.5.0 or 0.5.1; the first 0.5.x on the registry is 0.5.2, and current is 0.5.3. The 0.5.3 plugin launcher still gates on that file first.

If you installed from the v0.5.0 GitHub marketplace tag today, look for JEVMEM.md and .jevmem/ in repos you did not enable.