
:root{
  --bg:#0a0c0f; --fg:#eef1f4; --mut:#8d97a4; --line:#1d2229;
  --acc:#3fd9c4; --acc2:#7af0dd; --amber:#e8a33d; --deep:#06554b; --code:#12161b;
  --on-acc-hover:#0a0c0f;
}
@media(prefers-color-scheme:light){:root{
  --bg:#fcfcfb; --fg:#0e1116; --mut:#5b6572; --line:#e3e6ea;
  --acc:#00786a; --acc2:#00a892; --amber:#9a6700; --deep:#00695c; --code:#f1f3f4;
  --on-acc-hover:#ffffff;
}}
*{box-sizing:border-box}
[hidden]{display:none!important}
html{scroll-behavior:smooth}
body{margin:0;background:var(--bg);color:var(--fg);overflow-x:hidden;
  font:16px/1.6 ui-sans-serif,system-ui,-apple-system,"Segoe UI",Roboto,sans-serif;
  -webkit-font-smoothing:antialiased}
/* The one hero effect. The canvas belongs to the screenshot figure: it covers
   the picture and a 2.2rem halo around it, never the text column, and it is
   not fixed, so nothing paints behind copy as the page scrolls. With reduced
   motion or data saver the script never starts and the CSS glow below is the
   whole effect. */
.hero-shot{position:relative;margin:0;min-width:0}
.shot-stage{position:relative}
.shot-stage::before{content:"";position:absolute;inset:-2.2rem;z-index:0;border-radius:28px;
  background:radial-gradient(closest-side,color-mix(in srgb,var(--acc) 20%,transparent),transparent)}
#canvasui-fx{position:absolute;left:-2.2rem;top:-2.2rem;width:calc(100% + 4.4rem);height:calc(100% + 4.4rem);
  z-index:2;pointer-events:none;display:block;opacity:0;transition:opacity .6s ease}
