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.

Before asking any real question, scan the repository to confirm current behavior, implementation shape, existing glossary terms, and relevant ADRs.

That scan should:

identify the files, modules, routes, components, schemas, tests, context docs, or ADRs most relevant to the topic
confirm what the system appears to do today rather than relying on assumptions
note gaps where behavior, terminology, or decision history is unclear

Do not start grilling from pure speculation if the repo can answer part of the question first.

grill-with-docs