/* ============================================================================
   option4-bundle.css -- combined stylesheet for option4 / stage-2 /
   option4-stage.

   These nine files used to load as nine separate <link> tags, each its own
   render-blocking round trip before first paint -- disproportionately
   costly on a throttled mobile connection. Concatenated here in the exact
   order they used to load in (source-order-dependent overrides between
   them, if any, are preserved), each section kept intact and separated by
   a banner naming its original file so this stays as easy to maintain as
   the split files were. The originals are left on disk untouched, so
   reverting this bundle is just pointing the <link> tags back at them.
   ========================================================================= */

/* ---------- gallery-owl.css --------------------------------------------- */
/* Owl Carousel support for the #gallery rebuild — loaded only by
   option4/index-test.html. Everything is scoped to #gallery-owl-grid so it can
   never touch the production galleries that share style.css. */

/* Reproduces the hand-rolled track's `margin: 0 auto`. Owl gives .owl-stage an
   inline pixel width, so auto margins centre it whenever it is narrower than
   the viewport — the Video tab on desktop, 2 items in 3 slots — and collapse
   to 0 once the stage is wider, which is every looping state. Same trick, same
   two outcomes, no JS branch. */
#gallery-owl-grid .owl-stage {
  margin-left: auto;
  margin-right: auto;
}

/* Owl's stock easing is the shorthand `transition: <speed>s`, whose default
   timing function already matches the original `transform 0.6s ease`. Pinning
   the property list keeps it off `height`/`opacity`, which Owl's own
   .owl-height rule animates separately. */
#gallery-owl-grid .owl-stage {
  /* !important is required, not stylistic: Owl writes an inline
     `transition: <speed>s` SHORTHAND on the stage, which resets
     transition-property to `all`, so a plain stylesheet rule loses to it and
     the stage ends up animating every property it is given — including the
     width Owl rewrites on refresh and resize. The original track declared
     `transform 0.6s ease` and animated transform only. */
  transition-property: transform !important;
}

/* .owl-item is float:left with a JS-set width; the aspect-ratio boxes inside
   need it to establish its own block context so a fractional pixel width
   doesn't collapse the row. */
#gallery-owl-grid .owl-item {
  box-sizing: border-box;
}

/* Owl's `.owl-carousel .owl-item img { width: 100% }` wins over the item's
   `h-full object-cover` on specificity for width only, but its display:block
   would drop the flex centring inside the video tab's play badge. Restrict it
   back to the slide image itself. */
#gallery-owl-grid .owl-item img {
  display: block;
  width: 100%;
  height: 100%;
}

/* ---------- Mobile: image names always visible, bottom-left ----------
   style.css gates the label on hover (.gallery-hover-name{opacity:0} +
   .group:hover{opacity:1}), which a touch screen never satisfies — so the
   names simply never appeared on phones. Below md the label becomes permanent
   and moves from centred to bottom-left.

   The wrapper carries Tailwind's `items-center justify-center px-6` and the
   h3 carries `text-center`; the #id in these selectors outranks all of them,
   so no !important is needed. padding-bottom clears the .artistic-disclaimer
   line that sits at bottom:6px inside the same card. */
@media (max-width: 767px) {
  #gallery-owl-grid .gallery-hover-name {
    opacity: 1;
    align-items: flex-end;
    justify-content: flex-start;
    padding: 0 14px 22px;
  }
  #gallery-owl-grid .gallery-hover-name h3 {
    text-align: left;
  }
}

/* ---------- clubhouse-owl.css ------------------------------------------- */
/* Owl Carousel support for the Clubhouse strip rebuild — loaded only by
   option4/index-test.html. Scoped to #clubhouse-owl throughout so it cannot
   reach the production strips that share style.css. */

/* The strip is a bottom-aligned mosaic: 240px tall cards alternating with
   157.5px short ones (.ch-card-short at md and up), which the original got
   from the flex track's `items-end`. Owl lays .owl-item out as floats, which
   top-aligns them and loses the stagger, so the stage becomes a flex row with
   the same end alignment. Owl still writes the stage width and each item's
   width inline, and both are honoured under flex — only the float is ignored.
   transition-property is pinned to transform so Owl's shorthand duration does
   not also animate the height changes at the md breakpoint. */

/* .ch-card-short was described in the comment above but never actually
   implemented -- this is the first real rule for it. Mobile is left with
   no explicit height (governed implicitly by the image's own aspect
   ratio, same as before); only md and up get a fixed short height. */
@media (min-width: 768px) {
  .ch-card-short {
    height: 190px;
  }
}

#clubhouse-owl .owl-stage {
  display: flex;
  align-items: flex-end;
  /* !important for the same reason as the gallery build: Owl's inline
     `transition: <speed>s` shorthand resets the property list to `all` and
     outranks a plain rule here, which would let the stage animate its own
     width on refresh/resize. */
  transition-property: transform !important;
}

/* Cards carry flex-shrink-0, but that sits on the card *inside* .owl-item, so
   the flex stage would still be free to compress the items themselves below
   the width Owl measured for them. */
#clubhouse-owl .owl-item {
  flex: 0 0 auto;
  box-sizing: border-box;
}

