/* pages/pricing.css — the rules this page OWNS.
   Split from styles.css, components.css, paid.css, content.css by agent-os/tools/split_page_css.py. Only selectors whose classes are
   used by NO other page in this site moved here; shared rules stayed put, because
   duplicating one fact into several files is how the copies drift apart. */
/* .plan-badge is deliberately NOT here. It is exclusive to this page, but components.css also names it
   in a 15-selector grouped `line-height:1.5` base rule that cannot move (the other 14 selectors are
   shared). This sheet loads last, so re-homing it gave one selector two homes and page_css_cascade
   flagged the override. Reverted to components.css rather than pushed past the gate. */
/* ===== THE FIRST VIEWPORT OF A PRICING PAGE MUST CONTAIN SOMETHING TO PRESS =====
   Measured on the served site through serve_ui.py, viewport-only captures, always starting
   unscrolled: the tier CTA row began at y=1036 at 1280x720 AND at 1646x893. Below the fold at
   both — 352px and 179px of deliberate scroll before one pixel of a button appeared. A prospect
   met four prices and no control.
   Two things put it there and both are addressed. The card-internal one (the feature list absorbing
   the slack and sinking the action to the foot of the tallest card) is fixed in pricing.ui.jsx by
   placing the action with the price. This block is the other one: 386px of a 720px viewport — 54%
   — was spent on nav and hero before the subject of the page began. That is right for a landing
   page and wrong for the page whose whole job is "pick a tier and act".
   SCOPED TO THIS ROUTE ON PURPOSE. .ind-hero and .section are shared with the industry pages and
   every other route; compacting them globally would be one page's problem charged to all of them.
   ONE DECISION, SEVERAL PLACES, because that is where this route's furniture lives — the hero
   padding, the headline's measure, the section's lead-in, and the three whitespace gaps between the
   banner, the billing toggle, the legend and the ladder. Every value below is a REDUCTION of
   spacing. No copy is removed, no type size changes, no honesty banner is touched: a visitor still
   reads the same words in the same order, and now reaches a button while doing it.
   VERIFY BY MEASURING, NOT BY READING. The first version of this block left the comment above
   unterminated, so the browser's error recovery swallowed the very next rule — the hero padding —
   and the page rendered as if the fix had not been written. Reading the file showed a fix; the
   computed style showed 54px where 18px was declared. Every number here was checked against
   getComputedStyle and a viewport-only capture, unscrolled, at 1280x720, 1366x768, 1440x900 and
   1646x893. */
.pricing-page .ind-hero{padding:18px 0 14px}
/* Font size is UNCHANGED — this is the measure, not the type scale, and the type scale is not
   this file's to set. .ind-hero h1 caps at 20ch, which wrapped a 58-character headline onto three
   lines (136px) at every desktop width. Two lines on a desktop viewport, three when the viewport
   is genuinely narrow enough to need them.
   1081px, not a number of its own: it is the width above which components.css keeps this page's
   four-column ladder, and it is the same breakpoint the head reservation below uses. One boundary,
   one meaning — "the desktop four-column ladder" — rather than two breakpoints that drift apart.
   Set at 1200 first, which left 1081-1199 with a three-line headline and the action row 82px under
   a 700px fold. Measured, not assumed. */
@media (min-width:1081px){ .pricing-page .ind-hero h1{max-width:34ch} }
.pricing-page .section{padding-top:12px}
/* .gate-banner and .bill-toggle live in paid.css and are shared with the customer portal, so the
   reduction is scoped here rather than made there. 1.25rem -> .75rem, twice. */
.pricing-page .gate-banner,
.pricing-page .bill-toggle{margin-bottom:.75rem}
.pricing-page .plan{padding-top:16px}

/* ONE RESERVED HEIGHT FOR THE WHOLE CARD HEAD — audience line, tier name, price, billing note.
   Each of those wraps differently per tier, so reserving them individually meant four guesses and
   still produced a row of buttons on two different lines (measured 677/711, then 714/732). Grouping
   them makes the button below start at the same y on every card by construction. The number is the
   tallest head the current tier set produces at the narrowest column this grid uses, measured, not
   estimated; a tier whose copy grows past it makes ALL four cards taller together rather than
   pushing one button out of line.
   Shortening the copy would have been the cheaper fix and the wrong one: "Strategy / manufacturer /
   distributor / PE-M&A" answers "is this me?", and trimming a customer's answer to win pixels is
   not a layout decision. */
.tier-head{display:flex;flex-direction:column}
.tier-head .tier-note{margin-top:2px}
/* RESERVED ONLY WHERE IT WAS MEASURED, AND ONLY WHERE IT BUYS ANYTHING. 183px is the tallest head
   the current tier set produces in the FOUR-COLUMN ladder — the narrowest these cards ever get, and
   the only band where the fold defect was reproduced. Below 1081px components.css drops the grid to
   two columns and then one; the cards are wider there, every line fits, and the natural head is
   ~40-60px shorter. Applying a four-column number to a one-column phone would have reserved dead
   space under five stacked cards to solve a problem that band does not have.
   The audience line is reserved at its own two lines for the same reason and at no cost: the head
   is already reserved at the height Portfolio's two-line audience needs, so this only spends slack
   the shorter cards had going begging, and the tier NAME and PRICE then start at the same y on all
   four instead of Portfolio's pair sitting 17px lower. 33px is two lines of an 11px/1.5 label. */
@media (min-width:1081px){
  .tier-head{min-height:183px}
  .tier-head>.pf{min-height:33px}
}

.ladder-head{margin-bottom:16px}
.ladder-head p{color:var(--muted);font-size:14.5px;margin-top:8px;max-width:70ch}
.tier-card{display:flex;flex-direction:column;}
/* The action now precedes the feature list, so the gap that used to sit above it belongs below it.
   `flex:1 1 auto` still lets the list absorb the slack — which is what keeps the cards equal
   height — it just no longer has the button underneath it to push down. */
.tier-card>.btn-block{margin-bottom:18px}
.tier-card ul{flex:1 1 auto;}
.tier-fit{margin:.5rem 0;font-size:.85em;font-weight:600;}
.slice-picker{margin-top:2.5rem;}
.picker-total{margin-top:1rem;display:flex;align-items:center;flex-wrap:wrap;gap:.5rem;}
.picker-total b{font-size:1.1em;margin-right:.4rem;}
.fit-pill{padding:.2rem .6rem;border-radius:999px;font-size:.8em;border:1px solid var(--line);}
.slice-chip-name{display:block;white-space:normal;overflow-wrap:anywhere;}
