novahiz-clarifylisted

# novahiz-clarify: remove ambiguities **Step 2 of 6** in the pipeline. Questions come before anything gets locked. Previous: `novahiz-plan`. Next: `novahiz-task`. ## When you arrive The request is contradictory, loose, or broad enough that two readings lead to two different bodies of work. ## Part 1: sweep the ten families Run the request through these risk families and tag each one `clear`, `partial`, or `missing`: 1. Behavior and functional scope 2. Domain and data model 3. Flows and interactions 4. Non-functional qualities: performance, load, availability, security, accessibility, internationalization 5. External integrations and dependencies 6. Edge cases and failure handling 7. Constraints and tradeoffs 8. Terminology and consistency 9. Completion signals: what proves it is done 10. Fill zones and placeholder values A family still `missing` on scope, data, splitting, tests, UX, or operations becomes a question. Everything else waits. ## Part 2: frontier batches in the interface Picture the open decisions as a tree: each answer unlocks the choices that hang off it. The **frontier** holds the decisions whose inputs already exist, so you can ask them without guessing. One batch equals one call to the `question` tool, with one entry per frontier decision. ``` question({ questions: [ { header: "<short title, 30 chars max>", question: "<the decision, one sentence, with its stakes>", options: [ { label: "<recommended option> (Recommen