/* Was `#clubhouse-scroll .flex > div > div` in style.css: the hover-reveal
   layers (dark overlay, four corner blocks, centred title) need this
   transition or they snap. Owl inserts .owl-stage-outer > .owl-stage >
   .owl-item between the container and the card, so the original two-level
   descendant path no longer reaches them. */
#clubhouse-owl .owl-item > div > div {
  transition: opacity 0.35s ease, transform 0.4s ease;
}

/* ---------- Cards must not depend on .reveal inside a carousel ----------
   Each card carries Tailwind-side `reveal`, which style.css defines as
   opacity:0 + translateY(24px) until initReveal's IntersectionObserver adds
   .is-visible. Inside an Owl track that breaks in two ways:

     1. Owl builds its loop clones AFTER page load, so the observer — which
        only watches the elements that existed when it ran — never sees them.
        Measured live: all 24 clones sat at opacity:0, transform translateY(24px).
     2. A card clipped by the track's overflow never intersects the viewport
        either, so originals beyond the visible strip never get .is-visible.

   Both cases leave boxes that still occupy layout but paint nothing, which is
   what read as blank space at the end of the loop. Geometry-based checks miss
   it entirely because the boxes are exactly where they should be.

   Cards inside the track are therefore always painted. The section heading
   above keeps its own reveal animation. */
#clubhouse-owl .reveal {
  opacity: 1;
  transform: none;
}

/* ---------- Hover reveal (ported from JS's setHover in clubhouse-owl.js) ----------
   Positional (nth-child), not by class. Markup order per card is [img,
   overlay, cornerTL, cornerBR, cornerTR, cornerBL, titleWrap] — the
   .artistic-disclaimer div that used to sit at position 2 (which the
   original off-by-one indices below were written against) has since been
   removed project-wide, so every selector here shifted down by one to match:

     nth-child(2) overlay   <- 0 / 0.5, scale
     nth-child(3) cornerTL  <- 0 / 0.8, scale
     nth-child(4) cornerBR  <- 0 / 0.6, scale
     nth-child(5) cornerTR  <- 0 / 0.6, scale
     nth-child(6) cornerBL  <- 0 / 1, opacity only — no scale
     nth-child(7) titleWrap <- never targeted, stays at its authored
                               opacity:1 so the facility name is always
                               legible

   !important overrides each layer's own authored inline opacity/transform
   (a no-JS/no-CSS fallback paint, not part of the hover state itself).
   Unconditional -- the same collapsed-by-default/:hover-reveals rule set
   applies on every device now, no separate mobile branch. Touch devices
   simply have no :hover to trigger the reveal (a tap opens the popup
   directly per clubhouse-owl.js regardless). */
#clubhouse-owl .owl-item > div > :nth-child(2) { opacity: 0 !important; transform: scale(0) !important; }
#clubhouse-owl .owl-item > div > :nth-child(3) { opacity: 0 !important; transform: scale(0) !important; }
#clubhouse-owl .owl-item > div > :nth-child(4) { opacity: 0 !important; transform: scale(0) !important; }
#clubhouse-owl .owl-item > div > :nth-child(5) { opacity: 0 !important; transform: scale(0) !important; }
#clubhouse-owl .owl-item > div > :nth-child(6) { opacity: 0 !important; }

#clubhouse-owl .owl-item > div:hover > :nth-child(2) { opacity: 0.5 !important; transform: scale(1) !important; }
#clubhouse-owl .owl-item > div:hover > :nth-child(3) { opacity: 0.8 !important; transform: scale(1) !important; }
#clubhouse-owl .owl-item > div:hover > :nth-child(4) { opacity: 0.6 !important; transform: scale(1) !important; }
#clubhouse-owl .owl-item > div:hover > :nth-child(5) { opacity: 0.6 !important; transform: scale(1) !important; }
#clubhouse-owl .owl-item > div:hover > :nth-child(6) { opacity: 1 !important; }

/* Just the dark overlay layer (nth-child(2)), shown permanently on mobile
   so photos read legibly against the white page background; the corner
   accents and title stay hover-only (collapsed on touch, no separate
   mobile branch for those). */
@media (max-width: 767px) {
  #clubhouse-owl .owl-item > div > :nth-child(2) {
    opacity: 0.3 !important;
    transform: scale(1) !important;
  }
}

