pub fn brief<F: Fs>(db: &GraphDb<F>, opts: &BriefOptions) -> BriefReportExpand description
Summarise the store for the start of a session.
Deterministic for the same store state, with no now to pin: see the
module docs for why this one tool reads no clock at all.
§Two surfaces
A store ingest-git built carries the GitSync marker and is described
by the two rankings above. Any other store is a memory store, and the
same marker is what the MCP server’s tools/list splits on — so a store
whose session is offered explain_association and query is exactly the
store this describes with a SchemaBrief instead. Ranking a memory
store by IMPORTS and CALLS would rank nothing; naming its labels, its
edge types and one worked call per question kind is what spares the
session from probing for them.