v0.1.1

Changed

• The Release workflow now accepts only an existing annotated tag whose exact
  commit is on main; manual dispatch resolves the full refs/tags/... name
  so a same-named branch cannot shadow it. The workflow validates every public
  version surface, builds and checksums the explicit six-platform asset set
  from that commit, and renders release notes from this versioned section.
  Assets first upload to a draft; the workflow verifies the exact seven
  non-empty remote assets before the final step can publish the GitHub Release.

Fixed

• The npm installer now verifies the selected Release binary against the
  release's SHA-256 manifest before making it executable, rejects malformed or
  ambiguous manifest entries, verifies cached binaries, and removes partial or
  unverified files on failure.
• The npm wrapper no longer relies on a dependency postinstall script, which
  npm 12 blocks by default. The first explicit mem-mcp invocation performs the
  checksum-verified binary bootstrap, later invocations reverify and reuse a
  valid cache, all bootstrap diagnostics stay on stderr to preserve MCP stdout,
  and installer failures prevent the child process from starting. Runtime
  binaries now live in a user-writable, version-and-platform-scoped cache rather
  than the installed package; an atomic per-asset lock prevents concurrent
  installers from deleting each other's verified result, stale recovery cleans
  only its owner's artifacts, manifest failures remove any unverifiable service
  path, and wrapper shutdown forwards signals with bounded escalation so the
  native MCP child is not left orphaned.
• Release validation now verifies that every immutable GitHub Action pin used
  by the release workflow resolves in the action's official repository, runs
  on the macOS system Bash 3.2, and has a deterministic compatibility gate
  against Bash 4-only collection builtins.