/* ---------- key-project-features.css ------------------------------------ */
/* ============================================================================
   Key Project Features — dedicated stylesheet, following this project's own
   convention (clubhouse-owl.css, gallery-owl.css, pricing-owl.css each ship
   their own CSS rather than leaning on the compiled tailwind.css).

   This is necessary, not just conventional: tailwind.css here is a
   build-time-scanned, page-specific compile (Tailwind v4) — it only contains
   the utility classes that were present in the source templates at build
   time. Arbitrary-value utilities introduced by editing the HTML afterwards
   (e.g. h-[430px], text-[126px], leading-[40.6px]) are simply absent from
   the compiled CSS and have no effect, which is why the section rendered
   uncropped/uncentered/without its numeral and divider. Plain, hand-written
   CSS scoped to this section's own classes sidesteps that entirely.

   Layout replicates maduram-altura's #amenities section (reference:
   http://localhost/maduram-altura/index.php), but fonts and colors use
   this page's own design system instead of that reference's — Newsreader
   for headings/numerals and Montserrat for body text, #1a1a1a for text and
   #1e4620/#E35336 for accents, matching the Amenities/About sections and
   the arrow hover state already used elsewhere on this page.

   Vertical (top/bottom) slideshow, hand-written in key-project-features.js
   — not Owl Carousel: Owl only animates translateX internally, it has no
   vertical mode, and faking one with a CSS rotation hack fights directly
   with per-slide autoHeight (rotating a block swaps its visual box but not
   its offsetWidth/offsetHeight, so the two can't be reconciled without
   falling back to a guessed fixed height — exactly the mobile-clipping bug
   this rebuild exists to remove). No position:absolute anywhere here either
   way: .amenity-slide sits in normal document flow inside .amenity-track,
   .amenity-stage clips it with overflow:hidden and a JS-measured height that
   transitions alongside the track's translateY, so every slide gets its own
   real height at every breakpoint instead of one guessed number.
   ========================================================================= */

#key-project-features .font-body {
  font-family: "Montserrat", sans-serif;
}
#key-project-features .font-caudex {
  font-family: "Newsreader", "Newsreader Fallback", serif;
}
#key-project-features .font-blacker {
  font-family: "Newsreader", "Newsreader Fallback", serif;
}
#key-project-features .number-gradient {
  background: linear-gradient(180deg, #1e4620 0%, #153417 50%, #102812 100%);
  -webkit-background-clip: text;
  -webkit-text-fill-color: transparent;
  background-clip: text;
  opacity: 0.6;
}

/* ---- Layout ---- */
#key-project-features {
  position: relative;
  width: 100%;
  padding: 40px 0 40px;
}
#key-project-features .kpf-container {
  max-width: 1280px;
  margin: 0 auto;
  position: relative;
  padding: 0 16px;
}
#key-project-features .amenity-stage {
  position: relative;
  overflow: hidden;
  margin: 0;
  transition: height 0.7s cubic-bezier(0.4, 0, 0.2, 1);
}
#key-project-features .amenity-track {
  position: relative;
  display: flex;
  /* Mobile: slides sit side by side and the track moves horizontally
     (translateX in key-project-features-copy.js). Desktop switches this to
     a vertical column below. */
  flex-direction: row;
  align-items: stretch;
  transition: transform 0.7s cubic-bezier(0.4, 0, 0.2, 1);
}
#key-project-features .amenity-slide {
  width: 100%;
  flex: 1 0 100%;
  display: flex;
  flex-direction: column-reverse;
  justify-content: space-between;
}

#key-project-features .kpf-image {
  width: 100%;
  height: 220px;
  flex-shrink: 0;
  overflow: hidden;
  position: relative;
  cursor: pointer;
}
#key-project-features .kpf-image img {
  width: 100%;
  height: 100%;
  object-fit: cover;
}

#key-project-features .kpf-divider {
  display: none;
}

#key-project-features .amenity-active-line {
  /* height and transform are both set in key-project-features-copy.js —
     the divider's real rendered height divided by the slide count, so the
     highlighted segment always lines up with the divider regardless of how
     tall the active slide's content makes it. */
  position: absolute;
  left: 0;
  width: 100%;
  background-color: #1e4620;
  transition: transform 0.5s ease-in-out, height 0.5s ease-in-out;
}

#key-project-features .kpf-content {
  position: relative;
  padding: 10px 10px 0;
}
#key-project-features .kpf-number-wrap {
  position: relative;
}
#key-project-features .kpf-number {
  font-size: 60px;
  line-height: 1;
}
#key-project-features .kpf-title-wrap {
  position: relative;
  margin-top: -6px;
}
#key-project-features .kpf-title {
  font-size: 20px;
  color: #1a1a1a;
  text-transform: capitalize;
  letter-spacing: 0.68px;
  line-height: 40.6px;
  margin: 0;
}
#key-project-features .kpf-desc {
  font-size: 16px;
  color: rgba(26, 26, 26, 0.8);
  line-height: 28px;
  margin: 10px 0 16px;
}
#key-project-features .kpf-desc p {
  margin: 0;
}

/* ---- Arrows ---- */
#key-project-features .kpf-arrows-desktop {
  display: none;
}
#key-project-features .kpf-arrows-mobile {
  display: flex;
  justify-content: center;
  gap: 20px;
  margin-top: 20px;
}
#key-project-features .amenity-prev,
#key-project-features .amenity-next {
  display: flex;
  align-items: center;
  justify-content: center;
  cursor: pointer;
  border: 1px solid rgba(26, 26, 26, 0.3);
  border-radius: 999px;
  background: none;
  transition: all 0.3s ease;
  width: 42px;
  height: 42px;
}
#key-project-features .amenity-prev:hover,
#key-project-features .amenity-next:hover {
  border-color: #e35336;
  background-color: #e35336;
}
#key-project-features .amenity-prev svg path,
#key-project-features .amenity-next svg path {
  stroke: #1a1a1a;
  transition: stroke 0.3s ease;
}
#key-project-features .amenity-prev:hover svg path,
#key-project-features .amenity-next:hover svg path {
  stroke: #fff;
}

