/* Clone-specific overrides for website-5-c2d30d807b */

.website-5-c2d30d807b-hydrated-section a.button-citron,
.website-5-c2d30d807b-hydrated-section a.button-green,
.website-5-c2d30d807b-hydrated-section .button-citron,
.website-5-c2d30d807b-hydrated-section .button-green,
.website-5-c2d30d807b-hydrated-section a[class*="button"] {
  text-decoration: none !important;
}

/* THE ONLY CONSUMER of the transitions design token. tokens.ts has carried
   `transitions: { duration, timing }` since day one and token-resolver emits it as
   --transition-duration / --transition-timing, but NOTHING in the repo read those
   vars — grep returned zero `var(--transition-` hits — so the token was decorative
   and every clone rendered with instant, dead state changes no matter what its
   reference did. Reference JS is stripped from the clone, so CSS-only motion is the
   whole realistic target: interactive state changes are where it shows. Scoped to
   hydrated sections; the fallbacks keep this inert-but-valid if the token root is
   ever absent. Never transition transform/opacity FROM a hidden rest state here —
   the frozen bundle has no JS to reveal anything. */
.website-5-c2d30d807b-hydrated-section a,
.website-5-c2d30d807b-hydrated-section button,
.website-5-c2d30d807b-hydrated-section [class*="button"],
.website-5-c2d30d807b-hydrated-section [class*="btn"] {
  transition-property: color, background-color, border-color, box-shadow, opacity;
  transition-duration: var(--transition-duration, 200ms);
  transition-timing-function: var(--transition-timing, cubic-bezier(0.4, 0, 0.2, 1));
}