/*
 * CHIMZEE BRAND ADOPTION LAYER
 * Version: 4.1.2  ·  built 2026-08-15 against brand tokens v1.7.0
 *
 * Chris, 2026-08-15: "Apply across the entire platform (all CRM, etc)."
 *
 * The platform is five separate applications on five ports, each with its own inline palette
 * written before the brand system existed: the workspace (9106), the dashboard and CRM
 * prototype (9130), the price book (9108), the client portal (9120) and analytics (9141).
 * Rewriting five stylesheets by hand is five migrations, five chances to leave a screen half
 * converted, and five places to redo the next time a token moves.
 *
 * So this is one file, loaded after each application's own <style>, doing three things:
 *
 *   1. It points their variable names at the brand tokens. Every one of them independently
 *      settled on --ink, --line, --mute, --card and a green, so the mapping is nearly the
 *      same in all five, and a screen written a year ago is on the system without being
 *      opened.
 *   2. It carries the three brand faces, since the token file names them but does not serve
 *      them.
 *   3. It restates shape: rounded glass panels, pill controls, the system's focus ring. Only
 *      appearance is touched, never layout. A radius cannot break a grid; a display property
 *      can, and there are screens here nobody has looked at in weeks.
 *
 * Load order matters and is the whole mechanism: this must come AFTER the application's own
 * inline style, because at equal specificity the last declaration wins. It must come after
 * chimzee-brand.css too, which is where every --cz-* value it reads is defined.
 *
 *   <link rel="stylesheet" href="/brand/chimzee-brand.css">
 *   <link rel="stylesheet" href="/brand/chimzee-adopt.css">
 *
 * Governance: /srv/chimzee-brand/BRAND.md. Do not add a raw colour here.
 */

/* ── the faces ─────────────────────────────────────────────────────────────── */
/* Relative to this stylesheet, not absolute, so one file works on both hosts. On chimzee.com
   it sits at /brand/ and resolves to /fonts/; on chriscaterine.com it sits at /chimzee/brand/
   and resolves to /chimzee/fonts/. An absolute /fonts/ would be a 404 on the second host,
   where that path is claimed by a different backend entirely. */
@font-face{font-family:'Cormorant Garamond';font-style:normal;font-weight:400;
font-display:swap;src:url(../fonts/cormorant-garamond-latin-abcaa8b4.woff2) format('woff2')}
@font-face{font-family:'Space Grotesk';font-style:normal;font-weight:300 700;
font-display:swap;src:url(../fonts/space-grotesk-latin-4ecc7e89.woff2) format('woff2')}
@font-face{font-family:'Geist Mono';font-style:normal;font-weight:300 700;
font-display:swap;src:url(../fonts/geist-mono-latin-749b501e.woff2) format('woff2')}

/* ── their names, our tokens ───────────────────────────────────────────────── */
/* Two are derived rather than picked. The greens and ambers in these apps carry small text,
   and --cz-color-positive and --cz-color-warning measure 3.4:1 and 3.9:1, which the brand
   system itself rules out as body copy. Each is mixed toward the ink until it clears 4.5:1,
   which is a derivative of two tokens rather than a new colour: the same move the canonical
   stylesheet makes for its own hairlines. */