/* ---- Responsive ---- */
@media (min-width: 768px) {
  #key-project-features {
    padding: 50px 0 60px;
  }
  #key-project-features .kpf-container {
    padding: 0 32px;
  }
  #key-project-features .amenity-stage {
    margin: 0 24px;
  }
  #key-project-features .amenity-track {
    flex-direction: column;
  }
  #key-project-features .amenity-slide {
    flex: 0 0 auto;
    flex-direction: row;
    justify-content: flex-start;
  }
  #key-project-features .kpf-image {
    width: 280px;
    height: 320px;
  }
  #key-project-features .kpf-divider {
    display: block;
    width: 2px;
    height: auto;
    margin: 0 16px;
    background-color: #d1d5db;
    position: relative;
    overflow: hidden;
    flex-shrink: 0;
  }
  #key-project-features .kpf-content {
    flex: 1;
    padding: 93px 20px 0;
  }
  #key-project-features .kpf-number-wrap {
    position: absolute;
    top: 0;
    left: 0;
  }
  #key-project-features .kpf-number {
    font-size: 100px;
  }
  #key-project-features .kpf-title-wrap {
    margin-top: -30px;
    margin-left: 95px;
  }
  #key-project-features .kpf-title {
    font-size: 23px;
  }
  #key-project-features .kpf-desc {
    font-size: 17px;
    line-height: 30.4px;
    width: 285px;
    margin: 46px 0 0 18px;
  }
}

@media (min-width: 1024px) {
  #key-project-features .kpf-arrows-desktop {
    display: flex;
    flex-direction: row;
    gap: 9px;
    position: absolute;
    right: 0;
    top: 108px;
    z-index: 10;
  }
  #key-project-features .kpf-arrows-mobile {
    display: none;
  }
  #key-project-features .amenity-prev,
  #key-project-features .amenity-next {
    width: 36px;
    height: 36px;
  }
  #key-project-features {
    padding: 40px 0 60px;
  }
  #key-project-features .kpf-container {
    padding: 0 0;
  }
  #key-project-features .amenity-stage {
    margin: 0 60px;
  }
  #key-project-features .kpf-image {
    width: 320px;
  }
  #key-project-features .kpf-divider {
    margin: 0 33px;
  }
  #key-project-features .kpf-content {
    padding-left: 42px;
  }
  #key-project-features .kpf-number {
    font-size: 126px;
  }
  #key-project-features .kpf-title-wrap {
    margin-top: -40px;
    margin-left: 110px;
  }
  #key-project-features .kpf-title {
    font-size: 25px;
  }
  #key-project-features .kpf-desc {
    font-size: 16px;
    line-height: 26px;
    width: 80%;
  }
}

@media (min-width: 1280px) {
  #key-project-features .amenity-stage {
    margin: 0 80px;
  }
}

/* ---------- location-highlights.css ------------------------------------- */
/* ============================================================================
   Location Highlights — minimal custom stylesheet. Almost everything now
   lives as Tailwind utility classes directly in the HTML/JS; what remains
   here is only what Tailwind genuinely cannot express on this page:

     - This page's tailwind.css is a build-time scan of the original
       templates (Tailwind v4) — it only contains utility classes that were
       already present somewhere on the page when it was compiled. A few
       values needed here (the 45%/55% grid split, the 340×150 thumbnail
       size, responsive map-height overrides, the list's min-height) were
       never used elsewhere on this page, so no CSS exists for them no
       matter how the class is spelled — hence the small set of rules below.
     - Leaflet renders its own marker HTML at runtime from a plain string
       (see location-highlights.js), which Tailwind's build-time scanner
       cannot see either way, so those pin shapes need real CSS regardless
       of this page's Tailwind setup.
   ========================================================================= */

#location-highlights .lh-grid {
  grid-template-columns: 1fr;
  padding-left: 10px;
  padding-right: 10px;
  position: relative;
}
@media (min-width: 1024px) {
  #location-highlights .lh-grid {
    grid-template-columns: 45% 55%;
    padding-left: 40px;
    padding-right: 40px;
  }
}

#location-highlights .lh-image-wrap {
  width: 340px;
  height: 110px;
}

#location-highlights .lh-list {
  padding-left: 10px;
  padding-right: 10px;
}
@media (min-width: 1024px) {
  #location-highlights .lh-list {
    padding-left: 40px;
    padding-right: 40px;
  }
}

#location-highlights .lh-map-wrap {
  height: 300px;
  z-index: 1;
}

/* Tabs bar replacing the reference's prev/next arrows — sits full-width
   above both grid columns. grid-column here (rather than a Tailwind
   col-span-* class) for the same reason as the .lh-grid split above: this
   page's build-time tailwind.css only has classes already in use elsewhere,
   and col-span-2 isn't one of them. */
#location-highlights .lh-tabs {
  grid-column: 1 / -1;
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 10px;
  margin-bottom: 0px;
}
@media (min-width: 1024px) {
  #location-highlights .lh-tabs {
    gap: 14px;
    margin-bottom: 0px;
  }
}

/* Under 900px there isn't room to wrap the tabs onto extra lines without
   pushing the map down awkwardly — scroll them horizontally in one row
   instead, same pattern as the other carousels on this page. */
