Swap component variants

I need the button variant swapped across the checkout screens so the ‘primary/active’ style shows where the user can progress. Replace the rounded-blue variant with the filled-blue-primary variant on Checkout Step 1, Payment Review, and Order Confirmation, then check the interactions on desktop and mobile to ensure hover and pressed states still map to the correct variants. Complete by Thursday noon and flag any overrides you can’t reconcile.

Before I change variants across the file, make it obvious to reviewers which screens will change and why. Show the current component usage count, surface the visual difference between rounded-blue and filled-blue-primary at 1x and 2x, and list any instances with local overrides or detached instances that would break if I swap. Highlight anything that would affect the visual hierarchy on Payment Review.

I swapped the global button variant on the Payment Review frame and the CTA vanished in one breakpoint. The engineering handoff is Friday and I can’t tell if this is a missing instance, a renamed variant, or an override hiding the layer. Which is most likely, what should I check in the next five minutes, and what’s the safest immediate rollback so the handoff stays on schedule?

Every time I replace a component variant across the product, screens break because of overrides, naming drift, or detached instances. I lose time finding and fixing each case and stakeholders start to distrust mass updates. Where are we most likely failing on naming, library governance, or release steps, and what three habits should I adopt this quarter to reduce these firefights by 80%?