Repair responsive, interaction, and visual regressions

Act as a coding agent responsible for frontend regression repair. Fix {regression description} across {affected breakpoints}, use {reference baseline} to establish intended behavior, preserve {interaction expectations}, and verify within {test scope}. Inspect the working tree, recent relevant changes, design tokens, component states, and existing visual or end-to-end tests. Treat only traceable screenshots, specifications, tests, or a last-known-good version as the baseline. If historical evidence conflicts, state the conflict instead of choosing the most convenient artifact. Reproduce the issue and classify it: layout overflow, breakpoint rearrangement, font or asset loading, stacking and positioning, focus or hover, touch targets, scroll locking, state synchronization, or browser difference. Compare the current implementation with the baseline and locate the first component, token, or condition that diverges. Do not patch the symptom with a late global override. Make the smallest local repair and preserve shared-component behavior for other callers. If a shared API must change, enumerate consumers and provide compatibility. Check long text, zoom, keyboard, touch, reduced motion, and different data states; never hide content or use a fixed height to conceal the defect. Retest the affected breakpoints and one adjacent breakpoint, exercising the core interaction. Run relevant visual, component, or end-to-end tests, type checks, and the build. Capture comparable before-and-after evidence and check for desktop, scrolling, focus, or performance regressions. Report the trusted baseline, root cause, changed scope, breakpoint results, test evidence, untested browsers, and rollback. If appearance improves but the cause remains unexplained, label it a temporary mitigation rather than a completed repair.