@media (max-width: 900px) {
  #location-highlights .lh-tabs {
    display: flex;
    flex-wrap: nowrap;
    justify-content: flex-start;
    overflow-x: auto;
    overflow-y: hidden;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
    -ms-overflow-style: none;
    padding-bottom: 10px;
  }

  /* Hide browser's native scrollbar -- iOS Safari ignores this pseudo-
     element entirely (and any other webkit-scrollbar styling), which is
     why the custom track/thumb below exists instead of relying on it. */
  #location-highlights .lh-tabs::-webkit-scrollbar {
    display: none;
  }

  #location-highlights .lh-tab {
    flex-shrink: 0;
  }

  /* Custom scrollbar track -- built and driven by
     location-highlights-scrollbar.js since no real scrollbar reaches iOS.
     Absolutely positioned against .lh-grid (position: relative) rather
     than flowing below .lh-tabs. */
  #location-highlights .lh-custom-scrollbar {
    width: 100%;
    height: 3px;
    background: transparent;
    border-radius: 10px;
    margin-top: 2px;
    overflow: hidden;
    position: absolute;
    top: 50px;
    left: 10px;
  }

  /* Custom scrollbar thumb */
  #location-highlights .lh-custom-scrollbar-thumb {
    height: 3px;
    background: #1e4620;
    border-radius: 10px;
    width: 30%;
    transform: translateX(0);
  }
}

@media (min-width: 901px) {
  #location-highlights .lh-custom-scrollbar {
    display: none;
  }
}

#location-highlights .lh-tab {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  padding: 7px 14px;
  border-radius: 999px;
  border: 1.5px solid rgba(26, 26, 26, 0.15);
  background: #fff;
  font-family: "Montserrat", sans-serif;
  font-size: 13px;
  font-weight: 600;
  color: rgba(26, 26, 26, 0.55);
  cursor: pointer;
  white-space: nowrap;
  transition: border-color 0.25s ease, color 0.25s ease, background-color 0.25s ease;
}
#location-highlights .lh-tab:hover {
  border-color: rgba(26, 26, 26, 0.35);
}
#location-highlights .lh-tab.is-active {
  border-color: #1e4620;
  color: #1a1a1a;
  background: rgba(193, 122, 74, 0.08);
}

#location-highlights .lh-tab-dot {
  width: 8px;
  height: 8px;
  border-radius: 50%;
  flex-shrink: 0;
}

#location-highlights .lh-tab-count {
  font-weight: 700;
  color: #1e4620;
}

/* Leaflet marker styling — generated at runtime, outside Tailwind's reach.
   The site marker itself now uses the stock leaflet-color-markers green PNG
   (L.icon in location-highlights.js) instead of a custom div-icon, so only
   the category (POI) pins need custom CSS here. */
.lh-poi-pin {
  width: 30px;
  height: 30px;
  border-radius: 50% 50% 50% 0;
  transform: rotate(-45deg);
  border: 2px solid #fff;
  display: flex;
  align-items: center;
  justify-content: center;
  box-shadow: 0 2px 6px rgba(0, 0, 0, 0.3);
}

.lh-poi-pin svg {
  transform: rotate(45deg);
}

/* ---------- scroll-down-btn.css ----------------------------------------- */
/* Scroll-down button — ported from maduram-altura (D:\xampp\htdocs\maduram-altura\index.php).
   Colors swapped for this site's own accent (#1e4620) in place of altura's
   #b1381f/#C9A84C. Loaded only on option4/option4-stage. */

/* Base layout, entirely in real CSS — the button markup carries no
   Tailwind layout classes at all now (checked against the compiled
   tailwind.css and confirmed missing: md:left-1/2, md:-translate-x-1/2,
   -mt-[7px] chevron overlap, border-none, z-[9980] — this page's Tailwind
   build only contains utility classes already used elsewhere, so these
   never compiled and the button rendered stuck at the far left with its
   two chevrons stacked apart instead of overlapping).

   Default state is position:absolute, not fixed: the button now lives
   inside #hero-banner-b (right after the #hero-form wrapper in the
   markup) and is centered the same way that lg-only form is
   (left:50%/-translate-x-1/2), rather than fixed to the viewport. A
   fixed-with-hardcoded-bottom button drifted out of place on resize,
   because #hero-banner-b's own height is itself responsive
   (h-[380px]/md:h-[520px]/lg:h-[calc(100vh-64px)] clamped between
   lg:min-h-[440px] and lg:max-h-[640px]) and doesn't track viewport height
   1:1 at every breakpoint — "120px from the viewport bottom" and "just
   above the hero form" were only the same point sometimes. Positioning
   absolute inside the same box the form uses ties it to that box's actual
   edge instead, at every size — matching the form's own technique exactly,
   per how it's built.

   scroll-down-btn.js switches this to position:fixed (with its own
   left/bottom) once the user scrolls past the hero — that scrolled-state
   behavior is unchanged from before. */
