/* ============================================================================
   Big Easy Paintings, shared page kit STYLESHEET.

   The companion to preview-page-kit.js. The markup for the header, the mobile
   panel, the inner-page banner, the brushwork, the estimate block, the reviews
   and the footer already lives once, in the JS kit. Until 2026-09-03 the CSS for
   all of it was copy-pasted into each preview's own <style> block, and the
   comment in preview-service-areas.html said so out loud: "Lives in both preview
   files because they carry their own style blocks."

   Two copies is a warning. The location page would have been a third, and it
   went wrong immediately: the mobile nav panel rendered 100px tall and OPEN over
   the banner, because the one rule that closes it was not carried across. That
   is the same defect the hub round already found and fixed once.

   So this file holds everything the kit's own markup needs. A preview loads
   main.css (theme B), then this, then its own page-specific block.

   NOTHING PAGE-SPECIFIC BELONGS HERE. If a rule only styles one page's own
   sections, it stays in that page's block.
   ========================================================================== */

/* ---- brushwork ----------------------------------------------------------- */
/* The sweep is anchored to the HEADING BLOCK, never the section, it runs behind
   the content, and it dries out before any column of body copy. */
section.bwsec{position:relative;isolation:isolate;overflow:hidden}
section.bwsec > .wrap{position:relative;z-index:2}
.hbwrap{position:relative;isolation:isolate}
.hbwrap > .kick,.hbwrap > h2,.hbwrap > h3{position:relative;z-index:2}
.bw{position:absolute;inset:-20px 0 0 0;overflow:hidden;pointer-events:none;z-index:0;line-height:0}
.bw > span{position:absolute;top:50%;transform-origin:center center}
.bw svg{display:block;width:100%;height:100%;overflow:visible}
@media (max-width:900px){.bw > span{height:72px !important;margin-top:-36px !important}}
/* Seated on the h2 and painted to read as paint (2026-10-19, Spencer: too faint).
   Centred on the kicker plus heading at ~20% it sat mostly behind the kicker and
   read as a pale ruled band. It now sits on the bottom of the wrapper, which is the
   bottom of the h2, and the box overhangs the column so a long sweep ends on its
   dry-brush tail instead of a hard clip. Opacity is forced over each stroke's
   inline alpha; the per-hue spread there was only 0.18 to 0.22. */
.hbwrap > .kicker{position:relative;z-index:2}
.hbwrap > .bw{inset:-20px -24px -16px -24px}
.hbwrap > .bw > span{top:auto !important;bottom:0;left:0 !important;max-width:100%;margin-top:0 !important;opacity:.46 !important}
@media (max-width:900px){.hbwrap > .bw{inset:-20px -8px -8px -8px}}

/* ---- banner parts -------------------------------------------------------- */
.crumb{font-size:13px;color:var(--mut);margin-bottom:18px}
.crumb a{color:var(--blue-d);font-weight:600}
.hublede{font-size:20px;line-height:1.55;color:var(--mut);max-width:60ch;margin-top:20px}
.ctas{display:flex;gap:16px;flex-wrap:wrap;margin-top:32px}
.btn-inline{display:inline-flex}
.trustbar{display:flex;flex-wrap:wrap;gap:10px;margin-top:28px}
.trustbar .chip{gap:7px}

/* ---- the shared inner-page banner ---------------------------------------- */
/* One treatment for every inner page, so /services/, /service-areas/ and the ten
   location pages all open the same way. Spencer's call, 2026-09-02. */
