Deterministic structure (files + symbols) of an enrolled repo's current code. Use to ground claims about what functions/types/exports exist. Scope with paths globs and pick a detail level to keep responses small.

Structural drift for an enrolled repo: files and symbols added, removed, or whose body hash changed. With a+b (snapshot ids) diffs those snapshots; with since=label diffs that snapshot vs live code; default diffs the latest snapshot vs live code. Errors if the repo is not enrolled.

Deterministic root hash + file count of an enrolled repo's current code. Same code → identical hash across machines. Use to confirm two machines/checkouts hold identical code, or that code changed since a stored hash (compare with status's latest stored hash). Errors if the repo is not enrolled.

Per-repo index health: last indexed, staleness, parse errors, coverage %, snapshot count, latest stored hash, file cap. Use to judge the stored index that diff's default baseline and the guard read from (a stale index means a stale baseline), and to check coverage before trusting a structure/locate miss: those parse live code on every call, so staleness does not affect them, but the file cap does, and coverage below 100% means files they never see. For the store as a whole use health. Errors if the repo is not enrolled.

Store-wide health: schema version, integrity check, enrolled repo names and count, db path. Use once to check the store itself is sound (integrity, schema) or to list what is enrolled; for one repo's freshness use status. Takes no arguments.

Deterministically locate symbols in an enrolled repo: name → file:line (+ short body hash). Pass symbol to find a specific definition without grepping (a named lookup searches every kind); omit it to list all (capped, paginate with offset) — the unfiltered list defaults to functions+classes. Use this to verify a symbol exists before claiming it does: a zero-match result is definitive (parsed from the live AST), unlike grep, which can miss real symbols (formatting/whitespace variance, multi-line signatures) or hit false positives (comments, strings).