#scroll-down-btn {
  position: absolute;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 0;
  border: none;
  outline: none;
  cursor: pointer;
  left: 50%;
  transform: translateX(-50%);
  bottom: 16px;
  z-index: 99 !important;
}
@media (min-width: 1024px) {
  #scroll-down-btn {
    /* Clears #hero-form, which only renders at lg (hidden lg:block):
       its own bottom-5 (20px) plus its ~64px rendered height plus a
       visual gap. */
    bottom: 100px;
  }
}
#scroll-down-btn .scroll-chevron-2 {
  margin-top: -7px;
}

/* Hide while any Magnific Popup lightbox is open, same as the reference. */
body.mfp-zoom-out-cur #scroll-down-btn,
.mfp-wrap ~ #scroll-down-btn,
body:has(.mfp-wrap) #scroll-down-btn {
  display: none !important;
}

/* "Up" pill mode at the footer: a solid circular button instead of the bare
   bouncing chevrons. */
#scroll-down-btn.scroll-up-mode {
  background: #1e4620 !important;
  border-radius: 50% !important;
  width: 40px !important;
  height: 40px !important;
  padding: 10px !important;
  box-shadow: 0 4px 12px rgba(0, 0, 0, 0.25) !important;
  transition: transform 0.3s ease, background 0.3s ease, box-shadow 0.3s ease;
}

#scroll-down-btn.scroll-up-mode svg path {
  stroke: #ffffff !important;
}

/* Keep chevron bounce disabled while in up-mode for stability */
#scroll-down-btn.scroll-up-mode .scroll-chevron-1,
#scroll-down-btn.scroll-up-mode .scroll-chevron-2 {
  animation: none !important;
}

@keyframes scrollBtnChevronBounce {
  0%,
  100% {
    transform: translateY(0);
    opacity: 1;
  }
  50% {
    transform: translateY(7px);
    opacity: 0.6;
  }
}

#scroll-down-btn .scroll-chevron-1 {
  animation: scrollBtnChevronBounce 1.2s ease-in-out infinite;
}

#scroll-down-btn .scroll-chevron-2 {
  animation: scrollBtnChevronBounce 1.2s ease-in-out infinite 0.22s;
}

@media (width: 1366px) and (height: 551px) {
  #scroll-down-btn {
    bottom: 60px !important;
  }
}

/* ---------- mlp-zoom.css ------------------------------------------------ */
/* Zoom controls for the Master Plan popup — loaded only by
   option4/index-test.html. Everything is scoped under .mfp-mlp, the mainClass
   the master-plan popup is opened with, so no other lightbox on the page (the
   gallery, the clubhouse, amenities, unit plans) is affected. */

/* The scaled image is clipped to the box Magnific fitted it into, so zooming
   crops-and-pans inside a stable frame instead of spilling the plan across the
   whole viewport and over the close button. */
.mfp-mlp .mfp-figure {
  overflow: hidden;
}

/* Room for the control row underneath the plan.

   Magnific's resizeImage() writes `max-height: <viewport height>px` INLINE on
   the image, which would let the plan grow tall enough that anything below it
   falls off screen. Overriding that here (hence !important — it has to beat an
   inline style) shortens the image instead, and because .mfp-container centres
   its content vertically the reserved height splits above and below, leaving a
   clear band under the plan for the buttons.

   Reserving it this way rather than with padding on the image matters for
   zoom: padding would be inside the transformed box, so scaling would drift
   the picture upward by half the padding at every step. With the box holding
   the picture alone, scale stays centred on the plan. */
.mfp-mlp img.mfp-img {
    max-height: calc(100vh - 150px) !important;
    transform-origin: center center;
    transition: transform 0.25s ease;
    /* will-change: transform; */
}
.mfp-mlp img.mfp-img.is-panning {
  transition: none;
  cursor: grabbing;
}
.mfp-mlp img.mfp-img.is-zoomed {
  cursor: grab;
}

/* This popup has no title and no counter (single item, gallery disabled), so
   the gradient scrim style.css pins to the bottom of .mfp-content has nothing
   to sit behind — it would only darken the foot of the plan. */
.mfp-mlp .mfp-bottom-bar {
  display: none !important;
}

/* Centred below the image with a gap above, per the reference. top:100% is the
   bottom edge of .mfp-content, which hugs the image exactly, so the margin is
   a true gap between plan and buttons. Sits in .mfp-content rather than
   .mfp-figure so the figure's overflow:hidden cannot clip it. */
.mfp-mlp .mfp-zoom-controls {
  position: absolute;
  top: 100%;
  bottom: auto;
  left: 50%;
  right: auto;
  transform: translateX(-50%);
  margin-top: 18px;
  z-index: 1046;
  display: flex;
  align-items: center;
  gap: 8px;
}

.mfp-mlp .mfp-zoom-controls button {
  /* Same visual language as the close badge: brand fill, white glyph, fully
     round. The reset control is a pill rather than a circle because its label
     grows to "1.5x" / "2.5x". */
  height: 38px;
  min-width: 38px;
  padding: 0 10px;
  border: 0;
  border-radius: 9999px;
  background: #1e4620;
  color: #fff;
  font-family: 'Montserrat', sans-serif;
  font-size: 16px;
  line-height: 38px;
  text-align: center;
  cursor: pointer;
  opacity: 1;
  transition: background-color 0.2s ease, opacity 0.2s ease;
}

