plan-interrogationlisted

# Plan Interrogation Interview relentlessly about every aspect of the plan until shared understanding is reached. Walk down each branch of the design tree, resolving dependencies one-by-one. Ask ONE question at a time, wait for feedback before continuing. Provide your own recommended answer with each question. If a question can be answered by exploring the codebase, explore instead of asking. --- ## Context discovery On invocation, discover project context in this priority order: 1. **Read `CLAUDE.md`, `AGENTS.md`, and `AGENT.md`** at the repo root if they exist — find pointers to other docs. 2. **Read `CONTEXT.md` or `CONTEXT-MAP.md`** at the repo root if they exist. 3. **If `CONTEXT-MAP.md` exists** — multi-context repo; read the map to find the relevant context for the current topic. 4. **Read existing ADRs** from `docs/adr/` if the directory exists. 5. **Any paths explicitly referenced** in CLAUDE.md/AGENTS.md/AGENT.md. --- ## Domain awareness — file structure Most repos have a single context: ``` / ├── CONTEXT.md ├── docs/ │ └── adr/ │ ├── 0001-event-sourced-orders.md │ └── 0002-postgres-for-write-model.md └── src/ ``` If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives: ``` / ├── CONTEXT-MAP.md ├── docs/ │ └── adr/ ← system-wide decisions ├── src/ │ ├── ordering/ │ │ ├── CONTEXT.md │ │ └── docs/adr/ ← context-specific decisions │ └