grok-repolisted

# grok-repo Read declared intent, structure, mechanics, then history for the *why*; judge taste only after evidence. Pick one mode by the question; every claim cites a file path or commit: - **Scoped question** ("how does X work?", "where does Y come from?") → a **dataflow trace**. - **Change question** ("why was X added?", "how did this feature evolve?") → **change archaeology**. - **Whole-repo question** ("explain this codebase", "give me a tour") → the **full briefing**. ## Dataflow trace (scoped mode) Follow one datum — request, message, config value, file — from entry to effect. The trace is the answer. - Lead with a hop chain, one line per hop, each cited: `POST /jobs (api/handler.go:41) → validate → Job{} (job.go:12) → enqueue (redis) → worker.Run (worker.go:88) → status written (store.go:130)` - At each hop name its holder (type/struct/schema), transformation, and every **shape change or rename** (JSON→struct, field rename, enum remap). - Mark seams crossed: serialization, queue, process/network boundary, goroutine/thread handoff. - Close with skipped side flows, error/edge paths worth a second trace, and surprises. - If the *why* of a hop is odd, spot-check history: `git log -S '<symbol>'` or blame the line. ## Change archaeology (history mode) Reconstruct one feature or decision, not the repository's entire chronology: 1. **Anchor the current concept** — find present symbols, paths, config names, tests, and user vocabulary. State what it does now befo