v2.1.7
Three more gaps closed — this time verified against the real published package, not just local code
2.1.6's auto-heal looked right on paper but failed for the most common usage pattern. Found and fixed by testing against the actual npm registry end-to-end:
-
Auto-heal didn't work for
npx monomind@latest ...users — the session-start self-heal only searched local/globalnode_modulesfor a bundled reference copy.npxcaches each invocation under an unpredictable hashed directory that was never in the search list, so most users got silent no-ops. Rather than reimplement npx-cache scanning (found both a 2.1.6 and a stray 1.9.17 cache coexisting on one test machine — guessing wrong risks healing backward), added a background, non-blockingnpx monomind@latest doctor --fix --component helperscall (detached, unref'd, rate-limited to once per 6h, fails silently offline) that reuses the CLI's own already-correct resolution instead of duplicating it. -
doctor --fixwas a no-op for what it claims to fix —fixStaleHelpers()was actually gated behind--install, not--fix(confirmed by staling a file and watching--fixleave it untouched while--installhealed it).--installnow stays for the real Claude Code CLI install;--fixnow also applies the lightweight local file-copy fixes, matching what the flag name promises. -
Staleness detection only covered 4 hardcoded top-level files — everything under
handlers/andutils/(where essentially all the real hook-behavior fixes from the last two releases actually live) was invisible todoctor/doctor --fix. Now discovered dynamically from the bundled package so new handler files are covered automatically.
Verified live against the real registry, not just locally: installed monomind@2.1.7 via real npx, staled a handler file, fired the session-restore hook, and confirmed the background npx doctor --fix healed it within ~10 seconds — with zero local/global install present, the exact scenario that silently failed before this release.
Packages published: monomind@2.1.7, @monoes/monomindcli@2.1.7