doobidoo/mcp-memory-service v10.49.1 on GitHub

What's Changed

[#842 / #843] memory_type ontology coercion was invisible to callers: When a user passed an unknown memory_type (e.g. "foo"), Memory.__post_init__ silently rewrote it to "observation" and only logged a warning. The MCP/HTTP store responses still reported success, so the caller had no way to detect the rewrite — subsequent memory_list queries filtered on the original type returned 0 results and looked like a broken filter (#842). Fix: both the MCP memory_store handler and the HTTP POST /memories endpoint now compare the requested vs. effective memory_type and append a visible warning to the response when they diverge, including a hint to register the type via MCP_CUSTOM_MEMORY_TYPES. The default "note" (applied when the caller omits type) does not trigger a warning. Tool description for memory_store updated to enumerate the built-in base types and link to the new ontology guide. Closes #843.
uvx CI flake fix: tests/web/test_middleware.py and siblings used importlib.reload(middleware) which poisoned FastAPI route deps for subsequent tests, causing test_harvest_requires_auth to fail intermittently in the Test uvx compatibility run. Removed dead reloads in test_analytics_graph.py + test_memories_api.py, added teardown reload in test_middleware.py, and hardened unauth_client in test_harvest_api.py via monkeypatch.setattr of middleware globals.

New: docs/memory-ontology.md: Documents the built-in memory-type taxonomy (12 base types, ~60 subtypes), the rationale for ontology validation, the coercion warning surfaced in store responses, and the JSON format for MCP_CUSTOM_MEMORY_TYPES. Linked from the README documentation index and from the memory_store MCP tool description. .env.example expanded with concrete examples for the env var. (Issue #843)

Full Changelog: https://github.com/doobidoo/mcp-memory-service/blob/main/CHANGELOG.md#10491---2026-05-05