.mfp-mlp .mfp-zoom-controls button:hover,
.mfp-mlp .mfp-zoom-controls button:focus {
  background: #a9663a;
}

/* At a zoom limit the control stays in place but reads as unavailable, rather
   than disappearing and shifting the other two. */
.mfp-mlp .mfp-zoom-controls button[disabled] {
  opacity: 0.35;
  cursor: not-allowed;
  background: #1e4620;
}

.mfp-mlp .mfp-zoom-reset {
  font-size: 13px;
  letter-spacing: 0.3px;
}

@media (max-width: 767px) {
  /* Deeper reservation on phones: the close button is lifted to -50px above the
     frame there, so the popup needs clearance at both ends. */
  .mfp-mlp img.mfp-img {
    max-height: calc(100vh - 100px) !important;
  }
  .mfp-mlp .mfp-zoom-controls {
    margin-top: 14px;
    gap: 6px;
  }
  .mfp-mlp .mfp-zoom-controls button {
    height: 34px;
    min-width: 34px;
    line-height: 34px;
    font-size: 15px;
  }
}

/* ---------- pricing-owl.css --------------------------------------------- */
/* Owl support for the Pricing Table strip, scoped to #pricing-owl.
   Owl now runs at every breakpoint (2 items desktop, ~1.3 on mobile), so
   there is no separate grid layout to reconcile with any more. */

/* Owl's inline `transition: <speed>s` shorthand resets the property list to
   `all`, so without !important the stage would also animate the width Owl
   rewrites on refresh/resize. Same fix as the gallery and clubhouse builds. */
#pricing-owl .owl-stage {
  transition-property: transform !important;
}

/* The cards are min-w-[80%] flex children in the original; under Owl the
   .owl-item owns the width, and the card must fill it rather than keep a
   percentage of it. */
#pricing-owl .owl-item > div {
  width: 100%;
  min-width: 0;
  height: 100%;
}

/* The stage is a plain block under Owl, but the cards are `flex flex-col`
   boxes of unequal text length. The original strip let each card size itself
   and the grid stretched them; matching that means letting the items stretch
   to the tallest so the rounded panels line up. */
#pricing-owl .owl-stage {
  display: flex;
  align-items: stretch;
}
#pricing-owl .owl-item {
  flex: 0 0 auto;
  box-sizing: border-box;
  display: flex;
}

/* ---------- Cards must not depend on .reveal inside a carousel ----------
   Each card carries Tailwind-side `reveal`, which style.css defines as
   opacity:0 + translateY(24px) until initReveal's IntersectionObserver adds
   .is-visible. Inside an Owl track that breaks in two ways:

     1. Owl builds its loop clones AFTER page load, so the observer — which
        only watches the elements that existed when it ran — never sees them.
        Measured live: all 24 clones sat at opacity:0, transform translateY(24px).
     2. A card clipped by the track's overflow never intersects the viewport
        either, so originals beyond the visible strip never get .is-visible.

   Both cases leave boxes that still occupy layout but paint nothing, which is
   what read as blank space at the end of the loop. Geometry-based checks miss
   it entirely because the boxes are exactly where they should be.

   Cards inside the track are therefore always painted. The section heading
   above keeps its own reveal animation. */
#pricing-owl .reveal {
  opacity: 1;
  transform: none;
}

/* Gives the cards' 30px-blur box-shadow room to paint rather than being
   clipped by .owl-stage-outer's overflow:hidden, at every breakpoint now
   that Owl is never destroyed. */
#pricing-owl .owl-stage {
  padding-bottom: 37px;
}

/* ---------- cta-visibility.css ------------------------------------------ */
/* Gate for the two floating CTAs — the right-edge "Book a Site Visit" tab and
   the mobile Call Now / Download Brochure bar. Both stay hidden until the
   visitor scrolls past the mobile config/form block
   (<div class="lg:hidden w-full px-4 py-5">), and hide again on the way back up.

   Both are driven by TRANSFORM alone — no opacity, no visibility. Each slides
   off its own edge, which keeps the whole animation on the compositor
   (transform is the one property that never triggers layout or paint) and
   means neither element is ever an invisible-but-present hit target.

   This deliberately overrides script.js. initBookSiteVisitTab and
   initBottomCTA both show/hide the CTAs by whether a [data-lead-form] is on
   screen. Two reasons the gate has to win outright:

     - the trigger block CONTAINS #footer-form, so the form rule would suppress
       the CTAs at exactly the point they are meant to appear;
     - style.css drives the tab through opacity (`#book-site-visit-tab
       {opacity: 0}` + `.is-visible {opacity: 1}`), which would keep fading it
       independently of this gate.

   Hence !important throughout, including on the tab's opacity, which is pinned
   open so transform is the only thing deciding what you see. */

/* ---------- motion ----------
   style.css gave the tab opacity 0.5s and the bar transform 0.3s, so the two
   drifted apart when they moved together. One duration, one easing, one
   property. */
#book-site-visit-tab,
#bottom-cta {
  transition: transform 0.35s cubic-bezier(0.22, 1, 0.36, 1) !important;
  will-change: transform;
}

