handoff-to-devlisted

# Handoff to Development Handoff is a shared implementation contract, not a measurement dump. Specify intent, behavior, states, constraints, and verification so the team can build the experience without guessing or freezing the design into brittle pixels. ## 1. Confirm readiness Collect: - approved flow, screens, prototype, and decision history; - target platforms, browsers, devices, locales, and input modes; - design-system components, tokens, code links, and version; - content source, data shape, ranges, permissions, and latency; - API or service behavior known to the team; - accessibility target and test environment; - analytics plan, release scope, feature flags, and rollout constraints. 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` 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-o