:root{
  --bg:var(--cz-surface-page);
  --paper:var(--cz-surface-page);
  /* --card is what these apps paint a panel with, and pointing it at the page surface made
     every one of them a solid white block that no glass rule could reach: the app's own
     `.street table{background:var(--card)}` is more specific than anything a shared stylesheet
     can write for `table`. Pointing the token itself at the glass tint fixes them at the source
     instead of naming each one. --paper and --bg stay opaque: they are grounds, not cards. */
  --card:rgb(var(--cz-rgb-sky) / .027);
  --ink:var(--cz-text-heading);
  --line:var(--cz-color-line);
  --mute:color-mix(in srgb, var(--cz-text-body) 86%, var(--cz-color-ink));
  --cz-text-body:color-mix(in srgb, #5f7282 86%, #263f57);
  --cz-color-body-muted:color-mix(in srgb, #687c8b 72%, #263f57);
  --mute2:color-mix(in srgb, var(--cz-color-body-muted) 74%, var(--cz-color-ink));
  --label:var(--cz-text-body);
  --teal:color-mix(in srgb, var(--cz-color-positive) 62%, var(--cz-color-ink));
  /* --teal was these apps' success colour, so it stays green. --forest was not: on the old
     editorial pages it was the PRIMARY, setting links, buttons and headings, and mapping it to
     a green derivative turned every one of them green. Chris, 2026-08-17, looking at the live
     demo: "I'm still getting the old brand and the old colors of the old logo." The primary
     action colour is ink, so that is what the old primary becomes. */
  --forest:var(--cz-action-primary);
  --amber:color-mix(in srgb, var(--cz-color-warning) 62%, var(--cz-color-ink));
  --clay:color-mix(in srgb, var(--cz-color-warning) 62%, var(--cz-color-ink));
  --violet:var(--cz-logo-slate);
  --shadow:var(--cz-shadow-1);
  --serif:var(--cz-font-display);
  --ease:var(--cz-ease-standard);

  /* The glass, measured off chimzee.com rather than assembled from the tokens. Chris,
     2026-08-17: "I'm not getting that full glass feeling, and it does not match the website
     at all." The reason was --cz-glass-dialog, which is white at 90%: a card built on it is
     opaque paint, and no amount of blur behind an opaque surface can show through it.
     A real .coda-card on the live homepage computes to a sky or peach tint at 2.7%, a 145deg
     white sheen across it, blur(14px) saturate(1.12), a near-white hairline, 26px, and a wide
     soft drop with a bright inset along the top edge. These are those values. */
  --gl-tint:rgb(var(--cz-rgb-sky) / .027);
  --gl-tint-warm:rgb(var(--cz-rgb-peach) / .027);
  --gl-sheen:linear-gradient(145deg, rgba(255,255,255,.42),
                             rgba(255,255,255,.08) 52%, rgba(255,255,255,.2));
  --gl-blur:blur(14px) saturate(1.12);
  --gl-line:rgba(217,222,226,.92);
  /* The homepage's own drop is 0 38px 82px rgba(55,72,60,.15), which is a green-grey. It reads
     as depth there because a dozen big cards carry it down a long white page. Put it on every
     container of a dense admin screen and eighty of them stack into a green haze over the whole
     thing, which is dirt, not depth. Same geometry, the system's own cool ink instead, so the
     lift survives the density. */
  --gl-shadow:inset 0 1px 0 rgba(255,255,255,.94),
              var(--cz-shadow-2),
              0 8px 22px rgba(38,63,87,.05);
}

/* ── the field ─────────────────────────────────────────────────────────────── */
/* Chris, 2026-08-15: "I need each page and every dashboard to mimic chimzee.com." The first
   attempt at that put a CSS lattice here: a repeating linear-gradient grid with a dot at every
   half step. Chris, 2026-08-17: "I'm still getting the dots in the background, not the metrics
   that we are doing."

   He is right, and the reason is that nobody had measured the real page. chimzee.com's body is
   rgb(255,255,255) with background-image:none and no ::before at all. Its atmosphere is drawn
   by three <canvas> elements holding an irregular constellation: nodes of varying size, most
   of them slate, a few orange, joined to their near neighbours by thin straight lines. A
   regular grid of dots is the one thing it is not, and a grid is exactly what a repeating
   background-image can be.

   So this is the same constellation, generated by the same function that draws the login door
   (front._constellation, which Chris has looked at and not objected to), rendered once to
   /brand/field.svg and served as a file so it is cached rather than re-parsed, and sized to
   cover rather than tile so it never repeats. Static, so it costs one decode and no frames:
   the lag Chris reported is not something to answer with an animation loop. */
body{
  background:
    radial-gradient(ellipse 62% 44% at 18% 8%, rgb(var(--cz-rgb-peach) / .07), transparent 70%),
    radial-gradient(ellipse 58% 46% at 86% 34%, rgb(var(--cz-rgb-sky) / .06), transparent 72%),
    var(--cz-color-white);
  isolation:isolate;position:relative}
body::before{
  content:"";position:fixed;inset:0;z-index:-1;pointer-events:none;
  /* No opacity here and no mask. The nodes in field.svg are already drawn at .17 to .34, and
     the login door, which is the one screen Chris has looked at and approved, paints exactly
     this SVG with nothing on top of it. The first attempt multiplied it by --cz-lattice-opacity
     (.46) and then faded it out again with a mask, which took the nodes to roughly .08 and made
     the ground measure 254,251,249 against a white 255,255,255: a difference of four values,
     which is no difference. Chris: "There's no background gradient." */
  background-image:url(field.svg);
  background-size:cover;background-position:center top;background-repeat:no-repeat}

/* ── the floating bar ──────────────────────────────────────────────────────── */
/* The second part. Every one of these applications puts a solid slab of dark across the top,
   edge to edge. chimzee.com does the opposite: a white glass pill floating clear of the page,
   measured off the live site as rgba(255,255,255,.08) behind blur(22px) saturate(1.22), a
   near-white hairline, a 999px radius and an inset highlight along the top edge.
   Because the slab becomes light, everything written on it has to stop being white, which is
   what the rest of this block does. */
.czbar,.bar{
  background:rgba(255,255,255,.08)!important;
  -webkit-backdrop-filter:blur(22px) saturate(1.22);backdrop-filter:blur(22px) saturate(1.22);
  border:1px solid rgba(255,255,255,.82);
  /* Not a 999px pill: these bars are two rows tall and a stadium 130px high is a lozenge, not
     the site's nav. The site's own largest corner. */
  border-radius:var(--cz-radius-xl);
  box-shadow:var(--cz-shadow-inset),0 10px 30px rgb(var(--cz-rgb-sky) / .18);
  color:var(--cz-text-heading);
  margin:var(--cz-space-4) var(--cz-space-6);
  padding:var(--cz-space-2) var(--cz-space-4);
  position:sticky;top:var(--cz-space-3);z-index:60}
.czbar *,.bar *{color:var(--cz-text-heading)}
.czbar .sub,.bar .sub,.czbar .lane,.czbar [class*=label]{color:var(--cz-text-body)!important}
/* the mark was filtered to white to sit on the dark slab; on glass it is itself again */
.czbar img,.bar img,.czbar .logo img{filter:none!important}
/* Its buttons were outlined in white on navy. Same shape, ink hairline, ink text. */
.czbar .btn,.bar .btn,.czbar a.btn,.czbar .btn.onink,.bar .btn.onink{
  border:1px solid var(--cz-border-control)!important;color:var(--cz-text-heading)!important;
  background:var(--cz-glass-control)!important}
.czbar .btn:hover,.bar .btn:hover,.czbar .btn.onink:hover{
  background:var(--cz-action-primary)!important;border-color:var(--cz-action-primary)!important;
  color:var(--cz-text-inverse)!important}
/* The current screen. It was a white fill on the dark slab, which on glass is white on white:
   the workspace marks it `.here`, the trees mark it `.on`, and both read as disabled until
   they are filled with the ink. */
.czbar .btn.on,.bar .btn.on,.czbar .on,.bar nav a.on,.czbar .here,.czbar .btn.here{
  background:var(--cz-action-primary)!important;border-color:var(--cz-action-primary)!important;
  color:var(--cz-text-inverse)!important}
/* The group captions above each row were white at 42% for a dark bar, which on glass is
   nothing at all. */
.czbar .lanename,.czbar .lane,.bar .lanename{color:var(--cz-text-body)!important}

/* The little ↗ that marks a link leaving the tree. It was white at 50% for the dark slab,
   which on glass measures 1.02:1, which is to say it is not there. */
.czbar .btn.out span,.bar .btn.out span,.czbar .out span{color:var(--cz-text-body)!important}

/* ── the rails ─────────────────────────────────────────────────────────────── */
/* The third part. /crm2 still had a navy rail down the left, which is the one thing on that
   screen that says "different product". The new tree's rail went to light glass when Chris
   chose "All light, like the site", so this one follows it rather than being the last dark
   column on the platform.
   It is also what fixes the contrast underneath: its caption and its six nav glyphs were pale
   grey on navy at 3.68:1, and every attempt to fix that by darkening the grey made it worse,
   because the surface was dark and the token mapping is built for light. */
.side{
  background:var(--cz-glass-dialog)!important;
  color:var(--cz-text-heading)!important;
  border-right:1px solid var(--cz-border-subtle);
  -webkit-backdrop-filter:blur(var(--cz-glass-blur)) saturate(var(--cz-glass-saturation));
  backdrop-filter:blur(var(--cz-glass-blur)) saturate(var(--cz-glass-saturation))}
.side *{color:var(--cz-text-heading)}
.side .label,.side .user,.side small{color:var(--cz-text-body)!important}
.side .nav button{color:var(--cz-text-body)!important;background:transparent!important}
.side .nav button:hover{background:color-mix(in srgb, var(--cz-color-ink) 6%, transparent)!important;
  color:var(--cz-text-heading)!important}
.side .nav button.on{background:var(--cz-action-primary)!important;
  color:var(--cz-text-inverse)!important}
.side .nav button.on *{color:var(--cz-text-inverse)!important}
.side .brand img{filter:none!important}
.rail{
  background:var(--cz-glass-dialog)!important;color:var(--cz-text-heading)!important;
  border-right:1px solid var(--cz-border-subtle);
  -webkit-backdrop-filter:blur(var(--cz-glass-blur)) saturate(var(--cz-glass-saturation));
  backdrop-filter:blur(var(--cz-glass-blur)) saturate(var(--cz-glass-saturation))}
.rail *{color:var(--cz-text-heading)}
.rail .rail-brand strong{color:var(--cz-text-heading)!important}
.rail .rail-brand span,.rail .rail-meta,.rail .rail-group{color:var(--cz-text-body)!important}
.rail .rail-brand img{filter:none!important}
.rail .rail-nav button{color:var(--cz-text-body)!important;background:transparent!important}
.rail .rail-nav button:hover{color:var(--cz-text-heading)!important;
  background:color-mix(in srgb, var(--cz-color-ink) 6%, transparent)!important}
.rail .rail-nav button.on,.rail .rail-nav button.active{
  background:var(--cz-action-primary)!important;color:var(--cz-text-inverse)!important}
.rail .rail-nav button.on *,.rail .rail-nav button.active *{
  color:var(--cz-text-inverse)!important}
.rail .rail-nav button .num{color:var(--cz-text-body)!important}
/* Some of these rails write their nav as a bare <button> under a plain <nav>, not under
   .rail-nav, so the rules above walked straight past them and left white text on the glass at
   1.30:1. Anything inside the rail that is not the selected row is ink. */
.rail button,.rail b,.rail .num,.rail span,.rail small{color:var(--cz-text-heading)!important}
.rail button.on,.rail button.active,.rail button.on *,.rail button.active *{
  color:var(--cz-text-inverse)!important}

/* ── status colours that predate the system ────────────────────────────────── */
/* Raw reds, ambers and greys on the analysis pages: 3.36:1 to 4.08:1 as text, and the system
   already publishes the three it means. The ink-mix is because critical and warning are
   accents, and the system says an accent is not a body-copy colour. */
.pill.high,.num.high,.high{color:color-mix(in srgb, var(--cz-color-critical) 68%, var(--cz-color-ink))!important}
.pill.medium,.num.medium,.medium{color:color-mix(in srgb, var(--cz-color-warning) 62%, var(--cz-color-ink))!important}
.pill.low,.num.low,.low{color:color-mix(in srgb, var(--cz-color-positive) 48%, var(--cz-color-ink))!important}
.caveat{color:var(--cz-text-body)!important}
/* A white page heading whose dark band is now light. */
.report-head h1,.analysis h1,h1.inverse{color:var(--cz-text-inverse)}

/* ── white text that has lost its dark ground ──────────────────────────────── */
/* Turning the rails and bars to glass leaves behind every rule that painted text white for a
   surface that is no longer there. A sweep of all sixteen screens found exactly four, and
   three of them measured 1.00:1, which is white on white: invisible, not merely faint.
   Each is named rather than caught by a blanket rule, because a blanket "make white text ink"
   would also repaint the labels on the ink buttons, which are correct as they are. */
.side .user b{color:var(--cz-text-heading)!important}
/* the two links under the signed-in name, and the option label inside the queue select */
.side .user a{color:var(--cz-text-body)!important;text-decoration:underline}
.side .user a:hover{color:var(--cz-text-heading)!important}
select option{color:var(--cz-text-heading)}
/* The selected count in the dialer sits on its own pale tint, which takes the body tone from
   4.98:1 on white down to 4.21:1. On a tinted tile the label is the heading colour. */
.dial-count.on,.dial-count.on *{color:var(--cz-text-heading)!important}
.side .nav button i{color:var(--cz-text-body)!important}
.side .nav button.on i{color:var(--cz-text-inverse)!important}
/* the sandbox's lane switch and its Redraw action, both white on what is now white */
.rail .lane,.rail .lane.on{color:var(--cz-text-heading)!important}
.rail .lane.on{background:var(--cz-action-primary)!important;color:var(--cz-text-inverse)!important}
.btn.go{background:var(--cz-action-primary)!important;border-color:var(--cz-action-primary)!important;
  color:var(--cz-text-inverse)!important}
/* the deck's step numerals, a hairline grey on white at 1.34:1 */
.step .n{color:var(--cz-text-body)!important}

/* ── type ──────────────────────────────────────────────────────────────────── */
body{font-family:var(--cz-font-body);color:var(--cz-text-body)}
/* Space Grotesk, not the serif. CHIMZEE_CSS_IMPLEMENTATION.md is explicit: Cormorant is for
   display headings, and "For operational/admin headings, prefer Space Grotesk". Everything
   this file touches is an operational screen. */
h1,h2,h3,h4{font-family:var(--cz-font-body);color:var(--cz-text-heading);
font-weight:var(--cz-weight-semibold);letter-spacing:-.025em}

/* Chris, 2026-08-16, on the analysis template after it already had the palette, the corners
   and the field: "This is still not correct." He was right and it was never geometry. The page
   was still SPEAKING in the wrong voice: Inter for every heading and label, and a system
   monospace for things that are not data at all, so "STRENGTHS TO BUILD ON" and "OUT OF 100"
   came out looking like terminal output while chimzee.com says the same kind of thing in
   Space Grotesk.
   A page can carry every token and still read as a different product, because a typeface is
   not a colour. So the two brand faces are asserted over the whole element tree, not just
   inherited from body, since a page that names Inter on its own h2 beats inheritance every
   time. Icon carriers are left alone: a ligature icon font renders as the word "menu" if you
   take its family away. */
body *:not(i):not([class*=icon]):not([class*=Icon]):not([class*=material]):not(svg):not(svg *){
  font-family:var(--cz-font-body)}
/* Geist Mono goes back only where the system puts it: data and technical labels. */
.mono,code,kbd,samp,pre,.num,.figure,.data,.metric-value,tt,var{
  font-family:var(--cz-font-data)!important}
/* And the serif stays for display headings that ask for it by name. */
.cz-display,.display,.serif,[class*=display-]{font-family:var(--cz-font-display)!important}

/* ── surfaces ──────────────────────────────────────────────────────────────── */
/* Dialog glass, not card glass. Every one of these is something read down a column, which is
   what the system reserves the more opaque level for, and it is also what keeps text on them
   above 4.5:1 once the layers behind have composited. */
.card,.panel,.box,.tbl,.list,.tile,.cal,.well,.sheet,.block,.section-card,.nothing,
table{
  background-color:var(--gl-tint);
  background-image:var(--gl-sheen);
  border-color:var(--gl-line);
  border-radius:var(--cz-radius-md);
  box-shadow:var(--gl-shadow);
}
/* Alternating the tint is what stops a column of cards reading as one slab; the homepage
   alternates sky and peach down its own run of them. */
.card:nth-of-type(even),.panel:nth-of-type(even),.tile:nth-of-type(even),
.fcard:nth-of-type(even),.jcard:nth-of-type(even),.bcard:nth-of-type(even){
  background-color:var(--gl-tint-warm)}
/* A table's own corners cannot round while its cells are square, and overflow:hidden on a
   table breaks sticky headers, so the radius goes on the wrapper where there is one. */
.tbl,.table-wrap,.scroller{overflow:hidden}
th,td{border-color:var(--cz-border-subtle)}

/* ── the report pages ──────────────────────────────────────────────────────── */
/* The analysis templates are the pages a prospect is actually shown, and they are framed
   inside the dashboard at /trace/admin?open=analysis-template, which is where Chris found
   them: "parts of the CRM still have the old square box styling."
   They were built in their own language, a measurement report drawn as a hard 1px grid, and
   they name their own containers, so a class list written for the applications never touched
   them. These are those names, taken off the page rather than guessed. */
.fcard,.jcard,.bcard,.strength,.portrait,.portrait__intro,.portrait__fact,.bfacts,
.journey,.jstep,.gauges,.bcards,.panel-card,.metric,.finding,.summary-card{
  border-radius:var(--cz-radius-md);
  border-color:var(--cz-border-subtle)}
/* The outer boxes carry the lift; the cells inside a grid do not, or the page turns into a
   heap of floating tiles. */
.fcard,.jcard,.bcard,.portrait,.journey,.summary-card{
  background-color:var(--gl-tint);
  background-image:var(--gl-sheen);
  border-color:var(--gl-line);
  box-shadow:var(--gl-shadow)}

/* ── the rest of the platform's containers ─────────────────────────────────── */
/* Taken from brand_audit.py, which walks all 83 surfaces and reports every drawn box still
   carrying a square corner. Naming them beats guessing at them, and it beats a blanket rule on
   div, which would round the page bands and the table cells too.
   Rows are the interesting case: a row inside a rounded, clipping container is correctly
   square, and the audit already excludes those. These are the ones that stand alone. */
.row,.rows,.qa,.projection,.icard,.icards,.cvrow,.compare,.evr,.step,.bs,.stat,.kpi,
.proofcard,.why,.wlrow,.biz,.ver,.ctbl,.crow,.job,.ownercode,.user,.mapwrap,.rbot,
.g,.grid,.grow,.sktbl,.callbox,.kpis,.dial-counts,.dial-count,.event,.ergrid,.ertbl,
.topic,.top{
  border-radius:var(--cz-radius-md);border-color:var(--cz-border-subtle)}
/* The ones that are a card in their own right get the glass and the lift. The rest keep their
   own background, because a row inside a list is not a floating card. */
.icard,.proofcard,.qa,.projection,.compare,.biz,.job,.mapwrap{
  /* Was the opaque glass plus a blur. On the website builder these are .biz cards, one per
     business, and one of them is 1080x2833: blurring ten thousand pixels of backdrop on every
     scroll frame took that page to 13fps. Same tint and sheen as every other card, and the
     blur stays with the surfaces that actually float. */
  background-color:var(--gl-tint);
  background-image:var(--gl-sheen);
  border-color:var(--gl-line);
  box-shadow:var(--gl-shadow)}
/* The map is a third-party canvas with its own furniture; round the frame, leave the tiles. */
.leaflet-container{border-radius:var(--cz-radius-md);overflow:hidden}

/* The long tail, from the fourth pass of brand_audit.py. Every one of these is a drawn box
   with a square corner on a screen somebody still opens: the deck, the projects board, the
   people admin, the builds list, the five-act flow, the map, the ideas board. Named rather
   than caught by a rule on div, because a rule on div rounds the page bands too. */
.aimetrics,.svc-list,.revs,.rev,.form,.side-card,.callout,.gfoot,.mbtn,.frame,.gate-out,
.stage,.pcards,.ev,.flow,.gate,.honest,.sup,.suprow,.sec2,.secc,.proj,.pbody,.col,
.rail-meta,.upeople,.urow,.rolekey,.uform,.bnums,.logic,.costs,.cost,
.street,.yours,.unlocks{
  border-radius:var(--cz-radius-md);border-color:var(--cz-border-subtle)}

/* Round two of the loop, each from brand_audit.py naming the element and the two colours.

   .rail-group is a caption sitting ON the ink rail, so it needs a light tone, not a darker
   one: at rgb(142,151,163) on rgb(38,63,87) it measures 3.68:1, and every instinct to fix a
   grey by darkening it makes a grey on a dark surface worse. */
.rail-group{color:var(--cz-color-line)!important}
/* The ideas board counts sit on a chip filled with the hairline colour, which is a background
   the body tone was never meant for. */
.icount b,.icount span,.icount em{color:var(--cz-text-heading)!important}
/* A selected chip is filled with the ink, so everything written on it has to invert. The
   drafts index had its label at ink on ink, which measures 1.00:1: not faint, absent. */
.mbtn.on,.mbtn.on *{color:var(--cz-text-inverse)!important}

/* ── the last square containers ────────────────────────────────────────────── */
.audit,.ask,.askrow,.asknum,.risks,.unlock,.aiwhere,.aih,.steps,.ag,.icount,.figwrap,
.ec,.cttable,.vd,.risk,.safe,.row,.legend,.add,.rate,.trow,.aiwatch{
  border-radius:var(--cz-radius-md);border-color:var(--cz-border-subtle)}

/* Round five, each one named by the audit rather than guessed.

   A selected row was being given white text without being given the ink behind it, because
   these rails write their nav as a bare <button> under <nav> and only the .rail-nav form got
   the background. White on white is 1.00:1. Same for the tab strips. */
.rail button.on,.rail button.active,.mtabs button.on,.tabs button.on,.mtabs .on{
  background:var(--cz-action-primary)!important;color:var(--cz-text-inverse)!important}
.rail button.on *,.mtabs button.on *{color:var(--cz-text-inverse)!important}
/* The numeral in front of a rail label, which is the same grey the captions were. */
.rail .num,.rail span.num{color:var(--cz-text-body)!important}

/* Bare divs used as cards. They carry no class of their own, so they are reached through the
   grid that holds them: the builds list and the email report grid. */
.logic>div,.ergrid>div,.icards>div,.bcards>div,.aiwhere>div,.gauges>div,.grid-2>div,
.impact-grid>div,.stat-grid>div,.card-grid>div,
.strength>div,.me>td,.strengths>div,.aimetrics>div,.ag>div,.rolekey>div{
  border-radius:var(--cz-radius-md);border-color:var(--cz-border-subtle)}

/* Two more accents that read as body copy. --cz-color-warning is 4.2:1 on the peach field, so
   the demo's kicker and its buttons sat just under; the analysis scores likewise. */
.kick,.kick.rise,.demo .btn,.btn.glass,.num,.score,.grade{
  color:color-mix(in srgb, var(--cz-color-warning) 55%, var(--cz-color-ink))}
.vd{color:var(--cz-text-body)!important}
.rail{border-radius:var(--cz-radius-md)}

/* Round six. Five of these are the same mistake in five places, and it is mine: a rule that
   says "text on this platform is ink" meeting a surface that is still dark. The ink bands that
   remain are deliberate (a selected row, a hero strip, a report's title bar), so what they need
   is the inverse, and it has to be declared AFTER the ink rules or it loses to them. */
.rail button.on .num,.rail button.active .num,.rail button.on span,.rail button.active span{
  color:var(--cz-text-inverse)!important}
.heroin,.heroin *{color:var(--cz-text-inverse)!important}
/* The demo's own header is a dark translucent bar it draws itself, and the tag inside it was
   getting the platform's body tone: dark on near black, 2.95:1. The last one of these. */
header[style*="rgba(10"] .tag,.demo-header .tag,header .tag{color:var(--cz-text-inverse)}
/* A pale green notice band is not dark, but it is tinted enough to put the body tone under. */
.banner-title,.banner-title *{color:var(--cz-text-heading)!important}
/* The demo writes its accent into an <em> inside the headline, and its primary button had no
   fill at all: white text directly on the peach field, which is 4.34:1 and only that high
   because the field is not quite white. */
.title em,h1 em,.stage h1 em{color:color-mix(in srgb, var(--cz-color-warning) 55%, var(--cz-color-ink))}
.stage .btn{background:var(--cz-action-primary);border-color:var(--cz-action-primary);
  color:var(--cz-text-inverse)}
/* The two score blocks on the audit report: the right colours, on their own pale tints, which
   costs about half a point of contrast and put them under the floor. */
.score-big,.score-big *{color:color-mix(in srgb, currentColor 62%, var(--cz-color-ink))}
.score-big.red,.score-big.red *{color:color-mix(in srgb, var(--cz-color-critical) 62%, var(--cz-color-ink))!important}
.score-big.yellow,.score-big.yellow *{color:color-mix(in srgb, var(--cz-color-warning) 55%, var(--cz-color-ink))!important}
.score-big.green,.score-big.green *{color:color-mix(in srgb, var(--cz-color-positive) 62%, var(--cz-color-ink))!important}


/* Everything that gets a corner gets the glass behind it. The two lists were split into
   "round this" and "make this glass", and the difference was invisible to me and obvious to
   Chris: a rounded card with a solid fill is not liquid glass, it is a white box with soft
   corners. BRAND.md's own words: "cards do not become opaque color blocks". */
.row,.rows,.qa,.projection,.icard,.icards,.cvrow,.compare,.evr,.step,.bs,.stat,.kpi,
.proofcard,.why,.wlrow,.biz,.ver,.ctbl,.crow,.job,.ownercode,.user,.mapwrap,.rbot,
.g,.grid,.grow,.sktbl,.callbox,.kpis,.dial-counts,.dial-count,.event,.ergrid,.ertbl,
.topic,.aimetrics,.svc-list,.revs,.rev,.form,.side-card,.callout,.gfoot,.mbtn,
.pcards,.ev,.honest,.sup,.suprow,.sec2,.secc,.proj,.pbody,
.rail-meta,.upeople,.urow,.rolekey,.uform,.bnums,.logic,.costs,.cost,.street,.yours,
.unlocks,.ec,.cttable,.vd,.risk,.safe,.legend,.add,.rate,.trow,.aiwatch,.fcard,.jcard,
.bcard,.strength,.portrait,.portrait__intro,.portrait__fact,.bfacts,.journey,.jstep,
.gauges,.bcards,.panel-card,.metric,.finding,.summary-card,.idxc,.package,.section,.col,
.audit,.askrow,.lanes,.unlock,.aiwhere,.steps,.ag,.flow-rail,.banner,.icount,
.figwrap,.vcard,.score-big,.frame,.orch-col,.main>.top,.strength>div,.me>td,.strengths>div,.aimetrics>div,
.ag>div,.rolekey>div,.logic>div,.ergrid>div,.icards>div,.bcards>div,.aiwhere>div,
.gauges>div,.grid-2>div,.impact-grid>div,.stat-grid>div,.card-grid>div,
.leaflet-container{
  /* This is the rule that decides how the whole platform feels, because it names nearly every
     container on it. It used to paint --cz-glass-dialog, white at 90%, which is not glass: it
     is paint with a blur behind it that nothing can be seen through. Chris, 2026-08-17: "I'm
     not getting that full glass feeling ... I'm not getting that transparency and that depth."
     The measured recipe from the live homepage instead, so a card here is the same object a
     .coda-card is there. */
  background-color:var(--gl-tint);
  background-image:var(--gl-sheen);
  border-color:var(--gl-line);
  box-shadow:var(--gl-shadow)}
/* A map's own tiles must stay opaque or the map disappears; only its frame is glass. */
.leaflet-container .leaflet-tile-pane,.leaflet-container img{backdrop-filter:none}

/* One level of glass, not two, and generated rather than listed by hand.
   The blanket rule above names every container on the platform, outer and inner alike, so the
   moment it painted real glass a row inside a card became its own floating card. The website
   builder was four deep: a business card holding a version card holding a "sections in order"
   card holding a chip.
   Three earlier attempts are worth recording. The first put both halves in :where(), which is
   zero specificity, so it never beat .jstep. The second was a hand-written split of which
   classes are outer and which are inner, and that was wrong within the hour, because it is not
   a property of a class: .card is outer when it holds a .row and inner when it sits in a .panel.
   The third wrote one selector per class and came to 181KB, which is a page-weight problem
   answering a nesting problem.
   So: the ancestor list sits in :where() (zero weight) and the descendant list in :is(), which
   takes the weight of its most specific argument, one class. The whole thing is therefore
   exactly as specific as the blanket rule and later in the file, which is what wins, in one
   rule. Both lists are derived from that rule's own selector so they cannot drift from it, and
   the descendant list carries the .logic>div child forms too: those style classless children,
   a class-based descendant selector cannot reach them, and they were still lifting 60 elements
   on the builder after the class list alone was fixed. */
:where(.add,.ag,.aimetrics,.aiwatch,.aiwhere,.askrow,.audit,.banner,.bcard,.bcards,.bfacts,.biz,.bnums,.bs,.callbox,.callout,.card-grid,.col,.compare,.cost,.costs,.crow,.ctbl,.cttable,.cvrow,.dial-count,.dial-counts,.ec,.ergrid,.ertbl,.ev,.event,.evr,.fcard,.figwrap,.finding,.flow-rail,.form,.frame,.g,.gauges,.gfoot,.grid,.grid-2,.grow,.honest,.icard,.icards,.icount,.idxc,.impact-grid,.jcard,.job,.journey,.jstep,.kpi,.kpis,.lanes,.leaflet-container,.legend,.logic,.main,.mapwrap,.mbtn,.me,.metric,.orch-col,.ownercode,.package,.panel-card,.pbody,.pcards,.portrait,.portrait__fact,.portrait__intro,.proj,.projection,.proofcard,.qa,.rail-meta,.rate,.rbot,.rev,.revs,.risk,.rolekey,.row,.rows,.safe,.score-big,.sec2,.secc,.section,.side-card,.sktbl,.stat,.stat-grid,.step,.steps,.street,.strength,.strengths,.summary-card,.sup,.suprow,.svc-list,.top,.topic,.trow,.uform,.unlock,.unlocks,.upeople,.urow,.user,.vcard,.vd,.ver,.why,.wlrow,.yours) :is(.add,.ag,.aimetrics,.aiwatch,.aiwhere,.askrow,.audit,.banner,.bcard,.bcards,.bfacts,.biz,.bnums,.bs,.callbox,.callout,.card-grid,.col,.compare,.cost,.costs,.crow,.ctbl,.cttable,.cvrow,.dial-count,.dial-counts,.ec,.ergrid,.ertbl,.ev,.event,.evr,.fcard,.figwrap,.finding,.flow-rail,.form,.frame,.g,.gauges,.gfoot,.grid,.grid-2,.grow,.honest,.icard,.icards,.icount,.idxc,.impact-grid,.jcard,.job,.journey,.jstep,.kpi,.kpis,.lanes,.leaflet-container,.legend,.logic,.main,.mapwrap,.mbtn,.me,.metric,.orch-col,.ownercode,.package,.panel-card,.pbody,.pcards,.portrait,.portrait__fact,.portrait__intro,.proj,.projection,.proofcard,.qa,.rail-meta,.rate,.rbot,.rev,.revs,.risk,.rolekey,.row,.rows,.safe,.score-big,.sec2,.secc,.section,.side-card,.sktbl,.stat,.stat-grid,.step,.steps,.street,.strength,.strengths,.summary-card,.sup,.suprow,.svc-list,.top,.topic,.trow,.uform,.unlock,.unlocks,.upeople,.urow,.user,.vcard,.vd,.ver,.why,.wlrow,.yours,.ag>div,.aimetrics>div,.aiwhere>div,.bcards>div,.card-grid>div,.ergrid>div,.gauges>div,.grid-2>div,.icards>div,.impact-grid>div,.logic>div,.main>.top,.me>td,.rolekey>div,.stat-grid>div,.strength>div,.strengths>div){
  background-image:none!important;
  -webkit-backdrop-filter:none!important;backdrop-filter:none!important;
  box-shadow:none!important;
  border-radius:var(--cz-radius-sm)}

/* And the lift itself is a wide, soft, slightly cool drop taken off a .coda-card, which on
   chimzee.com carries perhaps a dozen elements on a long page. Spread across every container
   on a dense admin screen the same shadow stacks into a grey-green wash over the whole page,
   which is not depth, it is dirt. Outer containers keep the full drop; the ordinary ones take
   the system's own smaller one. */
.tbl,.list,.cal,.nothing,table,.row,.rows,.trow,.crow,.stat,.kpi,.kpis,.metric,.finding,
.step,.steps,.legend,.rate,.add,.topic,.event,.qa,.bs,.job,.cost,.costs,.grow,.col,.g{
  box-shadow:var(--cz-shadow-1)}


/* Nothing inside a deliberately ink band becomes glass. .rate sits in .heroin, which is the
   one dark strip on the five act flow, and glassing the child turned it light under white
   text: 1.19:1 for the rating, the stars and the sentence beside them. */
.heroin *{background:transparent!important;-webkit-backdrop-filter:none!important;
backdrop-filter:none!important;box-shadow:none!important}

/* ── controls ──────────────────────────────────────────────────────────────── */
/* NOT a blanket rule on `button`, and this is the correction to v1.0.0. These applications use
   <button> for things that are not buttons: a KPI segment 250x96, the dialer's count tiles
   190x73 sitting edge to edge in a row, a whole table row at 576x86, a calendar event. A
   999px radius on those draws half moons, and where they sit next to each other the curves
   read as overlapping crescents. Chris, 2026-08-15: "the CRM has issues (half moon overlap on
   tabs on the same row)."
   Softening the radius instead of removing it was not enough: the dialer's five counts sit
   edge to edge, so a 12px corner on each one notches every join and the row reads as a strip
   of scallops. A segmented row wants square inner corners and a rounded container, and a
   stylesheet that does not know which buttons are in a row cannot tell the difference.
   So the radius of a plain <button> is left exactly as each application drew it. The pill is
   reserved for the classes that actually mean "this is an action", and nothing else here
   decides the shape of a control it cannot see. */
.btn,.pill,.chip,.tag,.tick,.cz-button-primary,.cz-button-secondary{
border-radius:var(--cz-radius-pill)}
/* The system's primary action is the ink, not a colour. Chris had a green Continue on /crm2
   because that app's accent variable painted it, and a green primary is off the system. */
.btn.primary,.btn-primary,button.primary{background:var(--cz-action-primary);
border-color:var(--cz-action-primary);color:var(--cz-text-inverse)}
input,select,textarea{border-radius:var(--cz-radius-sm);
border-color:var(--cz-border-control);background:var(--cz-glass-control);
font-family:var(--cz-font-body)}
:focus-visible{outline:3px solid color-mix(in srgb, var(--cz-focus-ring) 38%, transparent);
outline-offset:3px}


/* The last three, all the same shape of mistake: a control marked selected gets white text
   from its own stylesheet and its dark fill from a rule that no longer applies, so the label
   goes white on white. .tab.on and a bare .btn on the price book were the two the audit could
   still see at 1.3:1. */
.tab.on,.tab.active,.pricebook .btn,.sheet .btn{
  background:var(--cz-action-primary)!important;color:var(--cz-text-inverse)!important;
  border-color:var(--cz-action-primary)!important}
/* A <select> and a panel on the five-act flow are still painted with the pre-system near
   black. They have no class between them and the page, so they are reached by what they are. */
.flow select,.flow>div[style],select[style]{background:var(--cz-action-primary);
  color:var(--cz-text-inverse);border-radius:var(--cz-radius-sm)}


/* ── segmented controls and narrow screens ─────────────────────────────────── */
/* A segmented switch is one rounded container with square segments inside it. Rounding the
   segments themselves made fifteen half moons at 390px, where they are short enough for an
   18px corner to pass half their height; rounding the container gives the same look at every
   width and cannot scallop. */
.lanes,.segmented,.tabs{border-radius:var(--cz-radius-md);overflow:hidden}
.lanes>.lane,.segmented>*,.tabs>button{border-radius:0}
.upeople>div,.urow>div{border-radius:var(--cz-radius-md);border-color:var(--cz-border-subtle)}

/* A table wider than a phone made the whole page scroll sideways, which the gate counts as a
   defect and a person experiences as the page sliding under their thumb. The table scrolls
   inside its own box instead. Layout, which this file otherwise leaves alone, and it is here
   because sideways scroll is not a style opinion. */
@media(max-width:560px){
  table{display:block;max-width:100%;overflow-x:auto;-webkit-overflow-scrolling:touch}
  .tbl,.table-wrap,.scroller,.tw,.xscroll{max-width:100%;overflow-x:auto;min-width:0}
  /* min-width:0 is the half that actually does it. A flex or grid child refuses to shrink
     below its content by default, so max-width:100% on a scroller inside one is ignored and
     the wrapper grows to its table's 640px. This is the rule that stops the page moving. */
  main,section,article,.page,.wrap,.main,.inner,.col{min-width:0}
  /* A table with its own min-width is meant to scroll inside its wrapper, so the wrapper is
     what needs capping. Capping the table instead does nothing: min-width beats max-width,
     which is why /beta/email-plan still pushed the page 7px sideways at 390. */
  .tw>table,.tbl>table,.table-wrap>table,.scroller>table{max-width:none}
  /* This used to make every tr a card: an 18px corner, 90% white and a blur. It was written
     for rows that stack on a phone, but the rule six lines above makes these tables SCROLL
     instead, so the rows never stack: they stay 42px tall and full width, and an 18px corner
     on a 42px row curves through the text in the first and last cells. That is the same fault
     Chris found on .bfacts, and check_page now has a `corner` check that catches it.
     A scrolling row needs separating, not floating. A hairline does that. */
  tr{border-bottom:1px solid var(--cz-border-subtle)}
  tr:last-child{border-bottom:0}
  /* Three items in two columns leaves a hole in the last row, and an empty grid cell reads as
     a card that failed to draw. One column on a phone, which is what three items want anyway.
     Setting grid-template-columns on something that is not a grid is simply ignored. */
  .row,.cols,.trio,.threeup{grid-template-columns:1fr}
}
/* Two screens still slid sideways at their own widths: a wide sandbox stage and a contacts
   table at tablet size. Both scroll inside themselves now rather than dragging the page. */
@media(max-width:900px){
  .stage,.sandbox,.cttable,.ctable,.wide{max-width:100%;overflow-x:auto}
  table{max-width:100%}
}


/* ── one identity, everywhere ───────────────────────────────────────────────
   Chris, 2026-08-16: "make sure the proper logo and text is consistent across the platform."
   Six rails and mastheads drew the mark as an <img> with the word typed beside it in whatever
   face that screen used. The guide is explicit that the lettering is artwork and not a
   typeable font, so each of them shows the lockup instead.
   font-size:0 on the wrapper is what removes the typed word without removing the sub-label
   beside it ("Operations workspace", "CRM2 test"), which is a real piece of information and
   not part of the identity. The <small> gets its size back on the next line. */
/* Scoped to Chimzee's own chrome. A bare `.brand img` also matches a CUSTOMER's logo on a
   site we rebuilt for them, and on the Central Comfort preview this rule was rewriting their
   mark to ours; it only failed to land because the URL happened to 404. A client's website
   must never wear our identity, so every selector here now requires a Chimzee container.
   The URL is relative to this stylesheet for the same reason the @font-face URLs are: the
   file is served at /brand/ on chimzee.com and /chimzee/brand/ on the drafts host, and an
   absolute /chimzee-lockup.svg only ever resolved on the first of those. It went unnoticed
   because no page had an <img> in one of these containers until the analysis template did. */
.side .brand img,.rail-brand img,.czbar .logo img,.bar .logo img,
.cz-chrome .brand img,.workspace .brand img,.mast img,.who img{
  content:url(logo/chimzee-lockup.svg);height:26px;width:auto;max-width:100%;flex:0 0 auto}
.side .brand>span,.rail-brand>span,.cz-chrome .brand>span,.mast>b,
.who>.chzbrand>span,.czbar .logo>div,.bar .logo>div{font-size:0!important}
.side .brand>span>small,.rail-brand>span>small,.cz-chrome .brand>div>small,
.czbar .logo .sub,.bar .logo .sub{
  font-size:11.5px!important;display:block;
  color:var(--cz-text-body);font-weight:400;letter-spacing:0}


/* ── found by the subpage review, 2026-08-16 ────────────────────────────────
   Each of these was measured, not guessed, and each is content a person cannot reach. */

/* The sandbox's lane filter is a 25px box with overflow hidden around a wrapping row that
   needs 80px, so the first row of buttons is sliced through the middle and the second row is
   painted under the heading beneath it. A row that wraps has to be allowed its height. */
/* Scoped to the sandbox's rail. Releasing every .lanes also released the segmented switch on
   the projects board, which needs its container to clip so its square segments read as one
   control. Two different widgets, one class name, again. */
.rail .lanes{height:auto!important;overflow:visible!important;
  border-radius:var(--cz-radius-md);border-color:var(--cz-border-subtle)}
/* and once it is visible, nothing clips the chips any more. The rule above squares the
   children of a .lanes on purpose, because a segmented control is a rounded container
   clipping square segments into one shape. This one is not that: it wraps, it is released,
   and its chips sit apart with a gap, so square corners here are just square corners in a
   place where everything else is a pill. They carry their own radius instead. */
.rail .lanes>.lane{border-radius:var(--cz-radius-pill)}

/* 24 data tables across 12 internal screens clip between 376 and 467 pixels at phone width
   with overflow-x hidden, so the columns are not merely off screen, they are unreachable.
   The page itself does not scroll sideways, which is exactly why the sideways check passed
   while the content was being thrown away. */
@media(max-width:900px){
  .tbl,.table-wrap,.scroller,.tw,.xscroll{overflow-x:auto!important;-webkit-overflow-scrolling:touch}
  .tabs,.mtabs,.adtabs{overflow-x:auto!important;flex-wrap:nowrap;-webkit-overflow-scrolling:touch}
}

/* The dial in the analysis reports draws its biggest number in Inter and its labels in
   whatever monospace the machine has, so the three report versions disagree with each other
   and none of them is on the system. SVG text takes fill and font from CSS like anything else. */
svg text,.dial text{font-family:var(--cz-font-body)}
svg text.mk,svg text.end,.dial text.mk,.dial text.end{font-family:var(--cz-font-data)}

/* One heading in Georgia on the email preview, one button in Arial on the CRM. */
.email-preview h2,.preview h2{font-family:var(--cz-font-body)!important}
button,input,select,textarea{font-family:var(--cz-font-body)}

/* Two display headings left with a one-word orphan on the last line. `pretty` is the setting
   that fixes an orphan without shortening the first line, which is the fault that put a
   headline on two lines with 500px of space beside it elsewhere on this site. */
#a2 .w h1,.rows .row h2{text-wrap:pretty}

/* ── data ──────────────────────────────────────────────────────────────────── */
/* The one job the system gives Geist Mono. */
.mono,code,kbd,samp,pre,.num,.figure{font-family:var(--cz-font-data)}

@media(prefers-reduced-motion:reduce){*{transition:none!important;animation:none!important}}


/* ── where the blur is allowed ──────────────────────────────────────────────── */
/* Chris, 2026-08-17: "I'm also getting some lag time." Measured: the analysis template was
   scrolling at 6fps with 62 backdrop-filtered elements on it, and the admin at 28fps with 20.
   Each backdrop-filter is its own compositing pass that has to re-read what is behind it, and
   the rules above had put one on essentially every container on the page.

   A blur only shows when something moving or strongly coloured passes behind it. Over this
   ground, which is near-white with a faint constellation, a card's tint and sheen are doing
   all the visible work and the blur costs a frame for nothing. So it is kept for the things
   that genuinely float over other content and nothing else: the bar, the rails, dialogs and
   overlays. Everything else keeps the same tint, sheen, hairline and lift, and looks the same
   sitting still. */
.czbar,.bar,.side,.rail,.modal,.dialog,.overlay,.sheet-open,.drawer,.popover,.menu-pop,
dialog,[role=dialog],#gate .box{
  -webkit-backdrop-filter:var(--gl-blur);backdrop-filter:var(--gl-blur)}

/* A dialog is the one surface the system reserves the opaque glass level for, and it is right:
   a modal sits ON TOP of a page that is still there, so at card transparency you read both at
   once. On the demo's passcode gate that put its own sentence over the page's copy at every
   width, 62px of overlap on desktop. Card glass is for something lying ON the page; dialog
   glass is for something covering it. */
.modal,.dialog,.overlay,.drawer,.popover,.menu-pop,dialog,[role=dialog],#gate .box{
  background-color:var(--cz-glass-dialog);
  background-image:var(--gl-sheen)}


