v0.15.0

Added

• diversity on memory_read (0 to 1, default 0), passed to core's
  POST /memory/read (core#656, live since 2026-10-04). Above 0, a match that
  is a near-copy of one already picked gives its slot to the next distinct
  memory (maximal marginal relevance); it changes which memories come back, not
  their scores, and applies only when there are more matches than top_k and
  top_k is below 200. The bounds come from core's OpenAPI contract through
  src/limits.ts. At 0 the request body is byte-identical to before, so an
  older core sees no difference.

Documentation

• The README quick start ends with a standing instruction. A new step
  "4. Make it a habit" after "3. Try it" says the agent calls memory tools in
  normal work only when its instructions tell it to, and points to the
  setup_memory prompt and mnemoverse.com/docs/api/agent-memory.

• Windsurf is Devin Desktop: the install snippet names the Devin file.
  Windsurf was renamed Devin Desktop on 2026-06-02, and since version 3.9.19
  (2026-09-08) its only agent is Devin Local, which reads
  ~/.config/devin/mcp_config.json. The README block and
  docs/snippets/windsurf.md (mirrored into mnemoverse.com/docs) now say
  "Devin Desktop (formerly Windsurf)" and that path. The file names stay, so
  every include keeps working; an entry in the old Windsurf file still loads,
  because Devin imports it by default.

• The write tool's description names the gate for what it does. It said
  "an importance gate may filter low-value writes", the frame the docs
  dropped on 2026-10-02 (mnemoverse-docs#671): the gate scores novelty against
  the nearest memory in the same domain and refuses only a write the embedder
  cannot tell apart from one already stored; it judges neither importance nor
  truth, and it does not apply in shared rooms. The sentence now says so, in
  the words /api/getting-started uses. Description text only: nothing the
  tool accepts, does or returns changed.

• The comment on the memory://item/{memory_id} resource no longer says a
  Vault secret is safe to open. The engine's point read
  (GET /api/v1/memory/atoms/{atom_id}) now answers a Vault secret's id with
  404, exactly as it answers an id that names nothing, so the resource returns
  resource-not-found (-32002) for it, as for any missing memory. The comment in
  src/resources.ts now says that. Comments are not stripped from dist/, so
  the old sentence shipped in the package. Comment only: nothing the resource
  does, returns or advertises changed.

• npm: https://www.npmjs.com/package/@mnemoverse/mcp-memory-server

• MCP Registry: https://registry.modelcontextprotocol.io/v0.1/servers?search=mnemoverse

What's Changed

• docs(resources): a Vault secret's id answers resource-not-found, not the secret by @izgorodin in #201
• docs(tools): the write tool's description names the gate for what it does by @izgorodin in #202
• docs(snippets): Windsurf is Devin Desktop; the install block names the Devin file by @izgorodin in #203
• feat(read): diversity on memory_read by @izgorodin in #204
• release: 0.15.0 by @izgorodin in #205

Full Changelog: v0.14.2...v0.15.0