codebase-snapshotlisted

# Codebase Snapshot ## Purpose Create or refresh `docs/SYSTEM_MAP.md` so future agents can understand the current codebase quickly without trusting stale memory. This skill is for agents, not end-user documentation. Prefer precise, verifiable facts over narrative explanations. Mark assumptions clearly. ## Division Of Labor With Graphify When `graphify-out/graph.json` exists (installed by `/ms.init` Step 2.9, kept current by post-commit hooks), the map and the graph split cleanly: - **Graph owns structure**: file inventories, symbol locations, call/import relationships, "what connects A to B". Answer these with `graphify query/path/explain` — never by writing them into SYSTEM_MAP.md, where they go stale by the next commit. - **Map owns curated prose**: system purpose, workflow semantics, invariants, risk areas, verification commands, runtime-path diagrams — knowledge a parser cannot extract. This content is deliberately slow-moving, which is what keeps the map trustworthy between refreshes. - Never paste Graphify output (GRAPH_REPORT.md, wiki, query results) into SYSTEM_MAP.md: `graphify-out/` is regenerated state; embedding it recreates the staleness problem the split exists to solve. Where no graph exists (e.g. a prose-heavy repo like the SPECTER template itself), structural questions fall back to `rg`/`find` at ask-time — still not to inventory sections in the map. ## When To Use - At the start of a non-trivial coding task. - When `docs/SYSTEM_MAP.m