handoff-to-devlisted

# Handoff to Development Specify intent, behavior, states, constraints, and verification so implementation requires no hidden product decisions or arbitrary pixel matching. ## 1. Confirm readiness Collect: `Approved flow and decisions | Platforms, browsers, devices, locales, inputs | Components, tokens, code, versions | Content, data, permissions, latency, APIs | Accessibility target and test environment | Analytics, release, flags, rollout | Open decisions and owners` Label unresolved product, data, security, privacy, or technical decisions. Do not disguise them as visual annotations. ## 2. Map the critical flow Write: `Entry -> Preconditions -> User action -> System response -> Branches -> Recovery -> Completion -> Return` Include deep link, refresh, back, cancel, interruption, duplicate submission, expired session, and partial completion where relevant. Define what state is retained. ## 3. Map design to system For every visible region identify: `Design object | Code component | Variant | Tokens | Content/data | Event | Owner | Gap` Synthetic example: `Address search | AddressAutocomplete | Default | semantic field tokens | Provider results | address_selected | Checkout | Timeout policy open` Use existing component and token names. Avoid raw pixel, color, and typography values when semantic tokens or layout constraints exist. Mark new components and variants explicitly; do not silently create one-off implementations. ## 4. Specify component behavior Read [re