/* ═══════════════════════════════════════════════════════════════
   PANEL MANAGEMENT SOFTWARE — landing page theme
   Loads AFTER css/base-styles.css. The shared header, mobile menu,
   .footer-min and the lead-modal shell come from the base file;
   this sheet re-tints them and styles the whole middle of the page
   (everything prefixed .pm-).

   Built on the ai-girlfriend-app sheet — same structure, same shared
   furniture — re-themed for a B2B research-operations buyer.

   LIGHT THEME (re-themed from the near-black violet build). The reference
   is innovatemr.com: a white page carried by one sky blue and one spring
   green, light blue tinted cards, and headings in a near-black slate. The
   page has NO dark section any more — the band that used to be #070A16 is
   now the deep sky --pm-band, which is what gives the middle of the page
   its one strong surface.

   Design rules this sheet follows, so later edits stay coherent:
   · THREE surfaces, never more: white -> #EAF3FA (--pm-paper-2) ->
     #D7EAF7 (--pm-band, which the footer runs). Each is ~4-5 L* below the
     last, which is the smallest step that still survives a cheap laptop
     panel; sections alternate so no two neighbours share one. The one
     exception is .pm-sec--brand (the features section), set by hand to the
     full brand blue — it is the page's single saturated block and the only
     place the copy is not --pm-head / --pm-body. The blue->green gradient
     is an ACCENT, never a section wash.
   · The container runs the base 1600px, so every prose block
     carries its own max-width instead.
   · Cards are hairline-bordered and shadowless at rest; the lift,
     the colour and the pointer spotlight all arrive on hover. On a tinted
     section they run white; on white they run tinted.
   · Green (--pm-green) is reserved for VERIFICATION moments — the
     data-quality checks, the verified/rewarded chips, the live dot. Blue
     is the page accent, so green is the only colour left that can carry a
     signal; spending it decoratively kills it.
   · --pm-mint is the "happening right now" green: the two live
     pulses only, never a decorative tick.
   · Text on every surface is --pm-head / --pm-body, except on the brand
     blue — see the note under .pm-sec--brand. There is no white-on-dark
     pair left in this sheet, and on a LIGHT blue white would be the wrong
     answer anyway: it measures 2.9:1 there against ink's 5.7:1.
   ═══════════════════════════════════════════════════════════════ */
