/* === PK_HERO_BREAKPOINT_SYNC_V1 (Phase 2M, 2026-09-14) ===
   Production hero breakpoint synchronisation.

   Slider Revolution selects its responsive level from documentElement.clientWidth,
   which EXCLUDES a vertical scrollbar, while a CSS media query and the vw unit resolve
   against the viewport width, which INCLUDES it. On any page long enough to scroll the
   two bases differ by the scrollbar width, so across viewport 1024-1038 the >=1024
   reservation in pk-site.css (CLS-HERO-1) was derived from a width larger than the one
   SR renders with. Because that rule set a definite aspect-ratio, the wrapper could not
   grow, and SR's taller LEV2 module overlapped the content beneath the hero.

   This file is additive: pk-site.css is NOT modified, so its long-lived cache entry
   stays valid and this rule is the only thing clients need to fetch. It is enqueued
   with an explicit dependency on 'pk-site' and at a later priority, so this rule is
   guaranteed to come after it and win the cascade at equal specificity.

   aspect-ratio:auto makes the wrapper content-driven, so it always grows to the real
   module height and can never overlap. min-height is a floor derived from the same
   clientWidth basis SR uses, which removes the residual over-reservation; it falls back
   to the old viewport-unit expression if the inline script never runs, in which case the
   hero is merely over-reserved exactly as before and still cannot overlap.

   No scrollbar width is assumed, hard-coded or subtracted: the basis is measured per
   client, so classic, overlay and absent scrollbars all resolve correctly. */
@media (min-width: 1024px) {
  .entry-content > .wp-block-themepunch-revslider:first-child {
    aspect-ratio: auto;
    min-height: var(--pk-hero-h, calc(100vw * 29 / 160));
  }
}
/* === /PK_HERO_BREAKPOINT_SYNC_V1 === */