interface-shiplisted

# Interface Ship ## Mission Decide whether the interface is ready to be trusted by real users. This is a gate, not a summary. ## Release philosophy A feature is not ready merely because it compiles, looks attractive, passes the happy path, or has been declared done. It is ready when remaining risk is understood and acceptable. ## Intent gate Verify intended task, requested outcome, common path, acceptance criteria, and scope. ## Architecture gate Verify hierarchy, navigation, surface selection, state ownership, responsive architecture, and progressive disclosure. ## Craft gate Verify typography, spacing, alignment, density, color, material, iconography, imagery, states, and consistency. ## Interaction gate Verify feedback, transitions, motion, interruption, cancellation, loading, errors, recovery, focus, and input modalities. ## Adaptation gate Verify meaningful combinations of space, input, content, text scaling, orientation, and reduced motion. ## State gate Verify reachable important states: empty, loading, success, error, disabled, partial, overflow, stale, interrupted, restored. ## Accessibility gate Verify native semantics, names, keyboard, focus, contrast, non-color cues, target behavior, reduced motion, and dynamic updates. ## Performance gate Use evidence for startup, interaction latency, rendering, memory, network, or storage where relevant. Never invent measurements. ## Regression gate Identify changed components, shared primitives, changed