/* The hidden state IS the initial state, so animating the first paint would
   show both sliding away as the page opens. The JS adds this class as it loads
   and drops it two frames later (with a timer fallback, since rAF is paused
   in a backgrounded tab). */
html.cta-no-anim #book-site-visit-tab,
html.cta-no-anim #bottom-cta {
  transition: none !important;
}

/* Takes opacity out of the equation entirely: style.css sets it to 0 by
   default and script.js re-adds .is-visible on its own schedule. Pinned to 1
   so transform is the single source of truth. */
#book-site-visit-tab {
  opacity: 1 !important;
}

/* ---------- default: parked off its edge ----------
   The tab is `fixed right-0 top-1/2` with an INLINE transform: translateY(-50%)
   doing the vertical centring. Any transform here replaces that outright, so
   the -50% Y has to be carried in both states or the tab drops half its own
   height. !important is what lets a stylesheet beat that inline declaration. */
html:not(.cta-armed) #book-site-visit-tab {
  transform: translate(100%, -50%) !important;
}
html:not(.cta-armed) #bottom-cta {
  transform: translateY(100%) !important;
}

/* ---------- armed: slid into place ---------- */
html.cta-armed #book-site-visit-tab {
  transform: translate(0, -50%) !important;
}
html.cta-armed #bottom-cta {
  transform: translateY(0) !important;
}

/* ---------- schedule-visit override: wins even while "armed" ----------
   #schedule-visit's own form is watched by script.js's initBottomCTA /
   initBookSiteVisitTab (both explicitly include the whole #schedule-visit
   section, not just its form), which toggle #bottom-cta.bottom-cta-hidden
   and #book-site-visit-tab's .is-visible. Without this block,
   html.cta-armed #bottom-cta / #book-site-visit-tab above always win once
   armed (higher specificity via the extra html.cta-armed compound), so the
   two bars stayed stuck on screen over the schedule-visit form regardless
   of what script.js decided. Each rule below adds exactly one more class
   to the selector so it outranks the "armed" rule it's overriding. */
html.cta-armed #bottom-cta.bottom-cta-hidden {
  transform: translateY(100%) !important;
}
html.cta-armed #book-site-visit-tab:not(.is-visible) {
  transform: translate(100%, -50%) !important;
}

/* ---------- header-scroll.css ------------------------------------------- */
/* Eases the header's scroll inset (header-scroll.js toggles p-2 padding on
   the div wrapping the glass bar, which stays h-auto throughout). Tailwind's
   p-2 carries no transition of its own, so without this the bar would snap
   to its inset size the instant the page moves. Height is intentionally left
   untransitioned: the element's height is always the auto keyword, never an
   explicit value, and CSS cannot animate a property that never resolves to
   two concrete values either side of the change -- it just snaps, which is
   fine here since padding easing is what reads as smooth.

   Scoped through the fixed header wrapper so it cannot reach any other
   h-auto element. */
.fixed.top-0.left-0.right-0.z-50 > div {
  transition: padding 0.35s cubic-bezier(0.22, 1, 0.36, 1);
  /* Same curve and duration as the CTA gate, so everything on the page that
     moves on scroll moves alike. */
}

/* The glass bar must NOT transition its own width.

   It is size-full, so its width is already derived from the parent's animating
   padding — a width transition on top of that makes it chase a target that is
   itself still moving, adding a second 0.35s lag on every frame. That
   compounding is what read as sluggish rather than smooth. Measured before the
   fix: bar `transition: width, border-radius 0.3s` while the parent was
   animating padding-inline over the same window.

   Only border-radius is transitioned here, which is independent of layout and
   cheap. The bar's own re-blur (backdrop-filter) is the remaining per-frame
   cost and is inherent to insetting a blurred element. */
.fixed.top-0.left-0.right-0.z-50 > div > .backdrop-blur-md {
  transition: border-radius 0.35s cubic-bezier(0.22, 1, 0.36, 1);
  width: 100%;
}


/* Project Highlights desktop image panels (option4 markup only, .ph-panels):
   70% of the screen height (this page renders in quirks mode, so the %
   resolves against the viewport), but never so tall that the section stops
   fitting one screen -- keeps it a single stop for option4-section-scroll.js.
   304px = everything else on that screen: fixed header 77 + section padding
   40+40 + title block 95 + bottom button row 52. */
#project-highlights-section .ph-panels {
    /* height: min(70%, calc(100vh - 304px)); */
    height: 65%;
}

/* Short desktop screens (e.g. 1280x551): fit Project Highlights and
   Location in one scroll stop each. */
@media (min-width: 1025px) and (max-height: 600px) {
  /* Project Highlights */
  #project-highlights-section { padding-bottom: 20px; }
  #project-highlights-section > .pb-5 { padding-bottom: 8px; }
  #project-highlights-section > .py-4 { padding-top: 8px; padding-bottom: 8px; }
  #project-highlights-section .ph-panels { height: 56%; }

  /* Location Highlights */
  #location-highlights { padding-bottom: 20px; }
  #location-highlights .mb-8 { margin-bottom: 4px; }
  #location-highlights .lh-grid { row-gap: 16px; }
  #location-highlights .lh-image-wrap { height: 70px; }
  #location-highlights .lh-map-wrap { height: 290px; }
}
