Codebase map

Ingest a .zip of your repo (or a single code/doc file) to build a lightweight map: file tree, ownership from CODEOWNERS, rationale facts from READMEs / ADRs / RFCs, and entity↔path links into your existing knowledge graph.

We don't embed code bodies — that's Cursor's job. We capture why the code is the way it is.