/**
 * Native smooth scrolling silently breaks every GSAP pin on the site.
 *
 * Something in the bundled GSAP build writes `scroll-behavior: smooth` as an
 * inline style on <html> shortly after load (the served markup has no such
 * attribute, and no stylesheet rule sets it). ScrollTrigger.refresh() works by
 * jumping the scroller to 0, reverting the pins, measuring, then restoring the
 * position. With smooth behaviour the browser *animates* those jumps, so every
 * measurement is taken mid-animation and lands short by exactly the scroll
 * offset at the time of the refresh.
 *
 * Measured on the front page at 390px, refreshing at y=3107:
 *
 *     start 3607 -> 500        off by -3107, i.e. -scrollY
 *     start   500 -> -1093     and again on the next refresh
 *
 * The pinned Recent Works carousel then believes it begins three screens
 * higher than it does: it snaps to its final frame, and never recovers for the
 * rest of the visit. It only ever showed up on phones because that is where a
 * refresh at a non-zero scroll offset is guaranteed — collapsing the address
 * bar changes innerHeight, which fires resize, which refreshes every trigger,
 * on the visitor's very first swipe. At scroll 0 the error is zero, which is
 * why the page always looks correct on load and in any test that measures from
 * the top.
 *
 * A stylesheet !important beats the inline style regardless of when the inline
 * style is written, which is a promise no JS guard could make. Anchor links
 * lose their native easing; the theme already assumes that, since its own
 * Lenis layer forces the identical value in leksa/style.css.
 */
html {
	scroll-behavior: auto !important;
}