:root {
  /* base-styles.css reads these for the shared shell */
  --primary: #1FA2E0;
  --primary-dark: #0B7EB8;
  --accent: #0DB1C4;
  --accent2: #00B887;
  --secondary: #12212A;
  --gradient-dark-card: linear-gradient(150deg, #FFFFFF 0%, #F2F9FD 64%);
  --gradient-cta: linear-gradient(115deg, #1FA2E0 0%, #0DB1C4 55%, #00B887 100%);
  --shadow-cta: 0 10px 28px rgba(31, 162, 224, 0.34);

  /* ── Page tokens ── */
  /* The three surfaces. --pm-band replaced the near-black slab the features
     section used to run on: a light page still needs one band that is
     unmistakably its own, and a third tint does that without reintroducing
     a dark half. */
  --pm-band: #D7EAF7;
  --pm-band-2: #E4F1FA;
  --pm-head: #12212A;
  --pm-body: #000000;
  --pm-muted: #8FA3AE;
  --pm-line: #DCE8F0;
  --pm-line-2: #EDF4F9;
  /* hairlines for the tinted surfaces — a --pm-line hairline disappears
     on --pm-band, so the band's own cards and rules use these instead */
  --pm-bline: rgba(16, 43, 58, 0.10);
  --pm-bline-2: rgba(16, 43, 58, 0.06);
  --pm-paper: #FFFFFF;
  --pm-paper-2: #EAF3FA;
  --pm-sky: #1FA2E0;
  /* The sheet's SMALL-TEXT blue — the eyebrow pills, the video ring, the ghost
     button, the footer hover. It has been walked down twice for contrast and
     the last step is the one that matters: an eyebrow is 12.5px uppercase
     sitting on its own 9%-blue pill, so the ground is #D7EBF8 on a tinted
     section, not white. #0B7EB8 measured 3.6:1 there and #0A76AB 4.07:1; this
     lands at 4.75:1 on the pill and 5.2:1 on white. Do not lighten it. */
  --pm-sky-d: #096B9B;
  --pm-aqua: #0DB1C4;
  --pm-green: #00B887;
  --pm-mint: #2ED3A8;
  /* the pale mint block the reference site sets its photographs on */
  --pm-mint-2: #A9F0D6;
  --pm-sky-2: #58C4EE;
  --pm-grad: linear-gradient(115deg, #1FA2E0 0%, #1FA2E0 55%, #1FA2E0 100%);
  --pm-grad-b: linear-gradient(115deg, #1FA2E0 0%, #0DB1C4 100%);
  /* THE FILLED-CTA GREEN. Blue is the page — the nav, the links, the icon
     tiles, the band — so the one thing a visitor is meant to press is the one
     thing that is NOT blue. It is the page's own green, not a stock one:
     --pm-green (#00B887) walked down until a white label holds on it. That
     matters here more than anywhere, because 14.5-15.5px white on a fill needs
     4.5:1 and the greens that look right at a glance do not have it — the
     theme accent measures 2.56:1 and a typical bootstrap-ish #28A745 3.13:1.
     This is 4.69:1 at rest and 6.62:1 on hover. Do not lighten past ~#068A66. */
  --pm-btn: #199947;
  --pm-btn-h: #037e30;
  /* the deep blue the buttons used to run — still the value for the things
     that are NOT buttons but were sharing that token: the migration band, the
     stat figures and the open FAQ disc. Blue is the page's colour; green is
     reserved for "press this". */
  --pm-deep: #0A76AB;
  --pm-grad-soft: linear-gradient(115deg, rgba(31, 162, 224, 0.12), rgba(0, 184, 135, 0.12));
  --pm-r: 18px;
  --pm-r-lg: 26px;
  --pm-pad: 96px;
  --pm-display: 'Sora', 'Segoe UI', system-ui, sans-serif;
  --pm-text: 'Plus Jakarta Sans', 'Segoe UI', system-ui, sans-serif;
}

body {
  font-family: var(--pm-text);
  color: var(--pm-body);
  background: var(--pm-paper);
  font-size: 16.5px;
  line-height: 1.72;
  -webkit-font-smoothing: antialiased;
  overflow-x: hidden;
}

/* text-wrap: balance evens the last line of a heading instead of leaving
   one orphan word; `pretty` does the orphan-only version for body copy,
   which is the right call there because `balance` caps out at a few
   lines and is expensive on long paragraphs. Both no-op where
   unsupported. */
h1, h2, h3, h4, h5 {
  font-family: var(--pm-display); color: var(--pm-head); letter-spacing: normal;
  /* text-wrap: balance; */
}
p, li { text-wrap: pretty; }

/* base-styles ships scroll-margin-top: 90px against an 84px header — 6px
   of clearance reads as the heading touching the bar on an anchor jump */
section[id] { scroll-margin-top: 106px; }

::selection { background: rgba(13, 177, 196, 0.22); color: var(--pm-head); }

/* ── FOCUS ───────────────────────────────────────────────────
   Every interactive element on this page is custom, so none of them
   inherit the .btn-* focus rings base-styles defines. One ring, two
   tints — the deeper one for the two surfaces that sit lighter than the
   page (the hero wash and the sky band). */
:where(a, button, input, textarea, [tabindex]):focus-visible {
  outline: 2px solid var(--pm-sky);
  outline-offset: 3px;
  border-radius: 6px;
}
/* the hero wash and the sky band sit lighter than the page, so the ring
   goes a step deeper there to keep the same contrast against them */
.pm-sec--brand :where(a, button):focus-visible,
.pm-hero :where(a, button):focus-visible,
.og-header:not(.scrolled) :where(a, button):focus-visible {
  outline-color: var(--pm-sky-d);
}
.pm-btn:focus-visible, .nav-cta:focus-visible { outline-offset: 4px; border-radius: 999px; }

/* ═══════════════ SCROLL PROGRESS RAIL ═══════════════
   scaleX driven from js/pmw.js inside a rAF. */
.pm-progress {
  position: fixed; top: 0; left: 0; right: 0; height: 3px;
  background: var(--pm-grad);
  transform: scaleX(0); transform-origin: 0 50%;
  z-index: 1200; will-change: transform;
}

/* ═══════════════ HEADER ═══════════════
   Transparent over the hero, solid white once .scrolled — but the hero is a
   near-white wash now, so "transparent" no longer means "on dark". Everything
   that used to run white at the top of the page (nav labels, burger bars, the
   reversed logo) runs ink from the first pixel instead; the only thing
   .scrolled still changes is the bar's own surface. */
.og-header {
  position: fixed; top: 0; left: 0; right: 0; z-index: 1000;
  background: transparent;
  border-bottom: 1px solid transparent;
  transition: background .32s ease, box-shadow .32s ease, border-color .32s ease, -webkit-backdrop-filter .32s ease;
  transition: background .32s ease, box-shadow .32s ease, border-color .32s ease, backdrop-filter .32s ease;
  transition: background .32s ease, box-shadow .32s ease, border-color .32s ease, backdrop-filter .32s ease, -webkit-backdrop-filter .32s ease;
  box-shadow: none;
  backdrop-filter: none; -webkit-backdrop-filter: none;
}
.og-header.scrolled,
.og-header:has(.mobile-menu.open) {
  background: rgba(255, 255, 255, 0.94);
  backdrop-filter: saturate(160%) blur(14px);
  -webkit-backdrop-filter: saturate(160%) blur(14px);
  border-bottom-color: var(--pm-line);
  box-shadow: 0 10px 34px rgba(16, 43, 58, 0.07);
}

/* The cross-fade is over. base-styles stacks a reversed wordmark over the
   full-colour one and swaps them on scroll, which only makes sense while the
   bar starts out on something dark. The white file is gone from the markup
   (see the note there) and this un-stacks what is left — base-styles absolutely
   positions .logo-img--dark at opacity 0, so without both lines the header
   would carry an invisible, zero-width logo. */
.logo { display: inline-flex; align-items: center; position: relative; }
.logo-img--dark { position: static; opacity: 1; }

.nav-links > li > a {
  font-family: var(--pm-text);
  font-size: 15px; font-weight: 600; letter-spacing: normal;
  color: #000000;
  transition: color .22s ease;
}
.nav-links > li > a:hover,
.og-header.scrolled .nav-links > li > a:hover { color: var(--pm-sky); }

/* shared scroll-spy (common-js/nav-active.js) picks this up — one value now,
   because the bar is light in both states */
.og-header { --nav-active-color: var(--pm-sky); }

/* base-styles ships this CTA in the amber theme it was written for — an
   amber fill, an amber glow, an amber focus ring, a near-black arrow
   chip, and in the mobile sheet a hardcoded #1FA2E0→#0B7EB8 gradient.
   All of it is restated here so the desktop CTA, the mobile-sheet CTA
   and .pm-btn--primary read as one button: same gradient, same
   hover shift toward blue, same glow. */
.nav-cta {
  font-family: var(--pm-text);
  font-size: 14.5px; font-weight: 700; letter-spacing: normal;
  color: #fff !important;
  background: var(--pm-btn);
  padding: 9px 10px 9px 22px; border-radius: 999px;
  box-shadow: 0 8px 22px rgba(7, 132, 95, 0.26);
  transition: transform .24s cubic-bezier(.22,1,.36,1), box-shadow .24s ease, background-color .24s ease;
}
.nav-cta:hover {
  transform: translateY(-2px);
  background: var(--pm-btn-h);
  box-shadow: 0 12px 30px rgba(7, 132, 95, 0.34);
}
/* the arrow chip is a solid near-black square in base; a translucent
   white disc sits on the gradient the way the inline SVG arrow does
   inside .pm-btn--primary */
.nav-cta::after {
  background: rgba(255, 255, 255, 0.22);
  color: #fff;
  border-radius: 50%;
  width: 26px; height: 26px;
  font-size: .78rem; font-weight: 700;
}
/* base sets `outline: 3px solid rgba(31, 162, 224,.55)` here and wins on
   file order over the generic :where() focus rule */
.nav-cta:focus-visible { outline: 2px solid var(--pm-sky-d); }

/* The burger ships at 26x26 — the only control that opens the menu on a phone,
   at little over half the 44px a thumb needs. It cannot be fixed with padding
   or a local width: ../common-css/header.css loads AFTER this sheet and sets
   `.og-header .hamburger { width: var(--hdr-burger) }` at higher specificity,
   so both lose. The token is the way in — it is declared on :root, and a value
   set here on .og-header is inherited from a nearer ancestor, which wins no
   matter what order the sheets load in. Scoped to .og-header so the other 17
   pages sharing header.css are untouched. */
.og-header { --hdr-burger: 44px; }
.og-header .hamburger { margin-right: -9px; }
.hamburger span { background: var(--pm-head); transition: transform .3s ease, opacity .2s ease; }

.mobile-menu { background: #fff; border-top: 1px solid var(--pm-line); }
.mobile-menu a { color: var(--pm-head); font-family: var(--pm-text); font-weight: 600; border-bottom-color: var(--pm-line-2); }
.mobile-menu a:hover, .mobile-menu a.is-active { color: var(--pm-sky); }
.mobile-menu .nav-cta {
  color: #fff !important;
  background: var(--pm-btn);
  border-color: rgba(255, 255, 255, 0.3);
  box-shadow: 0 12px 30px rgba(7, 132, 95, 0.30), 0 2px 6px rgba(16, 43, 58, 0.08);
  transition: background-color .24s ease, box-shadow .24s ease;
}
.mobile-menu .nav-cta:hover,
.mobile-menu .nav-cta:active {
  background: var(--pm-btn-h);
  box-shadow: 0 16px 36px rgba(7, 132, 95, 0.38);
}
.mobile-menu .nav-cta::after { background: rgba(255, 255, 255, 0.22); color: #fff; }

/* the six nav items + logo + CTA need ~880px before they crowd */
@media (max-width: 900px) {
  .nav-links { display: none; }
  /* base-styles gives it 4px of padding, which measures 26x26 on a phone —
     well under the 44px a thumb needs, and it is the ONLY way to open the menu.
     Padding buys the hit area and the negative margin gives the layout back,
     so the burger looks identical and nothing in the header shifts. Scoped
     here rather than in base-styles.css, which 17 other landing pages share. */
  .hamburger { display: flex; }
}

/* ═══════════════ SHARED FURNITURE ═══════════════ */

.pm-sec { padding: var(--pm-pad) 0; position: relative; }
.pm-sec--paper { background: var(--pm-paper-2); }
/* The deep sky band that replaced the page's near-black slab. It is the one
   surface strong enough to hold a section on its own, so it is spent ONCE —
   on the features grid — exactly where the dark band used to sit. The
   gradient runs top-down rather than flat so the band lifts off the section
   above it instead of butting against it as a hard step, and the cards on it
   run white (see .pm-svc__card): tinted cards on a tinted band lose their
   edges the moment the page is viewed on an uncalibrated screen. */
/* #0C79B0, not the brand #1FA2E0 it was set to by hand. The band wants white
   copy on it — that is the look, and it is why the two .pm-head rules above kept
   being pushed to #fff — but white on #1FA2E0 measures 2.88:1, under the 3.0
   even 44px display type needs and well under the 4.5 the 17px paragraph does.
   This is the same hue two steps down: white lands at 4.80:1 on it and the band
   still reads as the brand blue. Revert this one line to #1fa2e0 if the brighter
   band matters more than the copy on it — but then flip the .pm-sec--brand text
   rules to a dark ink (#0F2E3B, 4.95:1), because at that lightness dark wins. */
.pm-sec--brand {
  background: #0C79B0;
}
/* The soft lift that keeps the band from reading as a flat rectangle — it
   took over from the film grain the dark slab carried, which on a light
   surface reads as dirt rather than texture.

   45%, not the 85% it started at: the band's whole job is to sit a visible
   step BELOW the tinted section above it, and at 85% the top-right corner
   came out lighter than that section — the step inverted across the seam and
   the band read as a glow spilling down the page rather than a surface. */
.pm-sec--brand::before {
  content: ""; position: absolute; inset: 0; pointer-events: none;
  background: radial-gradient(1000px 420px at 82% 6%, rgba(255, 255, 255, .45), transparent 64%);
  display: none;
}
.pm-sec--brand > .container { position: relative; z-index: 1; }
/* The band's copy is white, set with the .pm-head rules further down — see the
   note there for why it is scoped rather than global, and the note on
   .pm-sec--brand's background for why that blue is two steps deeper than the
   brand blue. #0B6FA3 is the crossover: lighter than that and dark ink wins,
   darker and white does. */

.pm-eyebrow {
  display: inline-flex; align-items: center; gap: 9px;
  font-size: 12.5px; font-weight: 700; letter-spacing: .14em; text-transform: uppercase;
  /* --pm-sky-d, not --pm-sky: this is 12.5px uppercase, the smallest text on
     the page, and the brand blue on white measures 2.88:1 (2.56 on the tint). */
  color: var(--pm-sky-d);
  background: rgba(31, 162, 224, 0.09);
  border: 1px solid rgba(31, 162, 224, 0.18);
  padding: 7px 16px; border-radius: 999px;
}
/* On the band and on the hero wash the flat 9%-alpha pill loses its edge, so
   both get a white ground under the tint — same pill, one step brighter.

   SOLID white, not the .96→.82 gradient this started as. Against the pale hero
   wash the difference was invisible, but the band is saturated blue: at the
   .82 end it blended to #D6EEFA and dropped the 12.5px label to 3.7:1. A pill
   whose contrast depends on what is behind it is not a pill, it is a tint. */
.pm-sec--brand .pm-eyebrow,
.pm-hero .pm-eyebrow {
  color: var(--pm-sky-d);
  background: #fff;
  border-color: rgba(31, 162, 224, .28);
  box-shadow: 0 6px 18px rgba(16, 43, 58, .07);
}
.pm-dot {
  width: 7px; height: 7px; border-radius: 50%; background: var(--pm-green);
  box-shadow: 0 0 0 0 rgba(0, 184, 135, .7);
  animation: pmPulse 2.4s infinite;
  /* never let the pill squeeze the dot into an ellipse when the label is long */
  flex: 0 0 auto;
}
@keyframes pmPulse {
  0%   { box-shadow: 0 0 0 0 rgba(0, 184, 135, .55); }
  70%  { box-shadow: 0 0 0 9px rgba(0, 184, 135, 0); }
  100% { box-shadow: 0 0 0 0 rgba(0, 184, 135, 0); }
}

/* ── the eyebrow on phones ────────────────────────────────────────────────
   The hero label is 36 uppercase characters: at 12.5px/.14em it measures 350px
   against a 390px screen, so it wrapped to two lines INSIDE a 999px radius —
   which stops reading as a pill and starts reading as a stadium with the status
   dot stranded in the empty space beside the break. Tightening the type keeps it
   on ONE line, which is the whole point of an eyebrow: one glance, one row.
   Scoped to the hero: the section eyebrows are 18 characters at most and fit
   on one line at 320px as they are, so they keep the designed 12.5px. */
@media (max-width: 768px) {
  .pm-hero .pm-eyebrow {
    font-size: 11px;
    letter-spacing: .085em;
    gap: 8px;
    padding: 6px 14px;
  }
}
/* 11px still broke between 361px and 400px, and a third fixed step would only
   move the seam somewhere else — so the last leg scales with the viewport. The
   clamp holds the label on one line from 320px up and stops shrinking at 9px,
   below which uppercase .06em tracking stops being readable. */
@media (max-width: 400px) {
  .pm-hero .pm-eyebrow {
    font-size: clamp(9px, 2.65vw, 10.5px);
    letter-spacing: .055em;
    gap: 7px;
    padding: 6px 12px;
  }
}

.pm-head { max-width: 900px; margin: 0 auto 56px; text-align: center; }
.pm-head .pm-eyebrow { margin-bottom: 18px; }
/* text-wrap: balance, because these titles were shortened to fit and the
   break point is now the only thing that can spoil them. "Choose the Right
   Panel Software Model" is 37 characters against a container that holds ~31
   at 46px, so the default greedy wrap dropped "Model" onto a line of its own.
   balance splits the words evenly instead, and it re-solves itself at every
   width rather than needing a hand-placed <br> per breakpoint. */
.pm-head h2 {
  font-size: clamp(28px, 3.1vw, 46px); line-height: 1.16; font-weight: 700; margin: 0 0 16px;
  text-wrap: balance;
}
.pm-head p { font-size: 17px; line-height: 1.75; margin: 0 auto; max-width: 760px; color: var(--pm-body); }

/* WHITE COPY BELONGS TO THE BLUE BAND, AND ONLY TO IT. Both of the rules above
   carried `color:#fff` for a while, which is right for the one section that
   runs on blue and wrong for the other eleven — every heading and intro
   paragraph on the page went white-on-white. Scope it to the band. */
.pm-sec--brand .pm-head h2,
.pm-sec--brand .pm-head p,
.pm-sec--brand { color: #fff; }

/* left-aligned variant — used where the head sits beside artwork
   instead of centred over a grid */
.pm-head--left { text-align: left; margin: 0 0 34px; max-width: 640px; }
.pm-head--left p { margin-left: 0; }

.pm-grad-text {
  background: var(--pm-grad); -webkit-background-clip: text; background-clip: text;
  -webkit-text-fill-color: transparent; color: transparent;
}

/* buttons */
.pm-btn {
  display: inline-flex; align-items: center; justify-content: center; gap: 10px;
  font-family: var(--pm-text); font-size: 15.5px; font-weight: 700; letter-spacing: normal;
  padding: 15px 30px; border-radius: 999px; border: 1px solid transparent;
  cursor: pointer; text-decoration: none; white-space: nowrap;
  transition: transform .24s cubic-bezier(.22,1,.36,1), box-shadow .24s ease, background-position .55s ease, background-color .24s ease, color .24s ease, border-color .24s ease;
}
.pm-btn svg { width: 17px; height: 17px; flex-shrink: 0; }
  /* no-repeat is load-bearing, not tidiness. background-size is >100% here so
     background-position can slide the ramp on hover, and the default `repeat`
     tiles it. Because the gradient is ANGLED, the seam between tiles is a
     diagonal that clips the box corner and lands the ramp's bright end hard
     against its dark start — a 1px light streak up the left edge. */
.pm-btn--primary {
  color: #fff; background: var(--pm-btn);
  box-shadow: 0 12px 30px rgba(7, 132, 95, 0.30);
}
/* the ramp used to slide on hover (that is what background-size: 190% was for);
   with a flat fill there is nothing to slide, so the hover is a colour step */
.pm-btn--primary:hover {
  transform: translateY(-3px); background: var(--pm-btn-h);
  box-shadow: 0 16px 38px rgba(7, 132, 95, 0.38);
}
/* The secondary button. It was a glass pill — 5% white over blur — which is a
   treatment that only exists on a dark ground; on a light page the same rule
   renders as an invisible button. It is an outlined pill now, the same shape
   the reference site's secondary action uses. Currently unused in the markup;
   left correct rather than left as a trap for the next page that reaches for it. */
.pm-btn--ghost {
  color: var(--pm-sky-d); background: #fff; border-color: rgba(31, 162, 224, .40);
  box-shadow: 0 2px 8px rgba(16, 43, 58, .05);
}
.pm-btn--ghost:hover {
  background: rgba(31, 162, 224, .07); border-color: var(--pm-sky);
  transform: translateY(-3px); box-shadow: 0 10px 24px rgba(31, 162, 224, .18);
}
.pm-btn--dark { color: #fff; background: var(--pm-head); }
.pm-btn--dark:hover { transform: translateY(-3px); box-shadow: 0 14px 32px rgba(16, 43, 58, 0.28); }
.pm-btn--white { color: var(--pm-head); background: #fff; }
.pm-btn--white:hover { transform: translateY(-3px); box-shadow: 0 16px 36px rgba(0, 0, 0, 0.24); }
/* The outlined pill for DARK grounds. --ghost is the light-ground outline (white
   fill, blue rule); dropped on the FAQ card it would render as a second white
   button and kill the primary/secondary split. This one is the mirror: white
   rule and label over a transparent fill, filling to a low-alpha white on hover
   rather than lifting a shadow that has nothing to fall on. The 6% fill is not
   decoration — an unfilled outline on a gradient reads as a disabled control. */
.pm-btn--outline {
  color: #fff; background: rgba(255, 255, 255, .06);
  border-color: rgba(255, 255, 255, .55);
}
.pm-btn--outline:hover {
  background: rgba(255, 255, 255, .16); border-color: #fff;
  transform: translateY(-3px); box-shadow: 0 14px 32px rgba(0, 0, 0, .22);
}

/* the pointer spotlight every hover-card shares — js/pmw.js writes
   --mx / --my, the card paints a soft radial under the content */
.pm-spot { position: relative; isolation: isolate; }
.pm-spot::after {
  content: ""; position: absolute; inset: 0; border-radius: inherit; z-index: -1;
  opacity: 0; transition: opacity .3s ease; pointer-events: none;
  background: radial-gradient(340px circle at var(--mx, 50%) var(--my, 50%), rgba(31, 162, 224, .13), transparent 62%);
}
.pm-spot:hover::after { opacity: 1; }
/* on the sky band the same 13% wash is invisible — the surface is already
   tinted, so the spotlight has to run white to register at all */
.pm-sec--brand .pm-spot::after {
  background: radial-gradient(340px circle at var(--mx, 50%) var(--my, 50%), rgba(31, 162, 224, .16), transparent 62%);
}

/* scroll reveal — js/pmw.js owns the observer (main.js never
   watches .reveal itself) */
.reveal { opacity: 0; transform: translateY(26px); transition: opacity .7s cubic-bezier(.22,1,.36,1), transform .7s cubic-bezier(.22,1,.36,1); }
.reveal.is-visible { opacity: 1; transform: none; }
@media (prefers-reduced-motion: reduce) {
  .reveal, .reveal.is-visible { opacity: 1; transform: none; transition: none; }
}

/* ═══════════════ HERO ═══════════════ */
.pm-hero {
  position: relative; overflow: hidden;
  /* A WASH, not a wall of colour. The hero used to be near-black, which meant
     the whole hero could be one flat field and every element on it borrowed
     its contrast from the background. On white there is no such loan: the
     ground has to stay quiet so the headline, the shot and the button are the
     only things carrying weight. Pale sky at the top, plain white by the time
     the USP cards overlap the bottom edge, so those cards land on white and
     keep the shadow they were drawn with. */
  /* background:
    radial-gradient(1100px 620px at 84% 6%, rgba(31, 162, 224, .13) 0%, transparent 62%),
    radial-gradient(760px 520px at 6% 4%, rgba(0, 184, 135, .09) 0%, transparent 60%),
    linear-gradient(180deg, #EFF7FC 0%, #F8FCFE 46%, #FFFFFF 100%); */
  /* padding-bottom is the USP cards' clearance, not decoration: they ride up
     into it by -50px (see .pm-usp__grid), so what is left here is the gap
     between the terms bar and the top of a card. Shrink one, check the other. */
  padding: 100px 0px 24px;
  color: var(--pm-body);
  background: var(--pm-paper);

  /* The four hues the hero is lit with. They stayed their own tokens while the
     hero was navy and the page ramp was too dark to show on it; on the wash
     they are simply the page palette, kept as tokens because the headline, the
     three point icons, the chips and the hero button all have to move together
     if the accent ever changes again. */
  --h-sky:  #1FA2E0;   /* the accent — headline gradient, chip dots */
  --h-sky-l: #58C4EE;  /* mid tint — the light end of a ramp */
  --h-green: #00B887;  /* the verification accent */
  --h-deep: #0B7EB8;   /* the deep end — button ramp, ring text */

  /* The artwork's width, declared once because TWO elements must agree on it:
     .pm-shot is sized by it and .pm-hero__visual is capped by it so the chips
     have the artwork to hang off rather than the grid cell. Change it here. */
  --shot-w: 600px;
}
.pm-hero__bg { position: absolute; inset: 0; pointer-events: none; overflow: hidden; display: none; }
/* the blooms were 50%-opacity colour discs on near-black, which on a white
   wash print as two coloured smudges — they run a third of that strength and
   pale, so they read as light rather than paint */
.pm-bloom { position: absolute; border-radius: 50%; filter: blur(90px); opacity: .5; will-change: transform; }
.pm-bloom--tl { width: 520px; height: 520px; top: -160px; left: -140px; background: rgba(31, 162, 224, .16); }
.pm-bloom--br { width: 560px; height: 560px; right: -130px; bottom: -220px; background: rgba(0, 184, 135, .12); }
/* An animated ruled grid, replacing the two offset dot fields that stood here.
   The dot fields existed because the slot beside them held a CSS console that
   was itself full of ruled rows — doubling the texture. That console is a
   photograph now, so the ruled grid is back, and it moves.

   THREE nested elements, each doing exactly one job, because collapsing them
   breaks the effect:
   · .pm-mesh       carries the vignette. It must NOT be the element that
                    animates — a mask on a transformed box travels with it, so
                    the soft edge would drift out and snap back every loop.
   · .pm-mesh__pan  carries the grid and the drift. It is inset past the edges
                    so a one-cell translate never exposes a hard border, and it
                    travels exactly one cell, which is what makes the loop
                    seamless on a periodic pattern.
   · .pm-mesh__sweep is the SAME grid at full strength, revealed only through a
                    narrow band of light. Because it is a CHILD of the panning
                    element it inherits the drift for free — as a sibling its
                    bright lines would slide out of register with the dim ones
                    within a few seconds. */
.pm-mesh {
  position: absolute; inset: 0; overflow: hidden;
  /* the cap stays: on the wash the grid is far softer than it was on navy,
     but the headline still sits inside the mask's brightest zone and a full
     -strength grid behind 50px type is the one thing that made this field
     read as noise the last two times it was tuned */
  -webkit-mask-image: radial-gradient(92% 88% at 50% 34%, rgba(0,0,0,.5) 0%, rgba(0,0,0,.34) 46%, transparent 86%);
  mask-image: radial-gradient(92% 88% at 50% 34%, rgba(0,0,0,.5) 0%, rgba(0,0,0,.34) 46%, transparent 86%);
}
.pm-mesh__pan {
  position: absolute; inset: -80px; display: block;
  background-image:
    linear-gradient(to right, rgba(31, 162, 224, .17) 1px, transparent 1px),
    linear-gradient(to bottom, rgba(31, 162, 224, .12) 1px, transparent 1px);
  background-size: 88px 88px;
  animation: pmMeshDrift 34s linear infinite;
}
.pm-mesh__sweep {
  position: absolute; inset: 0; display: block;
  background-image:
    linear-gradient(to right, rgba(31, 162, 224, .30) 1px, transparent 1px),
    linear-gradient(to bottom, rgba(0, 184, 135, .22) 1px, transparent 1px);
  background-size: 88px 88px;
  -webkit-mask-image: linear-gradient(102deg, transparent 26%, #000 44%, #000 56%, transparent 74%);
  mask-image: linear-gradient(102deg, transparent 26%, #000 44%, #000 56%, transparent 74%);
  -webkit-mask-size: 300% 100%; mask-size: 300% 100%;
  -webkit-mask-repeat: no-repeat; mask-repeat: no-repeat;
  animation: pmMeshSweep 14s linear infinite;
}
/* one cell, so the pattern lands back on itself and the reset is invisible */
@keyframes pmMeshDrift { to { transform: translate(88px, 88px); } }
@keyframes pmMeshSweep {
  from { -webkit-mask-position: 135% 0; mask-position: 135% 0; }
  to   { -webkit-mask-position: -35% 0; mask-position: -35% 0; }
}

.pm-hero__grid {
  display: grid; grid-template-columns: minmax(0, 1.06fr) minmax(0, 1fr);
  gap: 60px; align-items: center;
}
.pm-hero__copy { max-width: 760px; }
/* Two deliberate lines, gradient on the short second one only. The
   earlier setting ran to 62px and stacked four lines with a gradient
   block through the middle of them — loud rather than confident.
   The <span> is forced onto its own line so the wrap can't move. */
/* The bevel-and-emboss this lockup carried is gone with the navy behind it:
   flat #fff on flat near-black is the one thing in a hero with no depth of
   its own, so both lines ran a vertical fill plus three drop-shadows to lift
   them. Ink on a white wash needs none of it — see the note inside the rule.
   The second line keeps its clipped gradient, which is why any shadow added
   here in future must be a drop-shadow and not a text-shadow: these lines are
   painted with background-clip:text, and a text-shadow prints straight
   THROUGH the transparent fill as a solid grey copy of the headline. */
.pm-hero__title {
  /* The budget is CHARACTERS PER LINE, not taste. Sora 800 runs ~0.584px of
     width per character per px of font-size, so a 25-character line needs
     ~14.6px of column width for every px of size. Both authored lines are
     exactly 25 characters, and the copy column measures 671px at 1440 and
     595px at 1280 — which caps the size at ~45px there, and 3.1vw lands under
     that at every width from 1024 up.

     The 50px ceiling only bites above ~1450px, where the column has grown to
     ~790px and 25 chars at 50px needs 730px. It was 45px while the heading
     was three lines of up to 25 characters; two lines can afford the extra
     five. Re-measure this if the copy changes length. */
  font-size: clamp(30px, 3.1vw, 50px); line-height: 1.12; font-weight: 800;
  margin: 22px 0 22px; letter-spacing: normal;
  /* The three drop-shadows that used to sit here — a hard dark edge, a wide
     black shadow and an indigo bloom — were an emboss for WHITE type on
     near-black, where flat #fff has no depth of its own. Near-black type on a
     white wash has all the contrast it needs; the same emboss on light prints
     as a grey halo round every letter. */
}
/* Two deliberate lines, not a wrap. The heading was 67 characters over three
   lines and is 50 over two; either way it would break at whatever point the
   viewport chose, moving as the viewport moved, so the break is owned here and
   the lockup holds its shape. Both lines are 25 characters, which is what lets
   them stay balanced instead of one running long. Unlike the sibling page, the
   short-laptop query does NOT re-join them — see the note in the max-height
   block for why. */
.pm-hero__line, .pm-hero__title .pm-grad-text { display: inline; }
/* Flat ink, not a clipped gradient. The three-stop white ramp this carried was
   the bevel half of the emboss described above; with the shadows gone it was
   painting #FFFFFF onto #FFFFFF three times. */
.pm-hero__line { color: var(--pm-head); }
/* The reference site sets its one highlighted headline line in flat green
   against black type. This keeps the ramp — sky → aqua → green, ending on
   that same green — because the page's whole accent story is those two hues
   travelling into each other, and the line is where that reads clearest. The
   light mid-tint the ramp used on navy is gone: #58C4EE against white is a
   pale patch in the middle of a headline. */
.pm-hero__title .pm-grad-text {
  /* background-IMAGE, never the `background` shorthand: the shorthand resets
     background-clip to border-box and .pm-grad-text's text clip goes with it,
     which paints this line as a solid gradient bar with no words in it. */
  background-image: linear-gradient(100deg, var(--h-deep) 0%, var(--h-sky) 42%, var(--h-green) 100%);
  background-size: 220% 100%; background-repeat: no-repeat;
  -webkit-background-clip: text; background-clip: text;
  /* animation: pmSheen 9s ease-in-out infinite alternate; */
}
@keyframes pmSheen { to { background-position: 100% 0; } }

.pm-hero__sub {
  /* 660 not 620: dropping .pm-hl's -4px margin (see below) handed ~16px of
     real width back to the markers and tipped this paragraph onto a third
     line. The copy column measures 663px at 1440, so this is the widest the
     sub can go, and it buys the two lines back with slack to spare. */
  font-size: 17.5px; line-height: 1.78; max-width: 100%;
  color: var(--pm-body); margin: 0 0 22px;
  /* balance, overriding the global `p { text-wrap: pretty }`. A .pm-hl is a
     nowrap atomic ~112px wide, so when the column narrows it does not shed a
     word onto the last line — the whole pill drops, and "pay to keep." sat
     alone on line 3 at 1280 looking like a broken element rather than a
     sentence. balance spreads the text evenly across however many lines it
     needs, so the last line always carries real words with the marker. */
  text-wrap: balance;
}
/* Marker-pen highlight — the claim that sells the product should not be the
   same weight as the sentence carrying it.

   Painted as a BACKGROUND on the inline with box-decoration-break: clone, not
   as an absolutely-positioned pseudo. An abs-positioned box measures the union
   of a wrapped inline's line boxes, so the moment "long-term memory" broke
   across two lines on a phone the marker became one tall rectangle that swept
   through the gap and stained the words beside it. Cloned decoration gives
   every line fragment its own bar. background-size/-position keep the ramp in
   the bottom half so it reads as a highlighter rather than a filled box. */
.pm-hl {
  color: var(--pm-head); font-weight: 700;
  /* A highlight has to be a FILLED shape behind the words — full height, with
     the text riding on top of it. On the old navy hero that meant a near-opaque
     bar, because anything lighter read as a slightly darker patch; on the white
     wash the same alpha would black out the words, so the ramp runs at ~22%
     and the text stays ink. */
  background-image: linear-gradient(100deg, rgba(31, 162, 224, .22) 0%, rgba(45, 205, 175, .24) 52%, rgba(0, 184, 135, .22) 100%);
  background-size: 100% 100%; background-position: 0 0; background-repeat: no-repeat;
  -webkit-box-decoration-break: clone; box-decoration-break: clone;
  /* vertical padding on an inline box does not grow the line box, so this
     thickens the marker for free. Horizontal padding DOES take width — at 9px
     the two markers added ~36px and pushed "keep" onto a third line by itself.

     margin is 0, NOT the -4px it was: the word space either side of the span
     is only ~5px at this size, so a -4px pull left ~1px of it and the pill
     collided with the words on both sides. At margin 0 the natural space
     renders outside the pill and the phrase sits in its own room.

     The trailing comma and full stop moved INSIDE the spans in the HTML for
     the same reason — outside, they were stranded 6px off the pill's right
     edge looking like floating punctuation.

     nowrap stops a marker splitting mid-phrase; both phrases measure well
     under the paragraph width even on a 390px screen, and
     box-decoration-break stays as the safety net for a longer one later. */
  padding: 3px 6px; margin: 0; border-radius: 7px;
  white-space: nowrap;
  box-shadow: none;
}
.pm-hero__cta { display: flex; flex-wrap: wrap; gap: 14px; margin-bottom: 30px; }

/* The three terms. They ran as a full-width glass bar under BOTH hero columns,
   which made them furniture — a rail the hero stood on rather than part of what
   the hero was saying. In the copy column, between the paragraph and the button,
   they are the last thing read before the CTA, which is the job they were always
   doing. The bar's per-item hues survive the move; its glass surface, dividers
   and equal-thirds grid do not, because a 600px column does not need them. */
.pm-hero__points {
  margin: 0 0 28px; padding: 0; list-style: none;
  display: flex; flex-direction: column; gap: 13px;
}
/* The three hues survive the re-theme but not their VALUES: a #58C4EE glyph
   in a 15%-alpha disc was legible on navy and is not on a white wash. Each
   runs its full-strength hue on a white disc instead, which is also what the
   reference site does with its icons. */
.pm-hero__points li:nth-child(1) { --t: #0B7EB8; --tb: rgba(31, 162, 224, .12); --tc: rgba(31, 162, 224, .30); }
.pm-hero__points li:nth-child(2) { --t: #0E9CAE; --tb: rgba(13, 177, 196, .12); --tc: rgba(13, 177, 196, .30); }
.pm-hero__points li:nth-child(3) { --t: #039C72; --tb: rgba(0, 184, 135, .12); --tc: rgba(0, 184, 135, .30); }
.pm-hero__points li {
  display: flex; align-items: center; gap: 13px;
  font-size: 15.4px; font-weight: 600; line-height: 1.35;
  color: var(--pm-head);
}
.pm-hero__pt {
  width: 30px; height: 30px; flex-shrink: 0; border-radius: 50%;
  display: grid; place-items: center; color: var(--t);
  background: var(--tb); border: 1px solid var(--tc);
  box-shadow: 0 2px 6px rgba(16, 43, 58, .05);
}
.pm-hero__pt svg { width: 15px; height: 15px; }

/* Capped to the artwork, not left as the full grid cell. The chips are absolutely
   positioned against THIS box, and the cell is ~640px wide at 1440 while the
   artwork is 600 and centred inside it — so a chip at `left: 0` sat 20px clear of
   the picture's left edge, and at 1920 the gap grew with the column. They looked
   like two labels dropped on the page rather than two badges on the shot. */
.pm-hero__visual {
  position: relative; display: flex; justify-content: center; align-items: center;
  width: 100%; max-width: var(--shot-w); margin-inline: auto;
}

/* ── HERO PRODUCT SHOT ──────────────────
   This slot used to hold a console drawn in CSS, because the page had no
   product asset. It has one now (images/hero-rgt-img.webp).

   The render is a near-white 16:9 dashboard, and the hero is now a near-white
   wash — which is the harder of the two problems the navy version had. On
   navy the shot only needed a frame to stop it floating; on white it has no
   edge at all above 96% grey, so the FRAME cannot come from the shot itself.
   It comes from the pale mint block offset behind it (.pm-hero__visual::before),
   the way the reference site sets its photographs, plus a hairline and a low
   neutral shadow. The old treatment — a near-black fill, a white 14% border
   and a 55%-black shadow — would print as a dark slab under a white picture.

   js/pmw.js writes the parallax + tilt transform onto .pm-shot, so
   nothing in this block may set `transform` at rest — the inline
   style would win and the two would fight. */
.pm-shot {
  position: relative; z-index: 2; margin: 0;
  width: 100%; max-width: var(--shot-w);
  border-radius: 24px; overflow: hidden;
  background: #fff;
  /* border: 1px solid rgba(16, 43, 58, .09); */
  /* box-shadow:
    0 30px 64px rgba(16, 43, 58, .16),
    0 4px 12px rgba(16, 43, 58, .05); */
  will-change: transform;
}
/* height:auto is not optional here. The <img> carries its real 1254x1254
   attributes so the browser can reserve the box before the file lands, and
   without this the next asset swapped in at a different aspect would be
   stretched to fit the old attribute ratio. */
.pm-shot img { display: block; width: 100%; height: auto; }

/* THE MINT BLOCK. On navy this slot held a blurred indigo bloom, which was
   how a white picture got separated from a black field. Neither the bloom nor
   the spinning rings before it survive a white ground — a soft glow on a wash
   is invisible — so the shot is set on a hard offset rectangle instead,
   exactly the device the reference site uses to hold its photographs.

   It is a SIBLING layer, not a border: .pm-shot clips its own content
   (overflow:hidden) so nothing drawn inside it can escape the frame, and the
   shot carries a js-driven parallax transform while this block stays put —
   which is what makes the two read as separate planes rather than one card
   with a thick edge. Offset down-left, because the two chips ride top-left and
   bottom-right and a block on that diagonal would sit under them.
   z-index:0 keeps it under .pm-shot's z-index:2. */
.pm-hero__visual::before {
  content: ""; position: absolute; z-index: 0;
  /* 56.25% is the shot's own aspect (16:9), so the block is exactly the same
     box as the picture and the offset shows an even 26px band on both the
     sides it sticks out of */
  left: 50%; top: 50%; width: 100%; padding-bottom: 56.25%;
  transform: translate(calc(-50% - 26px), calc(-50% + 26px));
  border-radius: 24px; pointer-events: none;
display: none;
  background: linear-gradient(150deg, var(--pm-mint-2) 0%, #CDEBF9 100%);

}

/* floating chips on the hero art */
/* Glass chips became solid white pills: a translucent dark pill needs
   something behind it to be translucent AGAINST, and it now floats over the
   hero wash where it read as a grey smudge. White on white needs the hairline
   and the shadow to exist at all — both are doing real work here. */
.pm-chip {
  position: absolute; z-index: 3;
  display: inline-flex; align-items: center; gap: 8px;
  background: #fff; border: 1px solid rgba(16, 43, 58, 0.08);
  color: var(--pm-head); font-size: 13px; font-weight: 600; letter-spacing: normal;
  padding: 9px 15px; border-radius: 999px;
  box-shadow: 0 12px 28px rgba(16, 43, 58, .12), 0 2px 6px rgba(16, 43, 58, .05);
  animation: pmFloat 6s ease-in-out infinite;
}
.pm-chip i { width: 8px; height: 8px; border-radius: 50%; background: var(--pm-green); }
/* The offsets are OUTDENTS, horizontal only. The -46px vertical ones they
   replace were tuned for an opaque framed console: the chips had to clear the
   panel entirely or they would cover its chart bars, so they floated in the
   slack above and below it. The artwork is a cut-out render on white now, with
   nothing to cover in its corners, and floating 46px clear of it just detached
   them — the top one landed under the fixed header.

   So each chip straddles a corner instead: inset vertically so it sits ON the
   picture, pulled out horizontally so it breaks the edge and reads as floating
   in front. Top-left is clear white above the pie card; bottom-right is clear
   below the bars. Re-check both if the artwork is swapped again. */
.pm-chip--1 { top: 14px; left: -24px; }
.pm-chip--2 { bottom: 18px; right: -24px; animation-delay: 1.4s; }
.pm-chip--2 i { background: var(--h-sky); }
@keyframes pmFloat { 0%, 100% { transform: translateY(0); } 50% { transform: translateY(-13px); } }

/* hero entrance choreography — scoped to html.js so a blocked
   stylesheet/script never leaves the hero invisible */
.js .pm-hero .pm-hero__copy > *,
.js .pm-hero .pm-hero__visual { opacity: 0; transform: translateY(22px); }
.js .pm-hero.is-ready .pm-hero__copy > *,
.js .pm-hero.is-ready .pm-hero__visual {
  opacity: 1; transform: none;
  transition: opacity .8s cubic-bezier(.22,1,.36,1), transform .8s cubic-bezier(.22,1,.36,1);
}
.js .pm-hero.is-ready .pm-hero__copy > *:nth-child(1) { transition-delay: .05s; }
.js .pm-hero.is-ready .pm-hero__copy > *:nth-child(2) { transition-delay: .14s; }
.js .pm-hero.is-ready .pm-hero__copy > *:nth-child(3) { transition-delay: .23s; }
.js .pm-hero.is-ready .pm-hero__copy > *:nth-child(4) { transition-delay: .32s; }
.js .pm-hero.is-ready .pm-hero__copy > *:nth-child(5) { transition-delay: .41s; }
.js .pm-hero.is-ready .pm-hero__copy > *:nth-child(6) { transition-delay: .5s; }
.js .pm-hero.is-ready .pm-hero__visual { transition-delay: .2s; }
@media (prefers-reduced-motion: reduce) {
  .js .pm-hero .pm-hero__copy > *, .js .pm-hero .pm-hero__visual { opacity: 1; transform: none; }
  .pm-chip, .pm-dot { animation: none; }
  /* the mesh is the loudest motion in the hero — it goes first */
  .pm-mesh__pan { animation: none; }
  /* not `animation:none` — a parked sweep freezes as a bright stripe down
     whichever side its default mask-position lands on */
  .pm-mesh__sweep { display: none; }
  .pm-hero__title .pm-grad-text { animation: none; background-position: 0 0; }
}

/* ═══════════════ USP STRIP (3 cards riding up onto the hero) ═══════════════
   The cards hang off the hero's bottom edge, which is why this section has NO
   heading: the grid's top ~50px sits on the dark, and an eyebrow + h2 above it
   would have to sit there too. The cards kept the full copy they gained when
   this was briefly a full section — only the heading went.

   Two numbers hold each other up: the overlap here and .pm-hero's
   padding-bottom. The pull-up eats into that padding, so whatever is left is
   the clearance between the terms bar and the top of a card. At the current
   100px hero padding, -50px leaves 50px. Change either and check the gap.

   The section runs WHITE, not --pm-paper-2 as it used to: the video section
   right below is paper-2, and two tinted blocks back to back read as one
   slab — the same trap the partners wall has to avoid. */
.pm-usp { background: var(--pm-paper); padding: 0; }
.pm-usp__grid {
  display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 22px;
  /* a GAP, not the -50px pull-up this was. That overlap was aimed at the
     hero; with the logo strip sitting between the hero and these cards it
     landed on the logos instead. */
  margin-top: 56px; position: relative; z-index: 5;
  padding-bottom: var(--pm-pad);
}
/* column, not row: the pills were icon-beside-text because they were one line
   each. With a paragraph under the heading, a leading icon would leave the
   copy hanging off a 46px indent for four lines. */
.pm-usp__card {
  display: flex; flex-direction: column;
  background: #fff; border: 1px solid var(--pm-line); border-radius: var(--pm-r-lg);
  padding: 32px 30px 30px;
  /* was rgba(3,6,20,.28) — that depth existed because the top half of every
     card sat on the near-black hero and needed to lift off it. The hero
     bottom is white now, so the same shadow prints as a grey bruise. */
  box-shadow: 0 20px 46px rgba(16, 43, 58, 0.10), 0 2px 6px rgba(16, 43, 58, 0.04);
  transition: transform .3s cubic-bezier(.22,1,.36,1), box-shadow .3s ease, border-color .3s ease;
}
.pm-usp__card:hover { transform: translateY(-6px); border-color: rgba(31, 162, 224, .35); box-shadow: 0 26px 56px rgba(31, 66, 224, 0); }
.pm-usp__ic {
  width: 52px; height: 52px; flex-shrink: 0; border-radius: 15px;
  background: var(--pm-grad-b); color: #fff;
  display: grid; place-items: center; margin-bottom: 22px;
  box-shadow: 0 10px 24px rgba(31, 162, 224, .26);
  transition: transform .3s cubic-bezier(.22,1,.36,1);
}
.pm-usp__card:hover .pm-usp__ic { transform: scale(1.07) rotate(-4deg); }
.pm-usp__ic svg { width: 24px; height: 24px; }
/* Reserves a second title line so the paragraphs line up across the row —
   the same alignment problem .pm-model h3 solves, and for the same reason.

   BOUNDED at the top, unlike that one, because the titles were shortened to
   36/30/36 characters and now all three fit ONE line once the card passes
   ~450px (measured: 1 line each at a 1496px viewport, card 1 wrapping at 1424,
   cards 1 and 3 at 1350, all three by 1184). Left open-ended, the reservation
   would hang an empty second line under every title on a wide monitor.
   Measure this with document.fonts.ready — Sora arrives via a media="print"
   swap, and before it lands the fallback's metrics give different wrap points. */
.pm-usp__card h2 {
  margin: 0 0 12px; font-size: 19px; font-weight: 700;
  line-height: 1.34; letter-spacing:normal; color: var(--pm-head);
}
@media (min-width: 1025px) and (max-width: 1460px) { .pm-usp__card h2 { min-height: 51px; } }
.pm-usp__card p { margin: 0; font-size: 15.5px; line-height: 1.68; color: var(--pm-body); }

@media (max-width: 1024px) {
  .pm-usp__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .pm-usp__grid > :last-child:nth-child(odd) { grid-column: 1 / -1; }
}
@media (max-width: 768px) {
  .pm-usp__grid { grid-template-columns: 1fr; margin-top: 40px; }
  .pm-usp__grid > :last-child:nth-child(odd) { grid-column: auto; }
  .pm-usp__card { padding: 26px 24px 24px; }
}

/* ═══════════════ NUMBERS BAND ═══════════════
   Five figures, so the two-column grid this block used to run would
   orphan the fifth. Five across on desktop, three then two on a
   tablet, and at the 2-col breakpoint an odd last card takes the whole
   row rather than sitting beside a hole. */
/* WHITE, and the cards carry the tint instead — the inversion this sheet
   applies everywhere. It ran tinted with white cards until the intro section
   between it and the video block was removed, which left two tinted sections
   touching. Deleting a section here always costs a flip somewhere: check the
   whole run of surfaces, not just the seam that broke. */
.pm-nums { background: var(--pm-paper); }
.pm-nums__grid { display: grid; grid-template-columns: repeat(5, minmax(0, 1fr)); gap: 16px; }
@media (max-width: 1200px) { .pm-nums__grid { grid-template-columns: repeat(3, minmax(0, 1fr)); } }
@media (max-width: 760px)  { .pm-nums__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
                             .pm-nums__grid > :last-child:nth-child(odd) { grid-column: 1 / -1; } }
@media (max-width: 420px)  { .pm-nums__grid { grid-template-columns: 1fr; } }
.pm-stat {
  background: var(--pm-paper-2); border: 1px solid var(--pm-bline-2); border-radius: var(--pm-r);
  padding: 30px 26px; transition: transform .3s cubic-bezier(.22,1,.36,1), border-color .3s ease, box-shadow .3s ease;
}
.pm-stat:hover { transform: translateY(-6px); border-color: rgba(13, 177, 196, .35); box-shadow: 0 24px 50px rgba(13, 177, 196, 0.14); }
.pm-stat__n {
  font-family: var(--pm-display); font-size: clamp(30px, 3.2vw, 44px); font-weight: 800;
  line-height: 1; letter-spacing: normal; margin: 0 0 8px;
  /* --pm-deep, not --pm-grad: these are 44px figures sitting on the --pm-paper-2
     tint, and the brand blue on that tint measures 2.51:1 — under the 3.0 large
     text needs. The deep blue lands at 4.37:1 and still reads as the accent.
     NOT --pm-btn: a figure is not something you press. */
  background: var(--pm-deep); -webkit-background-clip: text; background-clip: text; -webkit-text-fill-color: transparent;
}
.pm-stat__l { font-size: 14.5px; font-weight: 600; color: var(--pm-body); margin: 0; line-height: 1.5; }

/* ═══════════════ USE-CASE CARDS ═══════════════ */
.pm-cases__grid { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 24px; }
.pm-case-card {
  background: #fff; border: 1px solid var(--pm-line); border-radius: var(--pm-r-lg);
  padding: 34px 30px 32px; position: relative; overflow: hidden;
  transition: transform .32s cubic-bezier(.22,1,.36,1), border-color .32s ease, box-shadow .32s ease;
}
.pm-case-card::before {
  content: ""; position: absolute; left: 0; right: 0; top: 0; height: 3px;
  background: var(--pm-grad); transform: scaleX(0); transform-origin: 0 50%;
  transition: transform .45s cubic-bezier(.22,1,.36,1);
}
.pm-case-card:hover { transform: translateY(-8px); border-color: rgba(31, 162, 224, .3); box-shadow: 0 30px 60px rgba(31, 162, 224, .13); }
.pm-case-card:hover::before { transform: scaleX(1); }
.pm-case-card__ic {
  width: 52px; height: 52px; border-radius: 15px; display: grid; place-items: center;
  background: var(--pm-grad-soft); color: var(--pm-sky); margin-bottom: 22px;
  transition: background .32s ease, color .32s ease, transform .42s cubic-bezier(.22,1,.36,1);
}
.pm-case-card__ic svg { width: 24px; height: 24px; }
.pm-case-card:hover .pm-case-card__ic { background: var(--pm-grad); color: #fff; transform: rotate(-6deg) scale(1.06); }
.pm-case-card h3 { font-size: 19px; font-weight: 700; margin: 0 0 12px; line-height: 1.35; }
.pm-case-card p { font-size: 15px; margin: 0; line-height: 1.7; }

/* ═══════════════ GRADIENT CTA BAND ═══════════════ */
.pm-band { margin-top: 70px; }
/* Same reasoning as the buttons, and it matters more here: this block carries a
   13px kicker and a 16px paragraph in white, which need 4.5:1. On the brand
   tint they measured 2.9. It stays BLUE while the buttons are green — it is a
   surface, not a control, and the white button sitting on it needs a ground to
   sit on rather than a second green. */
.pm-band__inner {
  background: var(--pm-deep); background-size: 200% 100%; background-repeat: no-repeat;
  border-radius: var(--pm-r-lg); padding: 52px 56px; position: relative; overflow: hidden;
  display: flex; align-items: center; justify-content: space-between; gap: 34px; flex-wrap: wrap;
  animation: pmBandShift 14s ease-in-out infinite alternate;
}
@keyframes pmBandShift { to { background-position: 100% 0; } }
.pm-band__inner::after {
  content: ""; position: absolute; inset: 0; opacity: .5; pointer-events: none;
  background-image: linear-gradient(rgba(255,255,255,.1) 1px, transparent 1px), linear-gradient(90deg, rgba(255,255,255,.1) 1px, transparent 1px);
  background-size: 46px 46px;
  mask-image: radial-gradient(70% 100% at 90% 50%, #000, transparent 75%);
  -webkit-mask-image: radial-gradient(70% 100% at 90% 50%, #000, transparent 75%);
}
.pm-band__copy { position: relative; z-index: 1; max-width: 780px; }
.pm-band__kicker { font-size: 13px; font-weight: 700; letter-spacing: .12em; text-transform: uppercase; color: rgba(255,255,255,.78); margin: 0 0 10px; }
.pm-band__inner h3 { color: #fff; font-size: clamp(22px, 2.3vw, 32px); line-height: 1.28; margin: 0; font-weight: 700; }
.pm-band__inner p.pm-band__sub { color: rgba(255,255,255,.84); margin: 12px 0 0; font-size: 16px; max-width: 640px; }
.pm-band__inner .pm-btn { position: relative; z-index: 1; }

/* ═══════════════ SERVICES (on the sky band) ═══════════════
   The six feature cards. They ran near-black-on-near-black with a milled
   texture over them; on --pm-band they run WHITE, which is both the reference
   site's card treatment and the only value that separates cleanly from a
   tinted section without a heavy border. */
.pm-svc__grid { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 22px; }
/* The texture layer is gone with the dark card. It was a real asset
   (images/converstion_process_1.webp, a dark ruled panel with a soft wave)
   composited with mix-blend-mode:lighten — a blend mode that only does
   anything over a dark ground, and over white lightens to nothing but noise.
   The file is still in images/, referenced by nothing. */
.pm-svc__card {
  background: #fff; border: 1px solid var(--pm-bline);
  border-radius: var(--pm-r-lg); padding: 34px 30px 32px; position: relative; overflow: hidden;
  box-shadow: 0 2px 8px rgba(16, 43, 58, .04);
  transition: transform .32s cubic-bezier(.22,1,.36,1), border-color .32s ease, box-shadow .32s ease;
}
.pm-svc__card > * { position: relative; z-index: 1; }
.pm-svc__card:hover { transform: translateY(-8px); border-color: rgba(31, 162, 224, .40); box-shadow: 0 30px 56px rgba(16, 43, 58, .14); }
.pm-svc__ic {
  width: 52px; height: 52px; border-radius: 15px; display: grid; place-items: center;
  background: rgba(31, 162, 224, .11); color: var(--pm-sky-d); margin-bottom: 22px;
  transition: background .32s ease, color .32s ease, transform .42s cubic-bezier(.22,1,.36,1);
}
.pm-svc__ic svg { width: 24px; height: 24px; }
.pm-svc__card:hover .pm-svc__ic { background: var(--pm-grad); color: #fff; transform: translateY(-3px) rotate(-6deg); }
.pm-svc__card h3 { font-size: 18.5px; font-weight: 700; margin: 0 0 12px; line-height: 1.35; color: var(--pm-head); }
.pm-svc__card p { font-size: 14.8px; margin: 0; line-height: 1.72; color: var(--pm-body); }

/* The laptop band. The grid holds three columns all the way down to 1025px,
   so between there and 1536px each card loses ~15% of its width with nothing
   giving way — and every card body, written to set on four lines, spills to a
   fifth. Five lines is not a wrapping accident here, it is a second card
   height: the row grows 50px and the six bodies stop reading as one block.
   The line comes back from the BOX first — a tighter gap and inner padding are
   free width and cost the type nothing — and only then from a fluid step down
   in body size, which idles at the full 14.8px until the box runs out. Both
   ceilings land on the desktop values, so 1536px and up is byte-identical to
   what it renders today. Four lines holds from 1240px up; below that the copy
   is simply longer than three columns of that width can carry. */
@media (min-width: 1025px) and (max-width: 1535.98px) {
  .pm-svc__grid { gap: 18px; }
  .pm-svc__card { padding: 30px clamp(20px, 1.55vw, 28px) 28px; }
  .pm-svc__card p { font-size: clamp(13.1px, 1.02vw, 14.8px); line-height: 1.7; }
  /* Same story one line up, and it reads worse there. The six titles are
     written to a single line and the widest of them ("Use Profiling to Match
     the Right Surveys") measures 382px at 18.5px Sora. The text column is
     409px at 1536 — the last width that holds — then 374px at 1366 and 351px
     at 1280, so every real laptop breaks all six titles in two and the icon,
     title and body stop sitting at the same heights across a row.
     The box has nothing left to give here (the padding above is already
     buying the body its fourth line), so this comes out of the type: a fluid
     step tied to the same viewport the column width is. 1.26vw tracks just
     under the width the column actually offers, with ~5% of slack at 1366 so
     Windows font rendering cannot tip it over. The ceiling is the desktop
     18.5px and it is reached by ~1468px; the floor is 15.2px, which is where
     1200px lands — below that the titles are simply longer than a third of
     that screen and they wrap, but 15.2px still reads clearly above the
     13.1px body. 1536px and up never sees this rule. */
  .pm-svc__card h3 { font-size: clamp(15.2px, 1.26vw, 18.5px); }
}

/* The CTA card that closes the features grid. It is deliberately NOT the
   gradient: the migration band further down the page is the page's one
   gradient bar, and a second one three sections earlier makes both read as
   furniture. White with an accent rule and a gradient button is the louder
   move here anyway, because it is the only white block on the band that is
   not a feature card. */
.pm-svc__cta {
  margin-top: 24px; border-radius: var(--pm-r-lg); padding: 46px 52px;
  background: #fff;
  border: 1px solid var(--pm-bline);
  box-shadow: 0 14px 40px rgba(16, 43, 58, .09);
  display: flex; align-items: center; justify-content: space-between; gap: 30px; flex-wrap: wrap;
  position: relative; overflow: hidden;
}
/* the accent rule down the leading edge, in place of the indigo bloom the
   dark card carried in its corner */
.pm-svc__cta::before {
  content: ""; position: absolute; left: 0; top: 0; bottom: 0; width: 5px;
  background: var(--pm-grad);
  display: none;
}
.pm-svc__cta::after {
  content: ""; position: absolute; width: 420px; height: 420px; right: -140px; top: -200px;
  border-radius: 50%; background: radial-gradient(circle, rgba(31, 162, 224, .13), transparent 68%); filter: blur(30px);
}
.pm-svc__cta > * { position: relative; z-index: 1; }
.pm-svc__cta h3 { font-size: clamp(21px, 2.2vw, 30px); margin: 0 0 10px; line-height: 1.28; color: var(--pm-head); }
.pm-svc__cta p { margin: 0; color: var(--pm-body); font-size: 16px; }

/* ═══════════════ AWARDS (light) ═══════════════
   Six across, centred, with a 52px amber disc floating over each, read as a
   row of identical coins: the discs carried all the weight, every title broke
   to two or three ragged lines in a 190px column, and the awarding body — the
   part that makes an award mean anything — was the faintest text on the card.
   Three across in two rows gives each one the width to say what it is on one
   line, and turning the body into an eyebrow above the title puts the proof
   first.

   Colour is the page's own accent, not amber. It runs on --pm-grad-b
   (sky→aqua) — the BLUE half of the ramp, stopping short of the green — so
   --pm-green stays reserved for the verification moments the way the sheet's
   header rule requires. */
.pm-awards__grid { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 18px; }
.pm-award {
  position: relative; overflow: hidden;
  display: flex; align-items: center; gap: 18px;
  background: var(--pm-paper); border: 1px solid var(--pm-line);
  border-radius: var(--pm-r); padding: 22px 24px;
  box-shadow: 0 2px 10px rgba(16, 43, 58, .04);
  transition: transform .32s cubic-bezier(.22,1,.36,1), border-color .32s ease, background .32s ease, box-shadow .32s ease;
}
/* the rail wipes down from the top on hover — a ribbon cue, and the only
   full-strength accent a resting card carries */
.pm-award::before {
  content: ""; position: absolute; left: 0; top: 0; bottom: 0; width: 3px;
  background: linear-gradient(180deg, #1FA2E0, #0DB1C4);
  transform: scaleY(0); transform-origin: top center;
  transition: transform .45s cubic-bezier(.22,1,.36,1);
}
.pm-award:hover::before { transform: none; }
.pm-award:hover {
  transform: translateY(-5px); border-color: rgba(13, 177, 196, .34);
  box-shadow: 0 20px 40px rgba(16, 43, 58, .12);
}
.pm-award__medal {
  width: 50px; height: 50px; flex-shrink: 0; border-radius: 15px;
  background: linear-gradient(150deg, rgba(31, 162, 224, .12), rgba(13, 177, 196, .12));
  border: 1px solid rgba(13, 177, 196, .20); color: var(--pm-aqua);
  display: grid; place-items: center;
  transition: transform .42s cubic-bezier(.22,1,.36,1), background .32s ease, color .32s ease, box-shadow .32s ease;
}
.pm-award:hover .pm-award__medal {
  background: var(--pm-grad-b); color: #fff;
  border-color: transparent; box-shadow: 0 10px 24px rgba(13, 177, 196, .38);
  transform: rotate(-6deg) scale(1.06);
}
.pm-award__medal svg { width: 23px; height: 23px; }

.pm-award__txt { min-width: 0; }
.pm-award__by {
  display: block; font-family: var(--pm-display); font-size: 11px; font-weight: 700;
  letter-spacing: .14em; text-transform: uppercase; color: var(--pm-sky-d); margin-bottom: 7px;
}
.pm-award b {
  display: block; font-family: var(--pm-display); font-size: 16px; font-weight: 700;
  color: var(--pm-head); line-height: 1.34; letter-spacing: normal;
}

/* ═══════════════ CLIENT LOGO STRIP ═══════════════
   One full-width rail under the hero block, replacing the two-rail marquee
   that had its own section (heading, tinted wall, strapline) further down.

   WHITE, with a hairline top and bottom. The .pm-usp cards above it are white
   and the video section below is paper-2, so a tinted strip would merge with
   one of them; the hairlines are what make it read as its own band.

   The rail is no longer a CSS animation. It is driven from js/pmw.js so it can
   be dragged, swiped and wheeled by hand and pick the autoplay back up when the
   pointer leaves — none of which a keyframe can do. Everything below is
   presentation only; the transform belongs to the script. */
.pm-strip {
  position: relative;
  background: var(--pm-paper);
  border-top: 1px solid var(--pm-line);
  border-bottom: 1px solid var(--pm-line);
  padding: 26px 0 30px;
}
.pm-strip__cap {
  margin: 0 0 20px; text-align: center;
  font-family: var(--pm-display); font-size: 11.5px; font-weight: 700;
  letter-spacing: .16em; text-transform: uppercase; color: #52646E;
}
/* touch-action: pan-y is the whole reason a swipe works without breaking the
   page — the browser keeps vertical scrolling for itself and hands us the
   horizontal gestures, so a thumb dragging down the page still scrolls it and
   a thumb dragging sideways moves the rail. */
.pm-strip__rail {
  position: relative; overflow: hidden;
  cursor: grab; touch-action: pan-y;
  -webkit-user-select: none; user-select: none;
  /* the fade starts close to the edge: at 13% a full-bleed rail on a 1920
     monitor ghosts out 250px each side, which is a whole card lost to the mask */
  -webkit-mask-image: linear-gradient(90deg, transparent, #000 5%, #000 95%, transparent);
  mask-image: linear-gradient(90deg, transparent, #000 5%, #000 95%, transparent);
}
.pm-strip__rail:focus-visible { outline: 2px solid var(--pm-sky-d); outline-offset: 3px; }
.pm-strip__rail.is-dragging { cursor: grabbing; }
/* no animation here on purpose — see the note above */
/* gap in px, not em, so it does NOT scale with .pm-logo's font-size — it has
   to be brought down by hand whenever the cards shrink or the row starts
   reading as gaps with logos in between. */
.pm-strip__track { display: flex; gap: 13px; width: -webkit-max-content; width: max-content; will-change: transform; }
/* a drag must not fire the link/hover behaviour of the card under the cursor */
.pm-strip__rail.is-dragging .pm-logo { pointer-events: none; }

/* One card per logo, width driven by the mark it holds rather than a fixed
   slot: a fixed slot pads "Crunched" (6.5:1) and "Al Zain" (1:1) into the
   same rectangle, and the square one ends up a stamp floating in white. The
   min-width keeps the narrow marks from collapsing to a badge.

   Everything is em against a font-size the card owns, so one declaration in
   a media query scales the whole wall — cards, padding and every per-logo
   height together — instead of fifteen overrides per breakpoint. */
.pm-logo {
  /* 9px, down from 12 (2026-08-12). This one value is the whole wall's scale:
     the card height, its min-width, its padding and all fifteen per-logo
     heights are em against it, so nothing below needs touching. 110px cards
     were competing with the hero above them; 83px reads as a trust strip. */
  font-size: 9px;
  flex-shrink: 0; display: grid; place-items: center;
  height: 9.2em; min-width: 14.6em; padding: 0 2.4em;
  background: #fff; border: 1px solid var(--pm-line); border-radius: 16px;
  box-shadow: 0 2px 8px rgba(16, 43, 58, .05);
  transition: border-color .3s ease, box-shadow .3s ease, transform .3s ease;
}
/* height, not max-height: these files carry wildly different amounts of
   baked-in transparent margin (innovate-MR is 53% empty vertically, logo2 is
   55% empty horizontally), so capping a shared max-height renders half the
   wall at two-thirds the size of the other half. Each logo instead gets the
   element height that puts its INK at a matched optical size, measured from
   the alpha bounding box. width:auto keeps the aspect — see the height-attr
   stretch trap. */
.pm-logo img {
  display: block; width: auto; max-width: 100%; height: 3.4em;
  object-fit: contain;
  transition: transform .3s ease;
}
.pm-logo--purespectrum     img { height: 3.4em; }
.pm-logo--innovatemr       img { height: 7.2em; }
.pm-logo--krea             img { height: 5.6em; }
.pm-logo--crunched         img { height: 2.4em; }
.pm-logo--elicit           img { height: 4.7em; }
.pm-logo--datadiggers      img { height: 4.4em; }
.pm-logo--globalexchange   img { height: 4.8em; }
.pm-logo--alzain           img { height: 5.4em; }
.pm-logo--incentiveopinion img { height: 5.5em; }
.pm-logo--aim              img { height: 5.6em; }
.pm-logo--globalsurvey     img { height: 2.8em; }
.pm-logo--divergent        img { height: 4.8em; }
.pm-logo--martlenz         img { height: 3.7em; }
.pm-logo--progresso        img { height: 5.7em; }
.pm-logo--qmark            img { height: 6.4em; }

/* no grayscale at rest. The wall this replaced learned the lesson already:
   drained colour on white reads as "unavailable", not "client" — and hover
   is not a state a marquee card can be relied on to reach. */
.pm-logo:hover {
  border-color: rgba(31, 162, 224, .34);
  box-shadow: 0 16px 34px rgba(31, 162, 224, .14);
  transform: translateY(-4px);
}
.pm-logo:hover img { transform: scale(1.04); }

@media (max-width: 900px) { .pm-logo { font-size: 7.6px; } }
@media (max-width: 560px) { .pm-logo { font-size: 6.4px; } }

/* Under reduced motion the rail does not autoplay (js/pmw.js checks the same
   query) but it stays DRAGGABLE — the preference is about unrequested motion,
   not about taking the control away. So the mask stays too: it is still fading
   logos that slide under the edge, just under a hand rather than a timer. */
/* ═══════════════ FAQ ═══════════════
   The markup and the engine are the shared ones — .faq-listing / .faq-col /
   <details class="faq-item" name="faq">, styled in base-styles.css and driven
   by initFaqAccordion() in common-js/main.js, exactly as
   /taxi-app-development/ does it. Two independent .faq-col containers is the
   whole point: opening a question shifts only the questions under it in the
   SAME column, where one six-item grid leaves a hole beside the open card.

   Only the palette is overridden below. base-styles paints this in its own
   neutral ink with an amber [open] border, which belongs to another page.
   Structure, spacing and behaviour are deliberately left alone so this page
   stays in step if the shared file changes. */
#faq .faq-listing { max-width: 100%; margin-left: auto; margin-right: auto; }
/* Tinted rows on a WHITE section, which is the inversion the sheet applies
   everywhere else. The section ran paper-2 with white rows until the partners
   wall was removed from between it and the awards block — that left two tinted
   sections touching, and a 12-question accordion is the wrong one of the two to
   be the heavy slab. Flipping it puts the tint on the rows instead, where it
   also does more work: a white row on white needs its hairline to exist at all. */
#faq .faq-item { background: var(--pm-paper-2); border-color: var(--pm-line); border-radius: var(--pm-r); box-shadow: none; }
#faq .faq-item:hover { border-color: rgba(13, 177, 196, .3); box-shadow: 0 14px 34px rgba(31, 162, 224, .08); }
#faq .faq-item[open] { border-color: rgba(13, 177, 196, .42); box-shadow: 0 20px 44px rgba(31, 162, 224, .12); }
#faq .faq-item summary {
  font-family: var(--pm-display); font-size: 16.5px; font-weight: 700;
  color: var(--pm-head); letter-spacing: normal; line-height: 1.45;
  padding: 22px 26px;
  border-bottom: 1px solid transparent;
  transition: padding-bottom .4s cubic-bezier(.4, 0, .2, 1), border-color .3s ease;
}
/* The shared component ships a rotating chevron; this page keeps the +/- disc
   it had before, so `.faq-chevron` is swapped for `.faq-sign` in the markup —
   the accordion engine only needs <summary> and .faq-answer, it never looks at
   the icon. Two pseudo-elements make the cross; on [open] the vertical bar
   scales to nothing and the disc rotates, so + turns into - in one motion. */
#faq .faq-sign {
  width: 30px; height: 30px; flex: 0 0 30px; border-radius: 50%;
  background: var(--pm-line-2); color: var(--pm-head);
  display: grid; place-items: center; position: relative;
  transition: background .3s ease, color .3s ease, transform .35s ease;
}
#faq .faq-sign::before, #faq .faq-sign::after {
  content: ""; position: absolute; background: currentColor; border-radius: 2px;
  transition: transform .35s cubic-bezier(.22,1,.36,1), opacity .25s ease;
}
#faq .faq-sign::before { width: 13px; height: 2px; }
#faq .faq-sign::after  { width: 2px; height: 13px; }
#faq .faq-item[open] .faq-sign { background: var(--pm-deep); color: #fff; transform: rotate(180deg); }
#faq .faq-item[open] .faq-sign::after { transform: scaleY(0); opacity: 0; }
#faq .faq-answer { padding-left: 26px; padding-right: 26px; }
/* The gap between question and answer is the SUM of the summary's bottom
   padding and the answer's top padding, so raising only the answer stacked on
   top of the 22px already there: measured 26px above the question and 41px
   below it. That lopsidedness is what read as empty space — a heading belongs
   closer to the text it introduces, not further from it.

   Total is back to ~34px, split either side of a hairline, so the space now
   separates two things instead of just sitting there. Scoped to [open], and
   the summary transitions its padding so nothing jumps open.

   Safe with the height animation: initFaqAccordion() sets `item.open = true`
   BEFORE reading scrollHeight, so this padding and the border are already
   applied when the target height is measured. The divider lives on the SUMMARY,
   not on the answer — on the answer it would still paint a 1px line while the
   panel sits collapsed at height: 0. */
#faq .faq-item[open] summary { padding-bottom: 16px; border-bottom-color: #8dd7e3; }
#faq .faq-item[open] > .faq-answer { padding-top: 17px; padding-bottom: 26px; }
#faq .faq-answer p { color: var(--pm-body); font-size: 15.4px; line-height: 1.78; margin: 0; }

/* ── Centred CTA closing the accordion ──────────────────────────────
   It ran on --pm-paper-2, which is the tint the FAQ ROWS run — the
   closing call to action was the same colour as the twelve questions
   above it and disappeared into the list. It now takes the one move
   this page reserves for a CTA surface: a saturated blue slab, the
   same decision .pm-band__inner makes mid-page, with the same 46px
   white grid over it and the same white button. Blue is the surface,
   never the control.

   The gradient is deliberately DEEPER than either the band (--pm-deep
   #0A76AB) or the footer (#0C79B0) it sits above. Two reasons: white
   body copy needs 4.5:1 and #0A76AB gives pure white only 5.03:1 —
   no headroom left for the softened whites this block wants — while a
   third slab of the SAME blue, one 96px white gap above the footer,
   reads as a mistake. #05486B → #0A6E9E runs 9.8:1 down to 5.65:1, so
   every tone here is comfortable, and the card is plainly the darkest
   thing on the page: the last thing you see before the footer.

   Centred by FLEX, not by text-align: .pm-btn is an inline-flex pill,
   so text-align would only centre the label inside it and leave the
   pill wherever the line box put it. No `transition` is declared in
   this block — .reveal owns that property, and re-stating it would
   silently drop the fade-in. */
#faq .faq-cta {
  margin-top: 48px;
  position: relative; overflow: hidden;
  display: flex; flex-direction: column; align-items: center; text-align: center;
  padding: 58px 32px 56px;
  border: 1px solid rgba(255, 255, 255, .12);
  border-radius: var(--pm-r-lg);
  background:
    radial-gradient(72% 120% at 88% -10%, rgba(13, 177, 196, .40) 0%, rgba(13, 177, 196, 0) 62%),
    radial-gradient(58% 118% at 2% 116%, rgba(0, 184, 135, .17) 0%, rgba(0, 184, 135, 0) 62%),
    linear-gradient(118deg, #05486B 0%, #0A6E9E 100%);
  box-shadow: 0 26px 62px rgba(8, 62, 92, .24);
}
/* Same grid and the same 46px cell as the migration band, so the two CTA
   surfaces are visibly the same object. Masked from the TOP here rather
   than from the right: this block is centred, so a directional fade would
   pull the eye off the axis everything else is lined up on. */
#faq .faq-cta::before {
  content: ""; position: absolute; inset: 0; pointer-events: none; opacity: .55;
  background-image:
    linear-gradient(rgba(255, 255, 255, .10) 1px, transparent 1px),
    linear-gradient(90deg, rgba(255, 255, 255, .10) 1px, transparent 1px);
  background-size: 46px 46px;
  -webkit-mask-image: radial-gradient(84% 116% at 50% 0%, #000 0%, transparent 74%);
  mask-image: radial-gradient(84% 116% at 50% 0%, #000 0%, transparent 74%);
}
/* every child clears the texture layer */
#faq .faq-cta > * { position: relative; z-index: 1; }
#faq .faq-cta__eyebrow {
  display: inline-block;
  font-family: var(--pm-display); font-size: 12.5px; font-weight: 700;
  letter-spacing: .12em; text-transform: uppercase; color: #fff;
  background: rgba(255, 255, 255, .15);
  border: 1px solid rgba(255, 255, 255, .26);
  border-radius: 999px; padding: 7px 16px;
}
#faq .faq-cta h3 {
  margin: 18px 0 0; color: #fff;
  font-size: clamp(22px, 2.5vw, 31px); font-weight: 800; line-height: 1.26;
}
#faq .faq-cta > p:not(.faq-cta__note) {
  margin: 13px 0 0; max-width: 62ch;
  /* .94, not .84 like the band: at the light end of this gradient .84
     measures 4.4:1 and this is 15.8px body copy. .94 holds 5.2:1. */
  color: rgba(255, 255, 255, .94); font-size: 15.8px; line-height: 1.75;
}
/* The row owns the top margin now, not the button: with two pills the gap
   belongs to the group, and a per-button margin would double up the moment the
   row wraps. flex-wrap + centre keeps a wrapped second pill on the axis. */
#faq .faq-cta__actions {
  display: flex; flex-wrap: wrap; align-items: center; justify-content: center;
  gap: 14px; margin-top: 28px;
}
/* .92 is the floor for the note too — it is the SMALLEST text on the
   darkest surface, so it gets no extra softening. */
#faq .faq-cta__note {
  margin: 15px 0 0; font-size: 13.6px; color: rgba(255, 255, 255, .92);
}

/* Laptop/small-desktop: the two pills plus the 14px gap measure ~470px, so they
   hold one line well below this width. Only the gap tightens. */
@media (max-width: 980px) {
  #faq .faq-cta__actions { gap: 12px; }
}
@media (max-width: 768px) {
  #faq .faq-cta { margin-top: 34px; padding: 42px 24px 40px; border-radius: var(--pm-r); }
  #faq .faq-cta > p:not(.faq-cta__note) { font-size: 15.2px; }
  /* Tablet still fits both pills side by side; the labels shed a little
     horizontal padding rather than the row breaking early. */
  #faq .faq-cta__actions .pm-btn { padding-left: 24px; padding-right: 24px; font-size: 15px; }
}
/* Below ~520px a pill sized to its own label reads as a stray chip in the
   middle of an empty row, so it stretches — capped at 400px so it never
   becomes a full-bleed slab on a large phone or a folded tablet. */
@media (max-width: 520px) {
  #faq .faq-cta { padding: 34px 18px 32px; }
  #faq .faq-cta__eyebrow { font-size: 11.5px; padding: 6px 13px; }
  /* Stacked, both stretched to the SAME width — side by side at this width the
     shorter pill would look like an afterthought next to the longer one. The row
     becomes a column so max-width caps each pill, not the pair. */
  #faq .faq-cta__actions {
    flex-direction: column; width: 100%; max-width: 400px; gap: 11px; margin-top: 24px;
  }
  #faq .faq-cta__actions .pm-btn { width: 100%; justify-content: center; }
  #faq .faq-cta__note { font-size: 13px; }
}

/* ═══════════════ FOOTER ═══════════════
   The near-black bar is gone with the rest of the dark theme. It closes on the
   same blue the features band runs, hand-set rather than taken from --pm-band,
   so the page is bookended by its one saturated surface. White copy on it
   measures 4.80:1; the black wordmark 4.38:1. */
.footer-min { background: #0C79B0; border-top: 1px solid var(--pm-bline-2); }
/* #52646E, not --pm-body: the footer runs on --pm-band, and the page's body
   grey measures 4.43:1 there — short by 0.07. This is the same grey a shade
   down, at 5.0:1. */
.footer-min .footer-copy { color: #FFFFFF; }
.footer-min .footer-copy span { color: #000000; font-weight: 700; }
.footer-min .footer-links a { color: #FFFFFF; transition: color .22s ease; }
.footer-min .footer-links a:hover { color: #000000; }
/* a dark 28% tint left over from when this bar was a light tint — on the blue
   it blends to about 1.4:1 and the divider between the two links disappears */
.footer-min .sep { color: rgba(255, 255, 255, .55); }

/* ═══════════════ REDUCED MOTION ═══════════════
   The hero, reveal and marquee blocks each opt out locally; this catches
   the decorative loops that run forever regardless of scroll position —
   those are the ones that actually cause trouble for motion-sensitive
   readers, because they never stop. */
@media (prefers-reduced-motion: reduce) {
  .pm-band__inner { animation: none; background-position: 0 0; }
  .pm-dot { animation: none; }
  .pm-hero__art { transition: none; }
  .pm-progress { transition: none; }
  .pm-case-card__ic, .pm-svc__ic, .pm-award__medal, .pm-award::before { transition: none; }
  .pm-model, .pm-dq__card, .pm-shot { transition: none; }
}

/* ═══════════════ RESPONSIVE ═══════════════ */
@media (max-width: 1280px) {
  :root { --pm-pad: 80px; }
  .pm-hero { padding: 150px 0 74px; }
  .pm-hero__grid { gap: 42px; }
}

@media (max-width: 1024px) {
  :root { --pm-pad: 68px; }
  .pm-hero { padding: 132px 0 64px; }
  .pm-hero__grid { grid-template-columns: 1fr; gap: 46px; }
  .pm-hero__copy { max-width: 100%; }
  .pm-hero__visual { order: 2; }
  /* the features artwork un-sticks once its column is full width — a
     sticky element in a single-column stack pins over what follows */
  /* the showcase panel has nothing left to stretch against in one
     column, so it goes back to hugging the screenshot */
  .pm-cases__grid, .pm-svc__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .pm-awards__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .pm-band__inner, .pm-svc__cta { padding: 40px 34px; }
}

@media (max-width: 768px) {
  :root { --pm-pad: 56px; --pm-r-lg: 20px; }
  body { font-size: 16px; }
  .pm-hero { padding:80px 0 56px; }
  .pm-head { margin-bottom: 40px; }
  .pm-hero__cta { gap: 11px; }
  /* The sibling pages put two buttons on this row, so 100% each made them
     share it. This hero has ONE, and a 728px pill at 768px read as a banner
     rather than a button — cap it and let the phone widths still fill. */
  .pm-hero__cta .pm-btn { flex: 1 1 100%; max-width: 420px; }
  .pm-hero__points { gap: 11px; margin-bottom: 24px; }
  .pm-hero__points li { font-size: 14.6px; gap: 11px; }
  .pm-chip { display: none; }
  .pm-stats { gap: 14px; }
  .pm-stat { padding: 24px 20px; }
  .pm-cases__grid, .pm-svc__grid { grid-template-columns: 1fr; }
  .pm-awards__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .pm-band__inner { flex-direction: column; align-items: flex-start; }
  .pm-band__inner .pm-btn, .pm-svc__cta .pm-btn { width: 100%; }
  .pm-svc__cta { flex-direction: column; align-items: flex-start; }
  #faq .faq-item summary { padding: 18px 18px; font-size: 15.5px; }
  #faq .faq-answer { padding-left: 18px; padding-right: 18px; }
  #faq .faq-item[open] summary { padding-bottom: 13px; }
  #faq .faq-item[open] > .faq-answer { padding-top: 14px; padding-bottom: 20px; }
}

@media (max-width: 520px) {
  .pm-hero__title { font-size: 31px; }
  .pm-awards__grid { grid-template-columns: 1fr; }
  .pm-band__inner, .pm-svc__cta { padding: 30px 22px; }
  /* the card sizing lives on .pm-logo's own font-size, handled by the
     breakpoints in the logo-strip block — nothing to override per-logo here */
  .pm-strip { padding: 20px 0 24px; }
  .pm-strip__cap { font-size: 10.5px; margin-bottom: 15px; }
}


/* The INTRO section ("What Is Panel Management Software?") was removed on
   2026-08-12 at the user's request, and .pm-intro__grid / __copy went with it.
   `images/management-software.webp` is now referenced by nothing — left in the
   folder rather than deleted, like the card texture before it.

   .pm-figure survives below: it is the shared treatment for a light UI shot on
   a light section, and nothing on the page uses it today, but it is the pair to
   .pm-shot and the next screenshot dropped on this page wants it. */

/* Same problem as the hero shot, opposite ground: this is a light UI on a
   white section, so it has no edge of its own to show. It gets a hairline
   frame and a two-part lift — a tight neutral shadow that sets it on the
   page, and a wider one in the page's own sky blue, which keeps a shot of a
   blue product from reading as a grey rectangle. Matching the hero's
   treatment is deliberate: both shots read as the same kind of object — the
   hero one now gets its separation from the mint block behind it instead,
   because a shadow alone cannot hold a white picture on a white wash. */
.pm-figure {
  margin: 0; overflow: hidden;
  border: 1px solid var(--pm-line); border-radius: var(--pm-r-lg);
  /* background: var(--pm-paper);
  box-shadow: 0 2px 4px rgba(16, 43, 58, .05), 0 30px 66px rgba(31, 162, 224, .14); */
}
/* height:auto, as on .pm-shot: the attributes below are the real 1672x941,
   and without it a later asset of another aspect would be stretched to them */
.pm-figure img { display: block; width: 100%; height: auto; }

/* ═══════════════ DELIVERY MODELS ═══════════════
   The source for this section is a three-row table (model / best for /
   what OnGraph builds). A three-column table that narrow is unreadable
   on a phone, so each model becomes a column and the two row labels
   survive as small caps inside it: the information structure is kept,
   the table layout is not. */
.pm-model__grid { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 22px; }

/* Each card used to carry its OWN pastel wash — violet, blue, violet again.
   Colour that varies per card but means nothing reads as three unrelated
   blocks, not as three routes to compare, and the odd blue one in the middle
   looked like a mistake. All three now share one surface, and the per-model
   hue moved to the things that mark WHICH route it is: the rule across the
   top, the icon tile, the number and the link. Same information, and the eye
   can finally run across the three rows and compare them. */
.pm-model {
  /* --m1 paints the rule, the tile and the 01/02/03 marker — all decorative,
     all fine at the bright value. --m1d is the same identity for TEXT: the
     "Discuss this model" link is 14.5px on a near-white card, where --m1
     measures 2.5-2.8:1. */
  --m1: var(--pm-sky); --m1d: #096B9B; --m2: #5FC8EE;
  --mb: rgba(31, 162, 224, .38); --ms: rgba(31, 162, 224, .17);
  position: relative; overflow: hidden; display: flex; flex-direction: column;
  border-radius: var(--pm-r-lg);
  /* no padding-top: the header zone owns it, so it can bleed to the edges */
  padding: 0 30px 26px;
  border: 1px solid var(--pm-line);
  /* white, not the near-white gradient it was. That ran #FBFDFF to #EAF4FB
     against a WHITE section — 3 L* of separation at the top of the card and
     none of it where the eye enters. The card takes its edge from the shadow
     and its identity from the header band instead. */
  background: #fff;
  box-shadow: 0 2px 8px rgba(16, 43, 58, .05);
  transition: transform .32s cubic-bezier(.22,1,.36,1), box-shadow .32s ease, border-color .32s ease;
}
.pm-model--b { --m1: var(--pm-green); --m1d: #04795A; --m2: #4BDCB4; --mb: rgba(0, 184, 135, .38);  --ms: rgba(0, 184, 135, .17); }
.pm-model--c { --m1: var(--pm-aqua); --m1d: #0A7A86; --m2: #5FD9E6; --mb: rgba(13, 177, 196, .38);  --ms: rgba(13, 177, 196, .17); }

/* the card already clips, so the rule can sit flush in the rounded corners */
.pm-model::before {
  content: ""; position: absolute; top: 0; left: 0; right: 0; height: 4px;
  background: linear-gradient(90deg, var(--m1), var(--m2)); z-index: 2;
}
.pm-model:hover {
  transform: translateY(-8px);
  border-color: var(--mb);
  box-shadow: 0 30px 60px var(--ms);
}

/* THE HEADER ZONE — icon, route number and title on their own ground.
   The card used to be one flat pane: a 34px watermark numeral, an icon, a
   title and two label/value rows all sharing a single surface, which left the
   eye nothing to land on and made three cards meant for COMPARISON read as
   three loose stacks of text. Giving the identity half of the card its own
   tinted band does three things at once — it separates identity from spec, it
   lines the three titles up as a band across the row, and it carries the
   per-model hue at a size worth seeing.

   It bleeds to the card edges on negative margins rather than needing a second
   wrapper: the card's horizontal padding is the body inset and the head
   cancels it. Change one, change the other (including in the phone block). */
.pm-model__head {
  margin: 0 -30px 22px; padding: 30px 30px 22px;
  background: linear-gradient(180deg, var(--ms) 0%, rgba(255, 255, 255, 0) 100%);
  border-bottom: 1px solid var(--pm-line-2);
}

/* Route marker. Decorative — the heading already says which model this is — so
   it is aria-hidden and sits out of the flow.

   It was a 34px numeral at 17% opacity, which is the trap a big pale watermark
   always sets: at that size it is the second-largest thing in the card and it
   competes with the title, and at that opacity it is unreadable anyway — loud
   and useless at once. As a small solid chip beside the icon it says "route 1
   of 3" in the space that is worth, and it can carry real colour. */
.pm-model__no {
  position: absolute; top: 34px; right: 26px; z-index: 1;
  font-family: var(--pm-display); font-size: 12px; font-weight: 800;
  letter-spacing: .08em; line-height: 1; color: var(--m1d);
  background: #fff; border: 1px solid var(--mb);
  padding: 7px 11px; border-radius: 999px;
  transition: background .32s ease, color .32s ease;
}
.pm-model:hover .pm-model__no { background: var(--m1d); color: #fff; }

/* filled, not a white square with a tinted glyph — it is the card's anchor */
.pm-model__ic {
  width: 52px; height: 52px; border-radius: 16px;
  display: grid; place-items: center; margin-bottom: 18px;
  background: linear-gradient(140deg, var(--m1), var(--m2));
  color: #fff; box-shadow: 0 10px 22px var(--ms);
  transition: transform .42s cubic-bezier(.22,1,.36,1);
}
.pm-model:hover .pm-model__ic { transform: rotate(-6deg) scale(1.06); }
.pm-model__ic svg { width: 24px; height: 24px; }
.pm-model h3 { font-size: 19.5px; font-weight: 700; margin: 0; line-height: 1.32; padding-right: 52px; }
/* "White-Label Panel Management Software" is two lines where the other two
   titles are one, which staggered every "Best for" row across the row of
   cards — the labels have to line up for the three to read as a comparison.
   Two lines at 19.5px/1.32 measure 52px. It matters MORE now than it did on
   the flat card: the reserved line keeps the three header BANDS the same
   height, so the three bodies start on one line. Only needed side by side. */
@media (min-width: 769px) { .pm-model h3 { min-height: 52px; } }

/* the spec rows — the half of the card that is actually being compared */
.pm-model__row + .pm-model__row { margin-top: 14px; padding-top: 14px; border-top: 1px solid var(--pm-line); }
/* the floor under the last row, so the button never touches the copy on a card
   whose content happens to fill the height; margin-top:auto on the button
   handles the opposite case. */
.pm-model__row:last-of-type { margin-bottom: 24px; }
.pm-model__k { display: block; font-family: var(--pm-display); font-size: 10.5px; font-weight: 700; letter-spacing: .14em; text-transform: uppercase; color: var(--pm-body); margin-bottom: 7px; }
.pm-model__v { margin: 0; font-size: 15px; line-height: 1.62; color: #101a20; font-weight: 600; }

/* A BUTTON, not a text link. This was an inline arrow link on
   `align-self: flex-start`, which is the weakest possible ending for a card
   whose entire purpose is to be chosen — the section presented a decision and
   then whispered the way to act on it. Full width, so the three read as three
   equal choices and their edges line up; outlined rather than filled, so they
   do not compete with the page's one primary CTA; filling with the card's own
   hue on hover, which is the moment the route gets picked.

   margin-top:auto keeps all three on one line whatever the copy above does. */
.pm-model__cta {
  margin-top: auto;
  display: flex; align-items: center; justify-content: center; gap: 9px;
  padding: 13px 20px; border-radius: 999px;
  border: 1.5px solid var(--mb); background: #fff; color: var(--m1d);
  font-family: var(--pm-display); font-size: 14.5px; font-weight: 700;
  letter-spacing: normal; text-decoration: none; cursor: pointer;
  transition: background .28s ease, color .28s ease, border-color .28s ease, box-shadow .28s ease;
}
.pm-model__cta:hover {
  background: var(--m1d); border-color: var(--m1d); color: #fff;
  box-shadow: 0 10px 24px var(--ms);
}
.pm-model__cta svg { width: 16px; height: 16px; transition: transform .3s ease; }
.pm-model:hover .pm-model__cta svg, .pm-model__cta:hover svg { transform: translateX(5px); }
.pm-model__cta:focus-visible { outline: 2px solid var(--m1d); outline-offset: 3px; }

/* ═══════════════ INTEGRATIONS ═══════════════
   Eight integration families reuse the use-case card, four across:
   the shared three-column grid would strand two cards on a third row.
   These queries sit after the generic RESPONSIVE block on purpose —
   same specificity, so source order is what makes them win. */
.pm-cases__grid--4 { grid-template-columns: repeat(4, minmax(0, 1fr)); gap: 20px; }
.pm-cases__grid--4 .pm-case-card { padding: 28px 24px 26px; }
.pm-cases__grid--4 .pm-case-card__ic { width: 46px; height: 46px; border-radius: 13px; margin-bottom: 18px; }
.pm-cases__grid--4 .pm-case-card__ic svg { width: 21px; height: 21px; }
.pm-cases__grid--4 .pm-case-card h3 { font-size: 17px; margin-bottom: 9px; }
.pm-cases__grid--4 .pm-case-card p { font-size: 14.2px; line-height: 1.66; }
@media (max-width: 1200px) { .pm-cases__grid--4 { grid-template-columns: repeat(3, minmax(0, 1fr)); } }
@media (max-width: 900px)  { .pm-cases__grid--4 { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (max-width: 560px)  { .pm-cases__grid--4 { grid-template-columns: 1fr; } }

/* ═══════════════ DATA QUALITY ═══════════════
   Nine short labels, not nine paragraphs — so these are compact check
   rows in a 3x3, not cards with body copy that would have to be
   invented to fill them. This is the section the verification GREEN is
   reserved for: every row here is a verification step, and green is the only
   signal colour the light palette has left now that blue is the page accent.

   The section runs white (its neighbours either side are tinted), so the rows
   take the tint instead — the same swap the features cards make in reverse. */
.pm-dq__grid { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 14px; }
.pm-dq__card {
  display: flex; align-items: center; gap: 14px;
  background: var(--pm-paper-2); border: 1px solid var(--pm-bline-2);
  border-radius: 15px; padding: 18px 20px;
  transition: transform .3s cubic-bezier(.22,1,.36,1), border-color .3s ease, background .3s ease, box-shadow .3s ease;
}
.pm-dq__card:hover {
  transform: translateY(-5px); border-color: rgba(0, 184, 135, .42);
  background: rgba(0, 184, 135, .07); box-shadow: 0 14px 30px rgba(16, 43, 58, .08);
}
.pm-dq__ic {
  width: 38px; height: 38px; flex-shrink: 0; border-radius: 11px; display: grid; place-items: center;
  color: #039C72; background: rgba(0, 184, 135, .12); border: 1px solid rgba(0, 184, 135, .26);
  transition: background .3s ease, color .3s ease;
}
.pm-dq__ic svg { width: 18px; height: 18px; }
.pm-dq__card:hover .pm-dq__ic { background: var(--pm-green); color: #fff; }
.pm-dq__card p { margin: 0; font-family: var(--pm-display); font-size: 15px; font-weight: 600; letter-spacing: normal; color: var(--pm-head); line-height: 1.4; }
@media (max-width: 1024px) { .pm-dq__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (max-width: 640px)  { .pm-dq__grid { grid-template-columns: 1fr; } }


/* ─────────────── small-screen trims for the blocks above ─────────────── */
@media (max-width: 1024px) {
  .pm-model__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  /* three models on a two-column grid leaves the third beside a hole */
  .pm-model__grid > :last-child:nth-child(odd) { grid-column: 1 / -1; }
  /* The h3 min-height above reserves two lines so the "Best for" labels line
     up ACROSS a row. The card that goes full-width here has no neighbour to
     line up with, so the reserved second line is just a hole under a
     one-line title. */
  .pm-model__grid > :last-child:nth-child(odd) h3 { min-height: 0; }
}
@media (max-width: 768px) {
  .pm-model__grid { grid-template-columns: 1fr; }
  .pm-model__grid > :last-child:nth-child(odd) { grid-column: auto; }
  /* the head's negative margin must equal this inset — see .pm-model__head */
  .pm-model { padding: 0 24px 24px; }
  .pm-model__head { margin: 0 -24px 20px; padding: 26px 24px 20px; }
  .pm-model__no { top: 30px; right: 22px; }
}

/* ═══════════════════════════════════════════════════════════════
   LAPTOP HERO TRIM — scoped by viewport HEIGHT, not width.
   A 1366x768 laptop leaves ~640px of viewport once browser chrome
   is taken out, so the hero has to be exactly one screen or the
   CTAs fall under the fold. 1080p at 100% gives ~945px and never
   matches, so tall monitors stay pixel-identical.
   The shared header is fixed and the hero starts at y=0, so
   100vh = header + hero = one screen.
   ═══════════════════════════════════════════════════════════════ */
@media (min-width: 1200px) and (max-height: 820px) {
  .pm-hero {
    /* 100vh MINUS a sliver, so the top of the logo strip shows above the
       fold. At a flat 100vh the hero ends exactly on the fold and the page
       looks finished there — the cue the card overlap used to give. */
    min-height: calc(100vh - 46px);
    display: flex; flex-direction: column;
    align-items: stretch; justify-content: center;
    padding-top: 96px;
    /* the cards ride -44px up into this, so it is the overlap plus whatever
       gap is left under the terms bar — not spare air. But this box is
       min-height:100vh with justify-content:center, so the REAL gap is this
       padding plus half the leftover slack; once the hero copy dropped to one
       paragraph there was a lot of slack, and 92px opened a 150px void. */
    padding-bottom:24px;
  }
  .pm-hero__grid { gap: 40px; }
  /* 2.9vw keeps every authored line inside the copy column down to
     1200px; at 3.1vw the gradient line wrapped and pushed the hero
     past the one-screen budget */
  .pm-hero__title { font-size: clamp(30px, 2.9vw, 42px); margin: 10px 0 9px; }
  /* The sibling page re-joined its first two lines here (display:inline)
     because they measured 28 characters. These two are 41 together —
     inlined they wrap at a point the viewport chooses rather than the one
     the lockup authored, so all three lines stay blocks and the size
     clamp above is what buys the vertical budget instead. */
  .pm-hero__sub { font-size: 15.5px; margin-bottom: 15px; }
  .pm-hero__cta { margin-bottom: 12px; }
  .pm-hero__btn, .pm-hero__cta .pm-btn { padding-top: 13px; padding-bottom: 13px; }
  /* the ~60px the full-width terms bar used to cost is gone with the bar —
     the three points live in the copy column now and cost only their own
     rows. They still tighten here, because on a short screen every row in
     that column competes with the artwork beside it for the same budget. */
  .pm-hero__points { gap: 10px; margin-bottom: 18px; }
  .pm-hero__points li { font-size: 14.4px; gap: 11px; }
  .pm-hero__pt { width: 26px; height: 26px; }
  .pm-hero__pt svg { width: 13px; height: 13px; }
  /* This block used to zero the overlap, which meant EVERY laptop — the
     query is max-height:820, so it catches 1366x768, 1440x900, 1536x864 —
     lost the effect that only 1080p-and-taller monitors got to see. The
     overlap stays on now; the clearance it needs is bought from the padding
     above instead, which is free here because the hero sits on min-height
     100vh with slack to spare rather than at its natural height. */
  /* no overlap left to tune — just a tighter gap, because the strip and the
     first card both have to clear a one-screen hero */
  .pm-usp__grid { margin-top: 36px; }
  /* the sliver above the fold has to be worth showing: at 26px of strip
     padding the caption is clipped through its own line, which reads as a
     rendering fault rather than a hint. 14px, not 18: at 1366x768 the hero
     content runs 8px past its own min-height, so the sliver is 38px there and
     18px of padding put the caption's last pixel exactly on the fold. */
  .pm-strip { padding-top: 14px; }
  /* The shot is square, and js owns its transform — so the only way it can
     give height back to a one-screen budget is width. 460px is the measured
     ceiling less a margin: at 1366x768, the shortest screen this block has to
     hold, 480px pushed the hero 10px past 100vh and 470px landed exactly on
     it. 460 leaves that 10px as headroom for a machine whose fonts set the
     copy column one line taller. */
  /* the token, not .pm-shot's own max-width: .pm-hero__visual reads it too, and
     if only the shot shrinks the chips stop sitting on the artwork's corners */
  .pm-hero { --shot-w: 560px; }
  /* The chips used to be hidden here. That rule existed because they floated in
     the slack ABOVE and BELOW the artwork, and this block compresses the hero
     until that slack is gone — the bottom one landed on the terms bar (measured
     131x21 at 1280x800). They ride the artwork's own corners now, so they
     compress with it and there is nothing left to collide with; hiding them
     meant every laptop under 820px tall lost them. Phones still drop them at
     <=768, where the artwork is too small to carry a 180px pill. */
}

/* ═══════════════ VIDEO DEMO ═══════════════
   Poster + play trigger. The dialog it opens is styled in css/base-styles.css
   and driven by initVideoModal() in common-js/main.js — see the note on the
   markup in index.html.

   The whole poster is the button, not just the disc: a 92px target in the
   middle of a 1080px image is the smallest thing on the page to hit, and the
   image is doing nothing else. */
.pm-video-sec .pm-head { margin-bottom: 48px; }
.pm-video {
  position: relative; display: block;
  width: 100%; max-width: 960px; margin: 0 auto;
  padding: 0; border: 1px solid var(--pm-line); border-radius: 26px;
  background: #fff; overflow: hidden; cursor: pointer;
  box-shadow: 0 28px 66px rgba(16, 43, 58, .13);
  transition: transform .42s cubic-bezier(.22,1,.36,1), box-shadow .42s ease, border-color .42s ease;
}
.pm-video__poster { display: block; width: 100%; height: auto; }
.pm-video:hover, .pm-video:focus-visible {
  transform: translateY(-6px);
  border-color: rgba(31, 162, 224, .34);
  box-shadow: 0 40px 88px rgba(31, 162, 224, .24);
}

/* pointer-events:none on the wrapper so every pixel of it still counts as a
   click on the button underneath — including the gap inside the ring */
.pm-video__play {
  position: absolute; left: 50%; top: 50%; transform: translate(-50%, -50%);
  width: 212px; height: 212px; display: grid; place-items: center;
  pointer-events: none;
}
/* The poster is a light but BUSY render — charts, faces, a world map. The ring
   text is unreadable wherever a chart sits behind a letter, so the lockup
   carries its own soft white ground. It matters MORE on a light page, not
   less: the poster is no longer the brightest thing in its section. */
.pm-video__play::before {
  content: ""; position: absolute; inset: -12px; border-radius: 50%;
  background: radial-gradient(closest-side, rgba(255, 255, 255, .97) 62%, rgba(255, 255, 255, .93) 80%, rgba(255, 255, 255, .55) 90%, transparent 100%);
}
.pm-video__ring {
  position: absolute; inset: 0; width: 100%; height: 100%;
  animation: pmVideoSpin 18s linear infinite;
}
.pm-video__ring text {
  font-family: var(--pm-display); font-size: 15.5px; font-weight: 800;
  letter-spacing: .2em; text-transform: uppercase; fill: var(--pm-sky-d);
}
.pm-video__btn {
  position: relative; width: 104px; height: 104px; border-radius: 50%;
  display: grid; place-items: center; color: #fff;
  background: var(--pm-grad-b);
  box-shadow: 0 18px 40px rgba(31, 162, 224, .44), inset 0 1px 0 rgba(255, 255, 255, .3);
  transition: transform .38s cubic-bezier(.22,1,.36,1), box-shadow .38s ease;
}
/* optical centring: a right-pointing triangle's bounding box has its visual
   mass left of centre, so a mathematically centred glyph reads as too far left */
.pm-video__btn svg { width: 36px; height: 36px; margin-left: 4px; }
.pm-video__btn::after {
  content: ""; position: absolute; inset: -12px; border-radius: 50%;
  border: 2px solid rgba(31, 162, 224, .45);
  animation: pmVideoPulse 2.8s ease-out infinite;
}
.pm-video:hover .pm-video__btn {
  transform: scale(1.09);
  box-shadow: 0 24px 52px rgba(31, 162, 224, .55), inset 0 1px 0 rgba(255, 255, 255, .3);
}
@keyframes pmVideoSpin { to { transform: rotate(360deg); } }
@keyframes pmVideoPulse {
  0%   { transform: scale(.9);  opacity: .85; }
  100% { transform: scale(1.55); opacity: 0; }
}

/* This block sits at the END of the sheet, so it must carry its own
   breakpoints — a later base declaration beats an earlier @media. */
@media (max-width: 900px) {
  .pm-video__play { width: 158px; height: 158px; }
  .pm-video__ring text { font-size: 13px; letter-spacing: .17em; }
  .pm-video__btn { width: 76px; height: 76px; }
  .pm-video__btn svg { width: 27px; height: 27px; }
}
@media (max-width: 560px) {
  .pm-video { border-radius: 18px; }
  .pm-video__play { width: 118px; height: 118px; }
  /* the ring text stops fitting the arc long before the disc stops fitting
     the poster — the disc alone still reads as "play" */
  .pm-video__ring { display: none; }
  .pm-video__btn { width: 62px; height: 62px; }
  .pm-video__btn svg { width: 22px; height: 22px; }
}
@media (prefers-reduced-motion: reduce) {
  .pm-video__ring { animation: none; }
  .pm-video__btn::after { animation: none; opacity: 0; }
  .pm-video { transition: none; }
}
/* ── intl-tel-input country dropdown ────────────────────────────────────────
   The list is rendered with `dropdownContainer: document.body`, so it lives
   OUTSIDE the lead modal's stacking context. The library's own z-index is
   1060, which is *below* .lead-modal-overlay (z-index 9999) — the list opened
   but was painted behind the popup, which reads as "the country list does not
   open at all". Being on <body> it also inherits the page's text colour, so
   the colours are pinned here instead of trusting whatever theme is around it. */
html .iti--container { z-index: 10050; }
html .iti__country-list,
html .iti__dropdown-content { background: #FFFFFF; color: #1A1A1A; }
html .iti__country { color: #1A1A1A; }
html .iti__country-name { color: #1A1A1A; }
html .iti__dial-code { color: #6B6B6B; }
html .iti__country.iti__highlight,
html .iti__country:hover { background: #F1F1F1; }
html .iti__search-input { color: #1A1A1A; background: #FFFFFF; }

/* Safari: a large filter:blur() on a moving, composited layer inside an
   overflow:hidden hero gets painted as a solid BLACK box in Safari (Chrome is
   fine). The blur is dropped; each glow's box grows by 2x the old blur radius
   (negative margin keeps it centred) and its gradient stops are the old
   blurred profile, so it looks the same with no filter. */
.pm-bloom { filter: none; margin: -180px; }
.pm-bloom--tl { width: 880px; height: 880px; background: radial-gradient(circle closest-side, rgba(31, 162, 224, 0.158) 0%, rgba(31, 162, 224, 0.157) 10%, rgba(31, 162, 224, 0.152) 20%, rgba(31, 162, 224, 0.141) 30%, rgba(31, 162, 224, 0.123) 40%, rgba(31, 162, 224, 0.096) 50%, rgba(31, 162, 224, 0.066) 60%, rgba(31, 162, 224, 0.039) 70%, rgba(31, 162, 224, 0.019) 80%, rgba(31, 162, 224, 0.008) 90%, rgba(31, 162, 224, 0) 100%); }
.pm-bloom--br { width: 920px; height: 920px; background: radial-gradient(circle closest-side, rgba(0, 184, 135, 0.12) 0%, rgba(0, 184, 135, 0.119) 10%, rgba(0, 184, 135, 0.116) 20%, rgba(0, 184, 135, 0.11) 30%, rgba(0, 184, 135, 0.097) 40%, rgba(0, 184, 135, 0.078) 50%, rgba(0, 184, 135, 0.054) 60%, rgba(0, 184, 135, 0.032) 70%, rgba(0, 184, 135, 0.016) 80%, rgba(0, 184, 135, 0.006) 90%, rgba(0, 184, 135, 0) 100%); }
