`, `

`, `
`, and `` elements. The evidence does not identify reusable component boundaries or interaction states. Treat loading, focus, hover, pressed, error, and disabled states as implementation work to validate rather than as captured facts. ## Responsive behavior The captured token set does not establish breakpoint values or mobile behavior. Validate stacking, navigation changes, image treatment, and type scaling against the representative captures before implementing a responsive adaptation. ## Practical implementation guidance - Preserve the light surface relationship and the measured type hierarchy before adding decorative treatment. - Start from the returned typography, spacing, color, and border values; name any new scale or semantic role as an adaptation rather than as a source fact. - Keep the captured font families separate from licensing decisions. - Use screenshots to validate component anatomy, responsive behavior, focus treatment, and motion before shipping. - Avoid introducing gradients or shadows beyond the captured treatment; none are established. ## Scope note The guide uses representative captured pages. The evidence supports the values and observations above; it does not establish component semantics, interaction states, motion timing, breakpoint rules, font licensing, or a complete source stylesheet.