#canvasui-fx.is-live{opacity:1}
.shot-frame{position:relative;z-index:1;border:1px solid var(--line);border-radius:16px;overflow:hidden;background:#05070a}
.shot img,.shot video{display:block;width:100%;height:auto}
.shot figcaption{color:var(--mut);font-size:.82rem;margin:.7rem 0 0}
.hero-shot figcaption{margin-top:2.4rem}
header,main,footer{position:relative;z-index:1}
header{z-index:5}
/* The skip link is the first thing a keyboard user reaches: its own
   contrast has to pass, so it uses the page ink on the page ground. */
.skip-link{position:absolute;left:1rem;top:-4rem;z-index:100;background:var(--fg);color:var(--bg);padding:.6rem 1.1rem;font-weight:700;border-radius:4px;outline:2px solid var(--acc)}
.skip-link:focus{top:1rem}

/* chrome */
/* The header shares the hero's container (78rem, 1.6rem gutter) so the
   wordmark starts at the same x as the content beneath it. It used to be
   full-bleed, which put the mark hard against the viewport edge on a wide
   screen while everything below was centred. */
header{display:flex;justify-content:space-between;align-items:center;
  padding:1.1rem 1.6rem;gap:1rem;max-width:76rem;margin:0 auto}
.brand{font-weight:650;letter-spacing:-.02em;text-decoration:none;color:var(--fg);white-space:nowrap;flex:none;
  display:inline-flex;align-items:center;gap:.45rem;font-size:1.02rem}
.mark{color:var(--acc);font-size:1.1em}
nav{display:flex;align-items:center;gap:1.1rem;
  justify-content:flex-end;min-width:0}
/* WCAG 2.5.8 wants 24px; these measured 23 — the bare line box. Audited at
   390px on a touch viewport: on a phone the nav is how a buyer reaches
   Pricing. .pill sets 44px and .agi 24px, so this only lifts the plain links.
   (Kept free of internal context: this stylesheet is served to the public.) */
nav a{display:inline-flex;align-items:center;min-height:24px}

/* NAV LINKS ARE NEVER UNDERLINED AT REST. `a{color:var(--acc)}` below sets
   no text-decoration, so the browser default underlined all eight internal
   nav links while the two cross-site links (.agi) and the CTA (.pill) set
   text-decoration:none — three link treatments in one row, with the loudest
   one on the most important links. Prose links keep their underline: in
   running text the underline is the affordance, in a nav bar position is. */
nav a{text-decoration:none;color:var(--fg);font-size:.94rem;white-space:nowrap}
nav a:hover{color:var(--acc);text-decoration:underline;text-underline-offset:6px}
nav a[aria-current="page"]{color:var(--acc);box-shadow:inset 0 -2px 0 var(--acc)}
/* One visible focus ring for every interactive thing in the header, so a
   keyboard user is never guessing. Colour alone is not a focus indicator. */
header a:focus-visible{outline:2px solid var(--acc);outline-offset:3px;border-radius:4px}
/* The same ring on every other control (buttons, footer and prose links,
   FAQ rows, form fields), not only in the header. A control keeps its own
   corner radius. */
:is(a,button,summary,input,select,textarea,[tabindex]):focus-visible{outline:2px solid var(--acc);outline-offset:3px}

/* The two sister sites are quieter than this site's own links and sit after
   them, separated by a hairline: leaving Buzz is a different kind of move
   from going to Pricing. */
.agi{color:var(--mut);text-decoration:none;font-size:.88rem;white-space:nowrap;display:inline-flex;align-items:center;min-height:24px}  /* WCAG 2.5.8: was 23px */
.agi:hover{color:var(--acc)}
.nav-sep{width:1px;height:1.1rem;background:var(--line);flex:none}
/* Language switch. Header: a compact details menu showing the current
   language in its own name; it opens with JavaScript off. Phone menu and
   footer: the same links as a plain wrapping list. */
.lang-menu{position:relative;flex:none}
.lang-menu summary{list-style:none;cursor:pointer;display:inline-flex;align-items:center;gap:.4rem;
  min-height:36px;padding:0 .75rem;border:1px solid var(--line);border-radius:99px;
  font-size:.86rem;font-weight:560;color:var(--fg);white-space:nowrap}
.lang-menu summary::-webkit-details-marker{display:none}
.lang-menu summary::after{content:"";width:.42rem;height:.42rem;border-right:1.5px solid currentColor;
  border-bottom:1.5px solid currentColor;transform:translateY(-.12rem) rotate(45deg);opacity:.7}
.lang-menu[open] summary{border-color:var(--acc)}
/* On a phone the summary shows the two-letter code: "Bahasa Indonesia" does
   not fit beside the brand and the menu button. The panel keeps full names. */
.lang-code{display:none;font:600 .78rem/1 ui-monospace,SFMono-Regular,Menlo,monospace;letter-spacing:.04em}
@media(max-width:560px){.lang-name{display:none}.lang-code{display:inline}}
.lang-menu summary:focus-visible{outline:2px solid var(--acc);outline-offset:3px}
.lang-globe{width:.9rem;height:.9rem;border:1.5px solid currentColor;border-radius:50%;opacity:.75;
  background:linear-gradient(currentColor,currentColor) center/1.5px 100% no-repeat,
    linear-gradient(currentColor,currentColor) center/100% 1.5px no-repeat}
.lang-menu-panel{position:absolute;right:0;top:calc(100% + .5rem);z-index:60;display:grid;
  grid-template-columns:repeat(2,max-content);gap:.1rem .4rem;padding:.5rem;
  background:var(--bg);border:1px solid var(--line);border-radius:12px}
.lang-menu-panel a,.lang-list a{display:flex;align-items:center;min-height:40px;padding:.3rem .7rem;
  border-radius:8px;color:var(--fg);text-decoration:none;font-size:.92rem;white-space:nowrap}
.lang-menu-panel a:hover,.lang-list a:hover{color:var(--acc);text-decoration:none}
.lang-menu-panel a[aria-current="true"],.lang-list a[aria-current="true"]{color:var(--acc);font-weight:650}
.lang-list{display:flex;flex-wrap:wrap;gap:.1rem .2rem}
.lang-list a{min-height:32px;padding:.2rem .55rem;font-size:.84rem;color:var(--mut)}
.nav-menu-panel .lang-list{margin:.5rem 0 .2rem;padding-top:.5rem;border-top:1px solid var(--line)}
.nav-menu-panel .lang-list a{min-height:40px;font-size:.92rem;color:var(--fg)}
footer .lang-list{margin-left:-.55rem;max-width:22rem}
/* Scripts the system UI font may not cover get fonts the visitor already
   has; nothing is downloaded. Thai and Devanagari need more line height,
   and no script without capitals is letter-spaced or upper-cased. */
body:lang(zh-Hans){font-family:"PingFang SC","Microsoft YaHei","Noto Sans SC","Noto Sans CJK SC",ui-sans-serif,system-ui,sans-serif}
body:lang(ja){font-family:"Hiragino Sans","Yu Gothic","Noto Sans JP","Noto Sans CJK JP",ui-sans-serif,system-ui,sans-serif;line-break:strict}
body:lang(ko){font-family:"Apple SD Gothic Neo","Malgun Gothic","Noto Sans KR","Noto Sans CJK KR",ui-sans-serif,system-ui,sans-serif}
body:lang(th){font-family:"Thonburi","Leelawadee UI","Noto Sans Thai",ui-sans-serif,system-ui,sans-serif;line-height:1.8}
body:lang(hi){font-family:"Kohinoor Devanagari","Nirmala UI","Noto Sans Devanagari",ui-sans-serif,system-ui,sans-serif;line-height:1.75}
:lang(ko) h1,:lang(ko) h2,:lang(ko) h3,:lang(ko) .btn{word-break:keep-all}
/* Japanese headings break between phrases where the browser can tell them
   apart (older browsers keep the default). The Thai headline carries its own
   break points (zero-width spaces between words), so it never splits a word. */
:lang(ja) h1,:lang(ja) h2,:lang(ja) h3{word-break:auto-phrase}
:lang(th) .tag{word-break:keep-all}
/* Katakana makes the Japanese headline long; a smaller size keeps it to
   four lines beside the screenshot. */
:lang(ja) .tag{font-size:clamp(1.75rem,3vw,2.4rem)}
:lang(zh-Hans) .tag,:lang(ja) .tag,:lang(ko) .tag{letter-spacing:0;line-height:1.25}
:lang(th) .tag,:lang(hi) .tag{letter-spacing:0;line-height:1.4}
:lang(th) h2,:lang(hi) h2,:lang(th) h3,:lang(hi) h3{letter-spacing:0;line-height:1.45}
:lang(zh-Hans) h2,:lang(ja) h2,:lang(ko) h2,:lang(zh-Hans) .brand,:lang(ja) .brand,:lang(ko) .brand{letter-spacing:0}
:is(:lang(zh-Hans),:lang(ja),:lang(ko),:lang(th),:lang(hi)) :is(.eyebrow,.kicker,.foot-col h2,.dl,.preview,.eff){
  letter-spacing:0;text-transform:none;font-family:inherit}
:is(:lang(zh-Hans),:lang(ja),:lang(ko),:lang(th),:lang(hi)) .eyebrow{font-size:.86rem}
/* The language menu's own entries are each in their own script. */
.lang-menu-panel a:lang(zh-Hans),.lang-list a:lang(zh-Hans){font-family:"PingFang SC","Microsoft YaHei","Noto Sans SC","Noto Sans CJK SC",sans-serif}
.lang-menu-panel a:lang(ja),.lang-list a:lang(ja){font-family:"Hiragino Sans","Yu Gothic","Noto Sans JP","Noto Sans CJK JP",sans-serif}
.lang-menu-panel a:lang(ko),.lang-list a:lang(ko){font-family:"Apple SD Gothic Neo","Malgun Gothic","Noto Sans KR","Noto Sans CJK KR",sans-serif}
.lang-menu-panel a:lang(th),.lang-list a:lang(th){font-family:"Thonburi","Leelawadee UI","Noto Sans Thai",sans-serif}
.lang-menu-panel a:lang(hi),.lang-list a:lang(hi){font-family:"Kohinoor Devanagari","Nirmala UI","Noto Sans Devanagari",sans-serif}
/* The phone and tablet menu: a details element, so it opens with JavaScript
   off. Hidden on wide screens, where the same links sit in the row. */
.nav-menu{display:none;position:relative}
.nav-menu summary{list-style:none;cursor:pointer;display:inline-flex;align-items:center;gap:.55rem;
  min-height:44px;padding:0 .9rem;border:1px solid var(--line);border-radius:10px;
  font-weight:600;font-size:.9rem;color:var(--fg)}
.nav-menu summary::-webkit-details-marker{display:none}
.nav-menu summary::before{content:"";width:16px;height:2px;background:currentColor;
  box-shadow:0 5px 0 currentColor,0 -5px 0 currentColor}
.nav-menu summary:focus-visible{outline:2px solid var(--acc);outline-offset:3px}
.nav-menu-panel{position:absolute;right:0;top:calc(100% + .5rem);z-index:50;min-width:15.5rem;
  display:grid;gap:.1rem;padding:.6rem;background:var(--bg);border:1px solid var(--line);border-radius:12px}
.nav-menu-panel a{display:flex;align-items:center;min-height:44px;padding:.5rem .8rem;border-radius:8px;
  color:var(--fg);text-decoration:none;font-size:1rem}
.nav-menu-panel a:hover{color:var(--acc)}
.nav-menu-panel a[aria-current="page"]{color:var(--acc)}
.nav-signin{font-weight:600}
.pill{background:var(--fg);color:var(--bg);text-decoration:none;font-weight:600;
  font-size:.88rem;padding:.62rem 1.15rem;border-radius:99px;white-space:nowrap;
  min-height:44px;display:inline-flex;align-items:center;transition:.16s}
.pill:hover{background:var(--deep);color:#fff}

/* hero: one headline (the largest thing on the page), one sentence, two
   actions and one status line beside a real screenshot. It is as tall as its
   content, so a 900px-tall window also shows the start of the next section
   instead of an empty band. */
.hero{display:grid;align-items:center;
  grid-template-columns:minmax(0,.86fr) minmax(0,1.2fr);gap:3rem;
  padding:2.2rem 0 0}
.eyebrow{font:600 .76rem/1.3 ui-monospace,SFMono-Regular,Menlo,monospace;
  letter-spacing:.1em;text-transform:uppercase;color:var(--acc);margin:0 0 1rem}
.kicker{font:500 .74rem/1 ui-monospace,SFMono-Regular,Menlo,monospace;
  letter-spacing:.22em;color:var(--mut);margin:1.1rem 0 0}
.pitch{min-width:0}
.tag{font-size:clamp(2.1rem,3.8vw,3rem);line-height:1.08;font-weight:700;
  letter-spacing:-.035em;margin:0 0 1.1rem;text-wrap:balance}
.sub{color:var(--mut);font-size:1.12rem;line-height:1.55;margin:0 0 1.7rem;max-width:34rem}
.sub strong{color:var(--acc);font-weight:650}
.sub a{color:var(--acc)}
.status-line{display:flex;gap:.6rem;align-items:baseline;color:var(--mut);font-size:.9rem;
  line-height:1.5;margin:1.5rem 0 0;max-width:34rem}
.status-dot{flex:none;width:.55rem;height:.55rem;border-radius:50%;background:var(--amber)}
.cta{display:flex;gap:.65rem;flex-wrap:wrap}
.btn{display:inline-block;padding:.72rem 1.3rem;border-radius:10px;min-height:44px;
  border:1px solid var(--line);color:var(--fg);text-decoration:none;
  font-size:.94rem;font-weight:560;transition:.16s;
  background:color-mix(in srgb,var(--bg) 55%,transparent);backdrop-filter:blur(8px)}
.btn:hover{border-color:var(--acc);color:var(--acc)}
.btn.primary{background:var(--deep);border-color:var(--deep);color:#fff}
.btn.primary:hover{background:var(--acc);border-color:var(--acc);color:var(--on-acc-hover)}

/* body */
main{max-width:74rem;margin:0 auto;padding:1rem 1.6rem 5rem}
body.home main{max-width:76rem}
/* Every section starts at the same left edge as the header and the hero;
   the prose-only sections keep a reading measure. */
#brains,#get,#register,#inquiry{max-width:46rem}
/* The canvas is a HERO effect, and #sky is position:fixed — so without an
   opaque backdrop it keeps painting behind every section as you scroll, and
   the copy ends up competing with drifting motes and hex edges. Reported
   2026-08-05 as "still doesn't look correct"; the earlier overflow fix was
   real but was not this. Everything below the hero gets solid ground. */
main,footer{background:var(--bg)}
main{position:relative;z-index:1}
/* Named landing sections only — NOT a bare `section` type selector.
   `CSS` and `DOC_CSS` are both included on every doc page
   (`_content_page` renders CSS then DOC_CSS in one style element), and WP1.3's content
   migration wraps every /support and /trust section in a bare wrapper
   `<section>` tag carrying only a data-solace-id marker, no class or id
   of its own — a bare `section{margin-top:5rem}` rule reached those too,
   opening a huge unintended gap before "Contact", "Reporting abuse",
   etc. (2026-09-15 audit finding #6, confirmed against the WP1.6
   baseline screenshot: .local/outputs/solace-web-qa/wp1-6-baseline/
   solacebuzz-com.baseline.support-opens.png). Scoped to the real
   landing sections by their own class/id instead. */
.hero,#why,#products,#brains,#get,#register,#inquiry{margin-top:5rem}
#mesh,#tour,#faq{margin-top:5rem}
.hero{margin-top:0}
/* What the team does: four short cards instead of a wall of text. */
.feature-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:1.1rem;margin:1.6rem 0 0}
.feature{border:1px solid var(--line);border-radius:14px;background:var(--code);padding:1.3rem 1.4rem}
.feature h3,.feature h3:first-of-type{margin:0 0 .5rem;font-size:1.08rem}
.feature p{margin:0;color:var(--mut);font-size:.95rem}
/* A look inside: real screens from the demo community. */
.tour-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:1.25rem;margin:1.6rem 0 0}
.tour-card,.tour-video{margin:0;border:1px solid var(--line);border-radius:14px;overflow:hidden;
  background:var(--code);display:flex;flex-direction:column}
.tour-card img{border-bottom:1px solid var(--line)}
.tour-card figcaption,.tour-video figcaption{margin:0;padding:1rem 1.25rem 1.15rem}
.tour-card h3,.tour-video h3,.tour-card h3:first-of-type{margin:0 0 .3rem;font-size:1.05rem;color:var(--fg)}
.tour-card p,.tour-video p{margin:0;font-size:.92rem;color:var(--mut)}
.tour-video{margin-top:1.25rem}
/* The video's width/height attributes give its ratio; without this rule it
   rendered at its attribute width and was clipped by the card. */
.tour-video video{display:block;width:100%;height:auto;border-top:1px solid var(--line);background:#05070a}
.mesh-layers{list-style:none;counter-reset:layer;padding:0;margin:0;display:grid;
  grid-template-columns:repeat(4,minmax(0,1fr));gap:1rem}
.mesh-layers li{counter-increment:layer;border-top:2px solid var(--line);padding:.8rem 0 0;
  color:var(--mut);font-size:.92rem}
.mesh-layers li::before{content:counter(layer);display:block;font:600 .8rem/1 ui-monospace,monospace;
  color:var(--amber);margin:0 0 .5rem}
.mesh-layers b{display:block;color:var(--fg);font-weight:640;margin:0 0 .2rem}
.faq-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:.4rem 2.4rem;margin:1.2rem 0 0}
.faq-item{border-top:1px solid var(--line);padding:1.1rem 0 .6rem}
.faq-item h3,.faq-item h3:first-of-type{margin:0 0 .4rem;font-size:1.02rem}
.faq-item p{margin:0;color:var(--mut);font-size:.95rem}
#register .cta{margin-top:1.1rem}
.vision{margin:2.6rem 0 0;padding:1.1rem 0 0;border-top:1px solid var(--line);color:var(--mut);font-size:.95rem}
/* Scroll reveals. Content is visible by default; only when site.js has run
   (it sets .js-reveal on the root) do sections below the fold start faded,
   and they always end visible. Reduced motion turns the whole thing off. */
.js-reveal .reveal{opacity:0;transform:translateY(16px);transition:opacity .6s ease,transform .6s ease}
.js-reveal .reveal.in{opacity:1;transform:none}
.js-reveal .reveal.d1{transition-delay:90ms}
.mesh-kicker{margin:0 0 .55rem;color:var(--amber)}
.mesh-lede{max-width:46rem}
.mesh-stage{margin:1.6rem 0 2rem;border:1px solid var(--line);border-radius:14px;
  background:var(--code);padding:1rem 1.1rem 1.15rem;overflow:hidden}
.mesh-toolbar{display:flex;flex-wrap:wrap;gap:.5rem;margin:0 0 .9rem}
.mesh-tab{appearance:none;background:var(--bg);color:var(--mut);
  border:1px solid var(--line);border-radius:8px;padding:.48rem .85rem;
  min-height:40px;font:600 .8rem/1.2 ui-monospace,SFMono-Regular,Menlo,monospace;
  cursor:pointer;transition:.15s}
.mesh-tab:hover{border-color:var(--acc);color:var(--fg)}
.mesh-tab.active{background:var(--deep);border-color:var(--acc);color:#fff}
.mesh-tab:focus-visible{outline:2px solid var(--acc);outline-offset:2px}
#mesh-canvas{display:block;width:100%;height:auto;border-radius:10px;
  border:1px solid var(--line);background:var(--bg)}
.mesh-caption{margin:.85rem 0 0;font-size:.88rem;color:var(--mut)}
.tcards{display:grid;grid-template-columns:repeat(auto-fit,minmax(15rem,1fr));
  gap:1.1rem;margin:1.6rem 0}
.tcard{border:1px solid var(--line);border-radius:12px;padding:1.2rem 1.3rem;
  background:var(--code);display:flex;flex-direction:column}
.tcard h2{font-size:1.12rem;margin:.1rem 0 .5rem}
.tcard p{font-size:.92rem;margin:0 0 .8rem;color:var(--mut)}
.tcard p strong{color:var(--fg)}
.tcard .btn{margin-top:auto;align-self:flex-start}
@media(max-width:760px){
  .feature-grid,.tour-grid,.faq-grid{grid-template-columns:1fr}
  .mesh-layers{grid-template-columns:repeat(2,minmax(0,1fr))}
}
h2{font-size:1.5rem;letter-spacing:-.02em;margin:0 0 .6rem}
h3{font-size:1rem;letter-spacing:-.01em;margin:2rem 0 .7rem;font-weight:640}
h3:first-of-type{margin-top:1.2rem}
.lede.sm{font-size:.94rem;margin-bottom:1rem}
.lede{color:var(--mut);margin:0 0 1.4rem;max-width:34rem}
.fineprint{font-size:.84rem;color:var(--mut);line-height:1.55;
  border-left:2px solid var(--line);padding-left:.9rem;margin:1.6rem 0 0}
.note{color:var(--mut);font-size:.86rem;margin:1rem 0 0}
/* Sprint 17B: declared block-scope placement variants on an Image + text
   block's own wrapper (never an inline style, never an undeclared class —
   diagram 11 l.76). Left/right float the picture and let the block's own
   text wrap around it; full width stacks the picture above, at its own
   width, with no wrap. */
[data-solace-kind="image-text"].img-left img{float:left;margin:0 1.2rem 1rem 0;max-width:50%;height:auto}
[data-solace-kind="image-text"].img-right img{float:right;margin:0 0 1rem 1.2rem;max-width:50%;height:auto}
[data-solace-kind="image-text"].img-left::after,
[data-solace-kind="image-text"].img-right::after{content:"";display:table;clear:both}
[data-solace-kind="image-text"].img-full img{width:100%;height:auto;float:none;margin:0 0 1rem}
/* Sprint 17B-3: declared width-step variants (drag-to-resize, snapped
   to the nearest step on release — never an inline width, diagram 11
   l.76) refine img-left/img-right's own fixed 50% into one of five
   declared steps. `width`, not `max-width`: a customer choosing "two
   thirds" expects the picture to actually occupy two thirds of the
   block regardless of the uploaded file's own native resolution — the
   same reasoning img-full's own `width:100%` already used; `max-width`
   only ever SHRINKS, so a step wider than an image's natural size would
   silently do nothing (caught by the resize journey's own real
   computed-ratio check, not assumed). Each step also clears the base
   rule's own `max-width:50%` back to `none`: that property is untouched
   by a `width` declaration at any specificity, so left uncleared it
   silently clamped every step above 50% back down to it (the same
   computed-ratio check caught this too). Not paired with img-full: full
   width already claims the whole block edge to edge, so a width step
   has nothing to modify there. No step class present keeps the
   original 17B default (max-width:50%) exactly — old published content
   with no img-wNN class is untouched. */
[data-solace-kind="image-text"].img-left.img-w25 img,[data-solace-kind="image-text"].img-right.img-w25 img{width:25%;max-width:none}
[data-solace-kind="image-text"].img-left.img-w33 img,[data-solace-kind="image-text"].img-right.img-w33 img{width:33%;max-width:none}
[data-solace-kind="image-text"].img-left.img-w50 img,[data-solace-kind="image-text"].img-right.img-w50 img{width:50%;max-width:none}
[data-solace-kind="image-text"].img-left.img-w66 img,[data-solace-kind="image-text"].img-right.img-w66 img{width:66%;max-width:none}
[data-solace-kind="image-text"].img-left.img-w100 img,[data-solace-kind="image-text"].img-right.img-w100 img{width:100%;max-width:none}
/* CLEANUP-2 (2026-09-27, owner QA finding C2-5): "dragging a picture's
   corner shrinks it, but it pops back to the original size on release."
   The rules above only matched an img-wNN step PAIRED with img-left or
   img-right — the resize handle (web/editor.py::wireResizeHandle) offers
   a width step on ANY selected picture in an Image + text block, with no
   placement precondition, so a picture with no placement chosen (the
   common/default case right after inserting one) got a class the CSS
   never matched: the inline drag style was removed on release and
   nothing else constrained the width, so it snapped back to its
   unplaced default. These bare rules give a step real effect with no
   placement class present too; a later `.img-left.img-wNN`/
   `.img-right.img-wNN` selector still wins by specificity when a
   placement IS also chosen, so this changes nothing for that case. */
[data-solace-kind="image-text"].img-w25 img{width:25%;max-width:none}
[data-solace-kind="image-text"].img-w33 img{width:33%;max-width:none}
[data-solace-kind="image-text"].img-w50 img{width:50%;max-width:none}
[data-solace-kind="image-text"].img-w66 img{width:66%;max-width:none}
[data-solace-kind="image-text"].img-w100 img{width:100%;max-width:none}
/* Sprint 18C: a picture's own crop ratio and focal point — two declared
   data-attribute VALUES (web_svp/content.py IMAGE_RATIOS/
   IMAGE_FOCAL_POINTS), read only by this one declared CSS rule set:
   never an inline style, never a second, re-encoded copy of the file.
   "original" is an explicit, storable choice (not just "attribute
   absent") so a picture that was deliberately reset back to its
   native shape reads the same as one 18C has never touched.
   object-position only visibly moves anything once object-fit:cover
   is also cropping the image — paired with a non-original ratio, a
   no-op otherwise, so choosing a focal point before a ratio is never
   a broken combination to guard against. */
img[data-image-ratio="original"]{aspect-ratio:auto;object-fit:fill}
img[data-image-ratio="16-9"]{aspect-ratio:16/9;object-fit:cover;width:100%}
img[data-image-ratio="4-3"]{aspect-ratio:4/3;object-fit:cover;width:100%}
img[data-image-ratio="1-1"]{aspect-ratio:1/1;object-fit:cover;width:100%}
img[data-image-ratio="3-4"]{aspect-ratio:3/4;object-fit:cover;width:100%}
img[data-image-focus="top-left"]{object-position:0% 0%}
img[data-image-focus="top"]{object-position:50% 0%}
img[data-image-focus="top-right"]{object-position:100% 0%}
img[data-image-focus="left"]{object-position:0% 50%}
img[data-image-focus="center"]{object-position:50% 50%}
img[data-image-focus="right"]{object-position:100% 50%}
img[data-image-focus="bottom-left"]{object-position:0% 100%}
img[data-image-focus="bottom"]{object-position:50% 100%}
img[data-image-focus="bottom-right"]{object-position:100% 100%}
/* F2b (owner fix, 2026-09-28): the SAME declared classes the block-
   wrapped rules above already have, matched a second way — directly on
   the picture itself, no `[data-solace-kind]` ancestor required. A
   picture placed straight into an ordinary section's own text
   (web/editor.py::wrapEligibleTarget) with the rail's plain Image
   button never creates an Image + text block wrapper to carry them;
   disallowed_html_reason (web_svp/operations.py) already validates a
   class token against the site's declared style options only, never
   against which tag carries it, so no new class is declared here —
   only where it can land. Placed AFTER the crop-ratio rules above,
   deliberately: `img.img-wNN` and `img[data-image-ratio]` both set
   `width` at equal specificity, and a cropped, resized bare picture
   (found live, building the F3 walkthrough) needs the chosen width
   step to win, the same way the block-wrapped rules already do by
   their own higher specificity (an ancestor attribute selector, never
   only the bare `img` this case has). */
img.img-left{float:left;margin:0 1.2rem 1rem 0;max-width:50%;height:auto}
img.img-right{float:right;margin:0 0 1rem 1.2rem;max-width:50%;height:auto}
img.img-full{width:100%;height:auto;float:none;margin:0 0 1rem}
img.img-w25{width:25%;max-width:none}
img.img-w33{width:33%;max-width:none}
img.img-w50{width:50%;max-width:none}
img.img-w66{width:66%;max-width:none}
img.img-w100{width:100%;max-width:none}
/* Sprint 17C: declared block-scope COLUMN LAYOUT variants on a Text
   block's own wrapper — never a free grid an operator positions by
   hand, four fixed declared ratios only. CSS Grid, not multi-column
   text flow: `column-count` always produces EQUAL widths, which cannot
   express 1:2/2:1, and grid's own default auto-placement already puts
   every child (heading included) into cells in DOM order with no
   per-child styling needed — "children flow into the columns" is
   exactly grid's own built-in behavior, not something built here.
   Narrower than 640px stacks to one column: a fixed multi-column grid
   at phone width is illegible, not a layout choice worth offering. */
[data-solace-kind="text"].columns-two{display:grid;grid-template-columns:1fr 1fr;gap:1.6rem;align-items:start}
[data-solace-kind="text"].columns-1-2{display:grid;grid-template-columns:1fr 2fr;gap:1.6rem;align-items:start}
[data-solace-kind="text"].columns-2-1{display:grid;grid-template-columns:2fr 1fr;gap:1.6rem;align-items:start}
[data-solace-kind="text"].columns-three{display:grid;grid-template-columns:1fr 1fr 1fr;gap:1.6rem;align-items:start}
@media(max-width:640px){
  [data-solace-kind="text"].columns-two,[data-solace-kind="text"].columns-1-2,
  [data-solace-kind="text"].columns-2-1,[data-solace-kind="text"].columns-three{grid-template-columns:1fr}
}
/* Sprint 17C: declared block-scope BACKGROUND variants — colour only,
   this box; an owned-upload image background with alt text and a
   legibility scrim is its own named scope, built below as 17C-2 (see
   DECISIONS.md), not folded into this box's own falsifier. Each class names an
   EXISTING token this stylesheet already defines above (:root's own
   --code/--deep/--line) — never an arbitrary colour a customer could
   type in; the class is the only thing that reaches published content
   (diagram 11 l.76), so the actual colour can only ever be one this
   site's own design already uses elsewhere. Padding accompanies the
   background so text never touches the block's own edge.*/
[data-solace-kind="text"].bg-code,[data-solace-kind="cta"].bg-code,[data-solace-kind="faq"].bg-code{
  background:var(--code);padding:1.4rem 1.6rem;border-radius:12px}
[data-solace-kind="text"].bg-deep,[data-solace-kind="cta"].bg-deep,[data-solace-kind="faq"].bg-deep{
  background:var(--deep);color:#fff;padding:1.4rem 1.6rem;border-radius:12px}
[data-solace-kind="text"].bg-line,[data-solace-kind="cta"].bg-line,[data-solace-kind="faq"].bg-line{
  background:var(--line);padding:1.4rem 1.6rem;border-radius:12px}
/* Sprint 17C-2: an OWNED-UPLOAD image background, never a typed-in URL
   and never an inline style (diagram 11 l.76) — reuses the existing
   picture-insertion mechanism exactly (same upload, same alt-text/
   decorative dialog already checked by web_svp/media.py and
   disallowed_html_reason's own <img src> allow-list), never a new
   attribute or a second upload path. `bg-image` positions the block's
   own FIRST <img> as a full-bleed backdrop layer, purely by CSS
   selector — no class or data attribute on the <img> itself, so the
   exact same inserted picture stays a real, described <img> in the
   DOM (its own accessible description is the alt text the insert
   dialog already collects, not a new field invented for this).
   `bg-scrim` darkens that same picture with a `filter:brightness`,
   not a separate overlay element: an earlier version stacked a
   z-index:-1 pseudo-element scrim above a z-index:-2 <img>, correct
   per spec, but this engine's own negative-z-index paint order for a
   replaced element (<img>) versus generated content did not honour
   it — confirmed by a real computed-pixel check, not assumed (a
   still's own rendered colour matched the raw picture, un-blended).
   A brightness filter needs no second layer and no z-index ordering
   between two negative-index siblings to get right: 35% brightness
   left on white (a worst-case pale photo) still clears 4.5:1 contrast
   for the white text this class also sets (verified by the resize
   journey's own real computed-style contrast check, not assumed). */
[data-solace-kind="text"].bg-image,[data-solace-kind="cta"].bg-image,[data-solace-kind="faq"].bg-image{
  position:relative;overflow:hidden;padding:1.4rem 1.6rem;border-radius:12px}
[data-solace-kind="text"].bg-image img,[data-solace-kind="cta"].bg-image img,[data-solace-kind="faq"].bg-image img{
  position:absolute;inset:0;width:100%;height:100%;object-fit:cover;z-index:-1;margin:0;max-width:none;float:none}
[data-solace-kind="text"].bg-image.bg-scrim img,[data-solace-kind="cta"].bg-image.bg-scrim img,
[data-solace-kind="faq"].bg-image.bg-scrim img{filter:brightness(35%)}
[data-solace-kind="text"].bg-image.bg-scrim,[data-solace-kind="cta"].bg-image.bg-scrim,
[data-solace-kind="faq"].bg-image.bg-scrim{color:#fff}
/* Sprint 17D: an Embed block's own real <iframe> only ever exists here,
   in this served stylesheet's own page — never in the editor's own
   canvas (web_svp/content.py::_expand_embeds only expands it for a real
   visitor). No width/height attribute is set on the injected <iframe>
   itself (never a value this code invented mid-render), so its box comes
   entirely from this responsive 16:9 wrapper, matching the block's own
   wrapper it is already inside. */
[data-solace-kind="embed"]{position:relative;padding-top:56.25%;height:0;
  overflow:hidden;border-radius:10px;background:var(--code)}
[data-solace-kind="embed"] iframe{position:absolute;inset:0;width:100%;
  height:100%;border:0}
.why{list-style:none;counter-reset:n;padding:0;margin:1.5rem 0 0}
.why li{counter-increment:n;position:relative;padding:0 0 0 2.4rem;
  margin-bottom:1.3rem;color:var(--mut)}
.why li::before{content:counter(n);position:absolute;left:0;top:.05rem;
  width:1.6rem;height:1.6rem;border-radius:6px;border:1px solid var(--line);
  display:grid;place-items:center;font:600 .8rem/1 ui-monospace,monospace;
  color:var(--acc)}
.why b{color:var(--fg);font-weight:640}

.dl-list{list-style:none;padding:0;margin:0;border:1px solid var(--line);
  border-radius:12px;overflow:hidden;
  background:color-mix(in srgb,var(--bg) 62%,transparent);backdrop-filter:blur(10px)}
.dl-list > li{display:flex;align-items:center;gap:.8rem;padding:.82rem 1.05rem;
  border-bottom:1px solid var(--line);font-size:.94rem}
.dl-list > li:last-child{border-bottom:none}
.dl-list > li.mac-install{display:block}
.plat{font-weight:620;min-width:5.4rem}
.arch{color:var(--mut);flex:1}
.dl-actions{display:flex;align-items:center;gap:.35rem;flex-shrink:0}
.dl{font:500 .74rem/1 ui-monospace,monospace;letter-spacing:.12em;
  text-transform:uppercase;color:var(--mut);border:1px solid var(--line);
  border-radius:6px;padding:.28rem .6rem;
  /* WCAG 2.5.8: these pills are standalone targets, measured 23px. */
  display:inline-flex;align-items:center;min-height:24px}
a.dl.live{color:var(--acc);border-color:color-mix(in srgb,var(--acc) 46%,transparent);
  text-decoration:none}
a.dl.live:hover{background:color-mix(in srgb,var(--acc) 12%,transparent)}
@media(max-width:560px){
  .dl-list > li{align-items:flex-start;flex-wrap:wrap}
  .dl-actions{width:100%;flex-wrap:wrap}
}

code{background:var(--code);padding:.13em .4em;border-radius:4px;
  font:.87em ui-monospace,SFMono-Regular,Menlo,monospace;color:var(--acc)}
a{color:var(--acc)}

footer{border-top:1px solid var(--line);padding:2.6rem 1.6rem 1.6rem;color:var(--mut);font-size:.88rem}
.foot-grid{max-width:72.8rem;margin:0 auto;display:grid;gap:2rem;
  grid-template-columns:minmax(0,1.6fr) repeat(4,minmax(0,1fr))}
.foot-brand p{margin:.6rem 0 1rem;max-width:18rem}
.foot-col h2{font:600 .74rem/1.2 ui-monospace,SFMono-Regular,Menlo,monospace;letter-spacing:.1em;
  text-transform:uppercase;color:var(--fg);margin:.3rem 0 .7rem}
.foot-col ul{list-style:none;padding:0;margin:0}
.foot-col li{margin:0}
/* Footer links are 28px tall: over the 24px minimum target size (WCAG 2.5.8). */
footer a{display:inline-flex;align-items:center;min-height:28px;color:var(--mut)}
footer a:hover{color:var(--acc)}
footer .brand{color:var(--fg)}
.en-only{font-size:.78rem;opacity:.8}
.foot-legal{max-width:72.8rem;margin:2.2rem auto 0;padding:1.2rem 0 0;border-top:1px solid var(--line);
  font-size:.8rem;line-height:1.9}
.foot-legal a{display:inline;color:inherit}
/* The consent box used to be an <input> wrapped in a bare <label> with a link
   inside it. Screen readers get a cleaner name from label[for], and the link
   to /terms is no longer nested in the control's own label. */
.terms-row{display:flex;align-items:flex-start;gap:.6rem;margin:.6rem 0}
.terms-row input{width:20px;height:20px;margin:.15rem 0 0;flex:none}
.terms-row label{cursor:pointer}
.dot{margin:0 .45rem;opacity:.45}
.bld{opacity:.6}
/* 21H-F1 (auditor): the home page's own inquiry form and a Form block's
   real, rendered form share this one class — one set of rules for both,
   never two independently-maintained looks for the same kind of form. */
.solace-inquiry-form{max-width:420px}
.solace-inquiry-form label{display:block;margin:.9rem 0 .3rem;font-weight:600}
.solace-inquiry-form input,.solace-inquiry-form textarea{display:block;width:100%;
  padding:.6rem .75rem;border:1px solid var(--line);border-radius:8px;
  background:var(--code);color:var(--fg);font:inherit}
.solace-inquiry-form textarea{min-height:6rem;resize:vertical}
.solace-inquiry-form button{margin-top:1rem}

/* The header is one row at every width and in every language. The sister
   sites are in the menu and the footer, not the row: six links, sign-in, the
   language switch and the app button are what fits beside the brand in
   Vietnamese. Below 1040px the page links move into the menu too. */
header nav > .agi,header nav > .nav-sep{display:none}
/* Vietnamese labels run longer ("Bảo mật & Tin cậy"): just above the menu
   breakpoint the links sit closer so the first one clears the brand. */
@media(min-width:1041px) and (max-width:1100px){html[lang="vi"] header nav{gap:.8rem}}
@media(max-width:1040px){
  /* The row keeps the language switch and the app button; every link is in
     the menu. */
  header nav > a:not(.pill){display:none}
  .nav-menu{display:block}
}
/* Labels in other languages run longer than the English ones ("Keamanan &
   Kepercayaan", "Sicherheit & Vertrauen"), and the language button shows a
   whole name, so outside English the links move into the menu from 1200px
   down. Measured: every language keeps one 79-80px row with the first link
   clear of the brand at 1041, 1100, 1201, 1280 and 1440px. */
@media(max-width:1200px){
  html:not([lang="en"]) header nav > a:not(.pill){display:none}
  html:not([lang="en"]) .nav-menu{display:block}
}
@media(max-width:900px){
  .hero{grid-template-columns:1fr;gap:2.6rem;padding-top:1.2rem}
  .foot-grid{grid-template-columns:repeat(2,minmax(0,1fr))}
  .foot-brand{grid-column:1/-1}
}
@media(max-width:560px){
  /* Found 2026-08-05: at 390px the nav and the Get-the-app pill overflowed
     the viewport by 87px, cutting the nav links off mid-word and forcing a
     horizontal scrollbar. Nothing on a landing page should scroll sideways. */
  header{gap:.5rem;padding-left:1.1rem;padding-right:1.1rem}
  header nav{gap:.5rem}
  /* A phone cannot install the desktop app, so the app button gives its
     place to the language switch and the menu; the menu still links it. */
  header nav > .pill{display:none}
  main{padding-left:1.1rem;padding-right:1.1rem}
  .mesh-layers{grid-template-columns:1fr}
  #canvasui-fx{left:-.9rem;width:calc(100% + 1.8rem)}
  .shot-stage::before{inset:-2.2rem -.9rem}
  .wrap{padding-left:1.1rem;padding-right:1.1rem}
  h1,.word{max-width:100%}
}
/* Nothing may push the page sideways — the symptom is always a scrollbar and
   text sheared off at the right edge. */
html,body{max-width:100%;overflow-x:hidden}
@media(prefers-reduced-motion:reduce){
  html{scroll-behavior:auto}
  .js-reveal .reveal{opacity:1;transform:none;transition:none}
  #canvasui-fx{display:none}
  .btn,.pill,.mesh-tab{transition:none}
}

body.doc main{max-width:44rem;margin:0 auto;padding:2rem 1.6rem 5rem}
body.doc h1{font-size:2rem;letter-spacing:-.02em;margin:1rem 0 .3rem}
body.doc .eff{font:500 .78rem/1.4 ui-monospace,SFMono-Regular,Menlo,monospace;
  opacity:.55;margin:0 0 2.4rem}
body.doc h2{font-size:1.15rem;margin:2.6rem 0 .6rem}
body.doc p,body.doc li{line-height:1.65;opacity:.86}
body.doc ul{padding-left:1.1rem;margin:.6rem 0}
body.doc li{margin:.35rem 0}
/* 2026-09-18 Sprint 8: a picture the owner uploads never overflows its section (doc pages only — the home page's markup is byte-for-byte pinned by tests/fixtures). */
[data-solace-id] img{max-width:100%;height:auto}
body.doc table{border-collapse:collapse;width:100%;margin:1rem 0;font-size:.93rem}
body.doc th,body.doc td{text-align:left;padding:.55rem .6rem;
  border-bottom:1px solid var(--line);vertical-align:top}
body.doc th{font-weight:600;opacity:.7}
body.doc a{color:inherit}
/* …except the skip link, whose own contrast must hold: `body.doc a` is
   more specific than `.skip-link`, so it rendered ink on ink (1:1). */
body.doc a.skip-link{color:var(--bg)}
body.doc a.pill{color:var(--bg)}
body.doc a.pill:hover{color:#fff}
body.doc .box{border:1px solid var(--line);border-radius:.6rem;
  padding:1rem 1.2rem;margin:1.4rem 0}
body.doc .lede{color:var(--mut);font-size:1.02rem;margin:0 0 1.2rem}
body.doc .note{color:var(--mut);font-size:.86rem;margin:1rem 0 0}
body.doc .preview{display:inline-block;font:600 .72rem/1 ui-monospace,
  SFMono-Regular,Menlo,monospace;letter-spacing:.1em;text-transform:uppercase;
  color:var(--acc);border:1px solid var(--line);border-radius:6px;
  padding:.3rem .6rem;margin-bottom:.4rem}
body.doc .tiers,body.doc .tcards{display:grid;
  grid-template-columns:repeat(auto-fit,minmax(13rem,1fr));gap:1rem;
  margin:1.6rem 0}
body.doc .tier,body.doc .tcard{border:1px solid var(--line);border-radius:.7rem;
  padding:1.1rem 1.2rem}
body.doc .tier h2,body.doc .tcard h2{font-size:1.05rem;margin:.2rem 0 .5rem}
body.doc .price{font-weight:650;font-size:1.1rem;margin:0 0 .8rem}
body.doc .price span{font-weight:500;font-size:.78rem;color:var(--mut)}
body.doc .tier ul{font-size:.86rem}
body.doc .tcard p{font-size:.9rem}
/* Pages that carry cards or a screenshot get a wider column; their prose
   keeps the reading measure. */
body.doc.wide main{max-width:62rem}
body.doc.wide main > p,body.doc.wide main > h2,body.doc.wide main > .box{max-width:44rem}
body.doc .doc-shot{margin:1.8rem 0}
body.doc .doc-shot picture{display:block;border:1px solid var(--line);border-radius:12px;overflow:hidden;background:#05070a}
body.doc h3{font-size:1rem;margin:1.6rem 0 .4rem}
body.doc .status-list{padding-left:1.1rem}
body.doc .showcase-card{margin-top:1rem;padding:1rem;border:1px solid var(--line);border-radius:6px;background:var(--code)}
body.doc .crumb{color:var(--mut);font-size:.92rem;margin:0}
body.doc pre{background:var(--code);padding:.8rem 1rem;border-radius:8px;overflow-x:auto;
  font:.86rem/1.5 ui-monospace,SFMono-Regular,Menlo,monospace}
body.doc td code{word-break:break-all}
body.doc .manual-back{margin:0 0 1.2rem}
body.doc .manual-back a{font-size:.9rem;color:var(--acc);text-decoration:none;font-weight:600}
body.doc .manual-lede{font-size:1.1rem;line-height:1.5;margin:0 0 1.5rem;color:var(--fg);font-weight:500;opacity:1}
body.doc .manual-step{margin:0 0 2rem;padding:0 0 1.5rem;border-bottom:1px solid var(--line)}
body.doc .manual-step h2{font-size:1.25rem;margin:0 0 .6rem;color:var(--fg)}
body.doc .manual-step-body{font-size:.95rem;line-height:1.65;color:var(--mut)}
body.doc .box.manual-summary{margin-bottom:2.2rem}
body.doc .box.manual-ask{margin-top:2rem}
body.doc .tcard .tcard-sub{margin:.4rem 0 .8rem;color:var(--fg);font-weight:500;opacity:1}
