Repository navigation
mnemo 5.26.0
Precision baseline + auto-scoped retrieval (workstream C, part 1).
"No tuning without a baseline" + the cross-project leak fix. Strict
isolation has existed since v1.2 -- the leak was that no production caller
passed an active project. Now every entry point auto-detects it.
mnemo eval+ the precision harness. A labelled 14-query SELF set
(real "where/how is X in mnemo" questions with known answering files), a
pure hit@k/MRR scorer, and a CLI report instrument. Official baseline on
the live 17,940-node corpus: hit@1=0.14, hit@5=0.21, MRR=0.16 -- the
numbers v5.27.0's exactness work (BM25/RRF/chunking) must beat.- Multi-key cwd auto-scoping.
retrieve.resolve_auto_scope(store, cwd)
derives the active project key SET from the caller's working directory:
the path-derived key plus every source-declared key rooted at/under/above
cwd, each applied only when it owns nodes. (Measure-first caught
single-key scoping BLINDING a repo to its own code -- mnemo's code is
keyedmnemo-daemonwhile its path derivesD--Repository-knowledge-base;
the union tripled hit@5 with zero ranking changes.)retrieve.query
gainsactive_projects; the UserPromptSubmit hook forwardscwdto
/v1/query(new optionalQueryIn.cwd); the server resolver slots the
request-level cwd between the explicit key and the daemon-global
workspace;mnemo queryauto-scopes by default (--no-auto-scope/
--projectto override); MCP queries auto-scope from the server process
cwd and everymnemo_queryresponse carries ascopefield
({project_keys, auto}). - "Not indexed -- want to index it?" (user spec). When the session
starts in a.gitdirectory whose project has zero indexed nodes, the
visible banner appends themnemo source add <cwd>offer and the model
context tells Claude it may offer the indexing commands -- asking first;
never auto-index. The first MCPmnemo_querynotice says the same.
No scoring-weight changes (that is v5.27.0, measured against this
baseline); deterministic retrieval for unscoped calls is byte-stable.