.pagehero{background:var(--navy);color:#fff;position:relative;overflow:hidden;isolation:isolate}
.pagehero .wrap{position:relative;z-index:2}
.pagehero img.hb{position:absolute;inset:0;width:100%;height:100%;object-fit:cover;z-index:0;opacity:.42}
.pagehero .hv{position:absolute;inset:0;z-index:1;
  background:linear-gradient(96deg,rgba(18,20,23,.95) 0%,rgba(18,20,23,.86) 42%,rgba(18,20,23,.52) 100%)}
.pagehero h1{color:#fff;font-size:clamp(40px,5.2vw,64px)}
.pagehero .crumb{color:#9aa3ad}
.pagehero .crumb a{color:#ffc233}
.pagehero .hublede{color:#c4c8cd}

/* ---- reviews ------------------------------------------------------------- */
.revhead{display:flex;justify-content:space-between;align-items:flex-end;gap:24px;flex-wrap:wrap}
.ratings{display:flex;align-items:center;gap:24px;flex-wrap:wrap}
.ratings img{height:44px;width:auto}
/* no avatar. The homepage pairs each testimonial with a clip-art portrait whose
   alt text calls it a real person, which is an open defect on that page. */
.rev{margin:0;background:#fff;border:1px solid var(--line);border-radius:8px;padding:28px;
  display:flex;flex-direction:column}
.rev blockquote{margin:0;color:var(--ink);font-size:17px;line-height:1.6;flex:1}
.rev blockquote::before{content:"“";display:block;font:800 44px/0.9 'Archivo',Georgia,serif;
  color:#f0a500;margin-bottom:12px}
.rev figcaption{margin-top:20px;padding-top:16px;border-top:1px solid var(--line);
  font-weight:700;color:var(--navy)}

/* ---- page chrome --------------------------------------------------------- */
/* Header and footer are the shipped ones; what is added here is the current-page
   mark and a mobile panel that actually opens. */
.sahdr{background:#fff;border-bottom:1px solid var(--line);position:relative;z-index:20}
.hdr-nav a[aria-current="page"]{color:var(--navy);box-shadow:inset 0 -3px 0 #f0a500;padding-bottom:3px}
/* closed by default and only ever opened by a click. A nav panel that renders
   OPEN over the hero was one of the four defects found on the hub round, and it
   came straight back on the location page when this rule was not carried over. */
.mnav{display:none;border-top:1px solid var(--line);background:#fff}
.mnav[data-open="true"]{display:block}
.mnav .wrap{padding-top:8px;padding-bottom:20px}
.mnav a{display:block;padding:14px 0;border-bottom:1px solid var(--line);
  font-weight:600;font-size:16px;color:var(--navy)}
.mnav a[aria-current="page"]{color:var(--navy);box-shadow:inset 3px 0 0 #f0a500;padding-left:12px}

/* ---- header nav dropdowns (Services, Service Areas) ----------------------
   Copied verbatim from the WordPress theme's main.css, which had this and
   this file did not (added there directly on 2026-09-04, never ported back).
   Two ways in, so it works with or without JS and with or without a pointer:
   :focus-within opens it for keyboard tabbing with zero script, :hover is
   gated to real pointers only so a tap does not leave it stuck open, and the
   hdr-drop-btn is the touch/no-JS fallback (inert here since this kit ships
   no JS for it; a tap still reaches the hub page through the link itself). */
.hdr-drop{position:relative;display:inline-flex;align-items:center}
.hdr-drop > a{display:inline-flex;align-items:center;gap:4px}
.hdr-caret{transition:transform 160ms var(--ease-out);flex:0 0 auto}
.hdr-drop-btn{display:none;background:none;border:0;padding:4px;margin-left:-6px;
  color:var(--navy);cursor:pointer;align-items:center}
.hdr-drop-panel{position:absolute;top:100%;left:0;margin-top:14px;min-width:200px;
  background:#fff;border:1px solid var(--line);border-radius:8px;
  box-shadow:0 1px 2px rgba(22,24,28,.06),0 16px 32px rgba(22,24,28,.14);
  padding:8px;list-style:none;
  opacity:0;visibility:hidden;transform:translateY(-6px);
  transition:opacity 160ms var(--ease-out),transform 160ms var(--ease-out),visibility 160ms}
.hdr-drop-panel.hdr-drop-panel-wide{min-width:420px;column-count:2;column-gap:4px}
.hdr-drop-panel a{display:block;padding:9px 12px;border-radius:5px;font-size:14px;
  font-weight:600;color:var(--ink);white-space:nowrap;break-inside:avoid}
.hdr-drop-panel a:hover,.hdr-drop-panel a:focus-visible{background:var(--alt);color:var(--navy)}
.hdr-drop:focus-within .hdr-drop-panel{opacity:1;visibility:visible;transform:translateY(0)}
.hdr-drop:focus-within .hdr-caret{transform:rotate(180deg)}
@media (hover:hover) and (pointer:fine){
  .hdr-drop:hover .hdr-drop-panel{opacity:1;visibility:visible;transform:translateY(0)}
  .hdr-drop:hover .hdr-caret{transform:rotate(180deg)}
  .hdr-drop-btn{display:none !important}
}
@media (hover:none),(pointer:coarse){
  .hdr-drop-btn{display:inline-flex}
}
/* the touch route in. assets/js/chrome.js sets data-open on the .hdr-drop when
   the caret button is tapped; without this rule that attribute changes nothing
   and the panel stays shut on every touch screen. Added 2026-09-09 with the
   script, because the two are one mechanism and shipping either alone is a
   dropdown that cannot be opened by finger. */
.hdr-drop[data-open="true"] .hdr-drop-panel{opacity:1;visibility:visible;transform:translateY(0)}
.hdr-drop[data-open="true"] .hdr-caret{transform:rotate(180deg)}
@media (prefers-reduced-motion: reduce){
  .hdr-caret,.hdr-drop-panel{transition:none}
}
.mnav a.btn{border-bottom:0;padding:16px 32px;color:#17191c;justify-content:center}
@media (min-width:920px){.mnav{display:none !important}}

/* ---- the estimate block -------------------------------------------------- */
.qgrid{display:grid;grid-template-columns:minmax(0,1fr) minmax(0,0.92fr);gap:64px;align-items:start}
.qform{background:#fff;border:1px solid var(--line);border-radius:8px;padding:28px;
  box-shadow:0 1px 2px rgba(22,24,28,.05),0 12px 32px rgba(22,24,28,.08)}
.qform h3{font-size:24px}
/* The GHL form is a fixed-height card that scrolls INSIDE, the bigeasypatios.com
   pattern (Spencer, 2026-09-14: "it should be scrolling form"). !important because
   form_embed.js writes the form's full height (about 1,165px) into the iframe's
   inline style, which would stretch the card down the whole section. */
.qform-ghl{padding:22px 22px 14px;border-top:5px solid #f0a500}
.qform-ghl h3{margin:0 0 14px}
.qform-ghl iframe{display:block;width:100%;height:560px !important;border:0;border-radius:4px}
.qlist li{padding:14px 0;border-top:1px solid var(--line);color:var(--ink);
  display:grid;grid-template-columns:22px minmax(0,1fr);gap:12px;align-items:start}
.qlist li::before{content:"";width:9px;height:9px;border-radius:50%;background:#f0a500;
  margin-top:9px;margin-left:6px}
@media (max-width:940px){.qgrid{grid-template-columns:minmax(0,1fr);gap:40px}}

/* reduced motion means gentler, never zero: colour and opacity stay, movement goes */
@media (prefers-reduced-motion: reduce){
  .btn:hover{transform:none}
}

/* ==========================================================================
   DARK SECTIONS ON INNER PAGES  (2026-09-10)

   main.css already turns type white inside .dark. What it does NOT do is deal
   with the two things a section carries that have their own light ground: a
   card, and the decorative brush swash behind a heading. Both go wrong the
   moment a section is darkened, and both go wrong SILENTLY:

     - .coat and .condcard set their own background (#fff and --alt). Under
       .dark the h3 turns #fff and the paragraph #c4c8cd, so the card renders
       white text on a white card. Nothing errors and a section-level contrast
       walk still reports the section's own navy as the ground.
     - .bw is a pale coloured swash painted BEHIND the heading. On paper it
       lifts the heading; on navy it sits under white type and drops the
       contrast instead.

   So cards get a translucent white ground on dark, and the swash is suppressed
   there, because a dark section already carries its colour in the ground.
   ========================================================================== */
section.dark .bw{display:none}

section.dark .coat,
section.dark .condcard{background:rgba(255,255,255,.07);border-color:rgba(255,255,255,.20)}
section.dark .coat h3,
section.dark .condcard h3{color:#fff}
section.dark .coat p,
section.dark .condcard p,
section.dark .coat .mut,
section.dark .condcard .mut{color:#c9ced4}
section.dark .coatb .kick{color:#ffc233}
/* .30 measured 2.68:1 against the card ground, under the 3.0 floor a 30px
   run has to clear. Faint is the intent; illegible is not. */
section.dark .condcard .cnum{color:rgba(255,255,255,.42)}

/* .why is a rule-topped column, not a card, so it only needs its rule back */
section.dark .why{border-top-color:rgba(255,255,255,.34)}

/* DELETED 2026-09-10, same day it was added. It read
     section.dark + section, section.dark{border-top-color:rgba(255,255,255,.16)}
   which is (0,1,1) and therefore outranks page-matrix.css's own
     .fpdark{border-top:3px solid #f0a500}  and  .closeA{border-top:3px solid #f0a500}
   at (0,1,0). The matrix pages load page-kit.css too, so a rule written for the
   inner pages reached all 54 of them and turned 108 deliberate amber accents
   grey, verified by sampling the rendered pixels with the rule in and out
   (rgb(240,165,0) -> rgb(59,61,64)). The matrix pages were explicitly out of
   scope and no PHP of theirs was touched, which is exactly why this was easy to
   miss: nothing in the diff pointed at them.

   The hairline it was softening is cosmetic. It is not worth a selector that can
   reach a page type this file is not supposed to style. If a dark section ever
   needs its own top rule, give that SECTION a class and target the class. */

/* the ghost button reads as a thin dark outline; on navy it needs the on-dark
   treatment even when a caller forgets to ask for it */
section.dark .btn-ghost{border-color:rgba(255,255,255,.55);color:#fff}
section.dark .btn-ghost:hover{background:rgba(255,255,255,.14);border-color:#fff}
section.dark .sm,
section.dark .subhead{color:#c9ced4}
section.dark a:not(.btn){color:#ffc233}

/* ==========================================================================
   THE CLOSING CTA BAND, every page  (2026-09-15)

   The homepage's .h-cta ("Two coats, quoted up front") above the footer on
   every inner page, on Spencer's instruction. Every value is copied from
   build_improved_home.py (.h-cta, .h-gr.on-navy.mode-edge, .h-rule-top,
   .btn-a, .btn-g) so the two bands render alike. Class .ctab and not .h-cta
   because page-home.css scopes that under .hx, which only the homepage has.

   The button rules sit at (0,2,1) on purpose: main.css ships
   a:hover{color:var(--navy);text-decoration:underline} at (0,1,1), which is
   the leak that turned the homepage buttons navy on hover on 2026-09-14.
   ========================================================================== */
/* font-size, line-height and the h2's letter-spacing are PINNED, not inherited. The homepage
   runs 17px/1.62 with display headings at -.02em/1.08; main.css gives inner pages 16px/1.65
   and -.03em/1.12. Inherited, the band measured 2px taller headings set about 10px narrower on
   live (parity run against the homepage, 2026-09-15), so it has to name its own values. */
.ctab{position:relative;isolation:isolate;overflow:hidden;background:var(--navy);color:#fff;
  padding:96px 0;text-align:center;font-size:17px;line-height:1.62}
.ctab-bg{position:absolute;inset:0;z-index:-3}
.ctab-bg img{width:100%;height:100%;object-fit:cover}
.ctab-veil{position:absolute;inset:0;z-index:-2;
  background:linear-gradient(100deg,rgba(18,20,24,.90) 0%,rgba(18,20,24,.84) 46%,rgba(18,20,24,.70) 100%)}
.ctab-veil::after{content:"";position:absolute;inset:0;
  background:linear-gradient(180deg,rgba(18,20,24,.56) 0%,rgba(18,20,24,.10) 24%,
    rgba(18,20,24,.10) 76%,rgba(18,20,24,.58) 100%)}
/* amber rule on top, the same one accent the homepage band opens with */
.ctab::before{content:"";position:absolute;left:0;right:0;top:0;height:3px;background:#f0a500;z-index:1}
.ctab::after{content:"";position:absolute;left:0;right:0;bottom:0;height:1px;
  background:rgba(255,255,255,.12);z-index:-1}
.ctab .wrap{position:relative;z-index:1}
.ctab-sw{display:flex;height:8px;max-width:760px;margin:0 auto 34px;border-radius:99px;overflow:hidden}
.ctab-sw i{flex:1}
.ctab h2{color:#fff;font-size:clamp(30px,4vw,52px);margin:0 0 12px;letter-spacing:-.02em;line-height:1.08}
.ctab p{color:rgba(255,255,255,.86);font-size:18px;margin:0 0 26px}
.ctab-act{display:flex;flex-wrap:wrap;gap:14px;justify-content:center;align-items:center}
.ctab a.ctab-est{background:#f0a500;color:#16181c;text-decoration:none;
  font-family:'Archivo','Arial Narrow',system-ui,-apple-system,Arial,sans-serif;
  font-weight:800;font-size:16px;padding:15px 28px;border-radius:2px;display:inline-block;
  transition:background-color 180ms var(--ease-out)}
.ctab a.ctab-tel{border:1px solid rgba(255,255,255,.55);color:#fff;text-decoration:none;
  font-weight:700;font-size:16px;padding:14px 26px;border-radius:2px;display:inline-block;
  transition:background-color 180ms var(--ease-out),border-color 180ms var(--ease-out)}
.ctab a.ctab-est:hover{background:#ffb61f;color:#16181c;text-decoration:none}
.ctab a.ctab-tel:hover{background:rgba(255,255,255,.14);border-color:#fff;color:#fff;
  text-decoration:none}
@media (max-width:760px){.ctab{padding:68px 0;font-size:16px}}
