grill-with-docslisted

<what-to-do> Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask the questions one at a time, waiting for feedback on each question before continuing. If a question can be answered by exploring the codebase, explore the codebase instead. </what-to-do> <supporting-info> ## Domain awareness During codebase exploration, also look for existing documentation: ### File structure Most repos have a single context: ``` / ├── PROJECT.md ├── CONTEXT.md ├── LANGUAGE.md ├── docs/ │ └── adr/ │ ├── current/ │ │ ├── 0001-2026-01-04-0900-event-sourced-orders.md │ │ └── 0002-2026-02-11-1030-postgres-for-write-model.md │ └── archived/ └── src/ ``` If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives: ``` / ├── PROJECT.md ├── CONTEXT-MAP.md ├── LANGUAGE.md ← one shared glossary (sections per context) ├── docs/ │ └── adr/current|archived/ ← system-wide decisions ├── src/ │ ├── ordering/ │ │ ├── CONTEXT.md │ │ └── docs/adr/current|archived/ ← context-specific decisions │ └── billing/ │ ├── CONTEXT.md │ └── docs/adr/current|archived/ ``` Create files lazily — only when you have something to write. If no `LANGUAGE.md` exists, create one when the fir