repo-visualiser

Analyze the repository the user names — defaulting to the current one — at latest main, and render it as an **isometric** system map: every component is a **building** on a **grid**, every dependency is an edge carrying a **payload**, and everything drawn carries a **citation** to the code that proves it. The citations are the point. A building you inferred but never read is a fiction rendered in 3D. Draw only what you have read. ## 1. Pin the target at latest main Resolve the repo path, then pin the exact tree you will analyze: - **Has a remote:** `git fetch origin`, then read the tree at `origin/main` — or at the remote HEAD's default branch when it isn't called `main` (`git symbolic-ref refs/remotes/origin/HEAD`). Never analyze the working tree; it drifts from main, and the user asked for main. - **No remote:** use the local default branch and say so on the map. **Done when** the resolved branch and short sha are recorded, and they get stamped into the rendered output. ## 2. Survey the system Go codegraph-first, not grep-first, where those tools are present: `search_code` / `codegraph_context` for semantic candidates → `codegraph_callers` / `codegraph_callees` / `codegraph_impact` for structure → grep and read to confirm exactly. Where the codegraph tools are unavailable, fall back to semantic search plus grep and read, and say which you used in the final report. The citation requirement does not relax with the tooling. Every node you admit carries three things: |...