/* ── grids whose background IS the hairline ─────────────────────────────────── */
/* Chris, 2026-08-17, on the analysis template: "Everything's too squished ... It's still
   sitting within the cards."

   The report pages draw a run of cells as a grid with a 1px gap over a rule-coloured
   background, so the gaps read as hairlines and the whole block is one object with divisions
   in it. .portrait even carries margin:-20px to cancel its panel's padding and run edge to
   edge. The rules above painted a tint, a 26px corner and a lift onto both the grid AND each
   of its cells, which broke the technique twice over: the hairline colour was replaced, so the
   divisions vanished, and every cell became a floating card inside the card that already held
   it. That nesting is what he is seeing.

   These six grids keep their own background and square corners, and their cells stay flat.
   They are named rather than detected because "a grid with a 1px gap" is a thing CSS cannot
   ask about, and guessing here would repaint something else by accident. */
.portrait,.strength,.gauges,.journey,.bcards,.compare{
  background:var(--rule, var(--cz-color-line))!important;
  background-image:none!important;
  border-radius:0!important;
  box-shadow:none!important;
  -webkit-backdrop-filter:none!important;backdrop-filter:none!important;
  border:0!important}
.portrait>*,.strength>*,.gauges>*,.journey>*,.bcards>*,.compare>*{
  background-color:var(--panel, var(--cz-color-white))!important;
  background-image:none!important;
  border-radius:0!important;
  box-shadow:none!important;
  -webkit-backdrop-filter:none!important;backdrop-filter:none!important}
/* The panel that holds them still clips to its own corner, so the block's outer edge is round
   even though every cell inside it is square. */
.panel,.pb{overflow:hidden}


/* ── short data lists are not cards ─────────────────────────────────────────── */
/* Chris, 2026-08-17: "Yes this has overlap issues" on the built-on and search-and-AI blocks.
   .bfacts is a three-row fact list 68px tall. It was named among the report page containers, so
   it was getting --cz-radius-lg (26px) plus the glass and the lift. On a box that short a 26px
   corner is a quarter of its height, and the curve cuts through the text on the first and last
   rows: the value sits on the arc rather than beside its label. A rounded box needs to be tall
   enough for its own corner, and this one never was.
   Same for the other short lists in the report. They keep their hairline and their spacing. */
.bfacts,.bf,.jstep,.metric,.finding,.gauges>div>*,.strength>div>*{
  background:none!important;background-image:none!important;
  border-radius:0!important;
  box-shadow:none!important;
  -webkit-backdrop-filter:none!important;backdrop-filter:none!important}
