interface-reviewlisted

# Interface Review ## Mission Review the interface as one system rather than producing disconnected specialist reports. The result should reveal what is strong, what is weak, what causes the weakness, what evidence supports it, and whether the work is ready to proceed. ## Modes ### Focused Inspect the primary task and highest-risk states. Report meaningful findings only. ### Full Inspect the complete requested scope across architecture, craft, interaction, adaptation, states, accessibility, and implementation evidence. If the requested scope is too large to inspect credibly, narrow it and state the boundary. ## Review order 1. Resolve scope and intent. 2. Inspect existing architecture and conventions. 3. Evaluate information and structure. 4. Evaluate visual craft. 5. Evaluate interaction behavior. 6. Evaluate adaptation. 7. Stress reachable states. 8. Inspect implementation evidence. 9. Consolidate systemic findings. 10. Verify. 11. Issue a verdict. ## Evidence rule A finding needs evidence appropriate to its claim. - Source claim: cite source location. - Visual claim: inspect rendered UI. - Interaction claim: exercise the interaction. - State claim: reach or deliberately reproduce the state. - Accessibility claim: perform the relevant check. - Performance claim: measure or label unverified. Never infer runtime behavior from source alone when runtime behavior determines the result. ## Consolidation One root cause is one finding. If one system decision creates