/* ════════════════════════════════════════════════════════════════════════════════
   hero-v2.css — the signed-in composer. SHIPPED (2026-11-21).

   Every rule in this file is gated on html[data-hero-v2]. Until 2026-11-21 that
   marker existed only on a generated preview page, so the fence was "no page
   carries the marker". The Founder authorised the port, index.html now carries
   the marker, and the fence moved — it is now the ELEMENT, not the attribute:
   every rule gated on the marker ALONE names a node the runtime creates on
   sign-in and deletes on sign-out (the stage, the appearance tray, "My rooms",
   the retired CTA row). Measured 2026-11-21: 162 data-hero-v2 rules, 32 gated on
   the marker alone, and every element those 32 name is absent from static
   index.html. test/hero-v2.test.js asserts that stays true.

   And the signed-in half is gated a second time, on a session phase
   (data-hero-v2-signedin / -authed / -exiting / -pending). hero-v2.js sets those
   only when a session token exists, so the ANONYMOUS rendering of index.html is
   byte-for-byte the anonymous page it was before the port. That is the safety
   property: the composer can never show a signed-out visitor something the live
   page did not already show.

   WHAT THIS FILE DOES NOT DO
   No handler, no fetch, no state, no copy. It moves nothing. hero-v2.js moves
   #weyaFabRoot and #heroForming into the stage; this file only decides what the
   resulting column looks like. Every modal (funnel 9600, s5 9700, gear 10001,
   stay-confirm 10200) is outside #hero and untouched here — not one selector.

   THE SHAPE, IN ONE PARAGRAPH
   Signed in, the hero is one centred column, 720px wide. Top: the Weya composer
   — the same 44px pill, now a 60px bar, in the place the avatar vacated. Below
   it: the glimpse, collapsed to one line, exactly as it is today. The avatar
   column retires (it was already opacity:0 on sign-in since DR-2026-09-20-03),
   and the corner dock retires with it. The chat panel stops being a floating
   380px card in the bottom-right corner and becomes the column's own body: it
   opens BELOW the bar, in flow, 720px wide. Nothing overlays anything.
   ════════════════════════════════════════════════════════════════════════════════ */

/* ───────────────────────────────────────────────────────────────────────────────
   0. The one column. Applies to the signed-in state only.
   ─────────────────────────────────────────────────────────────────────────────── */

/* The signed-in column is centred, exactly as the shipped hero centres its
   split. This rule is the shipped one restated for the new single column and
   nothing more. */
html[data-hero-v2][data-hero-v2-signedin] .hero-split {
  /* today: grid-template-columns: 1fr 1fr; gap: 60px */
  display: flex;
  flex-direction: column;
  align-items: stretch;
  justify-content: center;
  gap: 0;
  max-width: 720px;
  width: 100%;
  /* MEASURED: the column is 578px closed and 898px with both disclosures open.
     .hero is 100vh with min-height:640 and overflow:hidden (hero.css:2-9), so on
     the shortest hero the promise makes, a centred 898px column would push the
     composer off the top edge with #hero clipping it — unreachable, and #hero
     cannot scroll.

     Capping the column and letting it shrink is flexbox's own answer: the
     composer keeps its 60px, the panel and the glimpse take what is left and
     scroll inside themselves. Nothing is clipped, nothing scrolls at the page
     level, and the overlay keeps its shipped pointer-events:none.

     132px, not 32px: centred, this leaves 66px of clearance above the composer
     on every viewport — enough for the "Signed in / Sign out" chip (16..78) to
     never share a band with the bar it sits beside. At 32px the fully-open
     column measured a bar at y=16, flush against the top edge of the hero. */
  max-height: calc(100vh - 132px);
  min-height: 0;
}

html[data-hero-v2][data-hero-v2-signedin] .hero-left {
  /* today: gap 22px, the marketing stack rhythm */
  display: flex;
  flex-direction: column;
  align-items: stretch;
  gap: 16px;
  width: 100%;
  /* min-height:0 is what lets a flex child go below its content size. Without
     it the panel refuses to shrink and the column overflows anyway. */
  min-height: 0;
}

/* The avatar column retires. Not "hidden behind something" — removed from the
   flow, because the composer now stands where she stood. Her face is already
   gone at this point in the shipped page (diminishHeroForProfile sets
   opacity:0 on the wrap); this removes the empty 200px box it left behind. */
html[data-hero-v2][data-hero-v2-signedin] .hero-weya-col {
  display: none;
}

/* Founder answer 1a: one door to My rooms. hero-v2.js marks the CTA row; this
   is the whole removal. Un-marked on sign-out, so the anonymous CTA returns.
   Gated on the marker alone — it is only ever set while a session exists. */
html[data-hero-v2] .hero-cta-row[data-hero-v2-retired="1"] {
  display: none;
}

/* ───────────────────────────────────────────────────────────────────────────────
   0b. The handover (Founder walk, 2026-11-19).

   WHAT WAS WRONG. hero.js retires the marketing intro with a class
   (.hero-intro.is-retired → display:none) in the same frame that the forming
   window appears and the FAB blooms. Two states of the page were being asked
   to swap in one frame: the copy vanished, the column re-centred, and the only
   thing moving was her face. That is the dissonance the walk named.

   THE FIX IS ONE SHARED LANGUAGE, NOT MORE MOTION. The old hero leaves the way
   the avatar does — a short lift and fade — and the composer arrives on the
   same curve from below. hero-v2.js sets [data-hero-v2-exiting] only when the
   intro was actually on screen, so a returning member's page never replays a
   departure it did not witness.

   WHY ABSOLUTE. The retired intro must not keep its layout box during the
   fade: the glimpse and the composer are moving into that space, and a box
   that lingers would push them down for the duration. Absolute takes it out
   of flow, so the incoming column lays out immediately underneath while the
   copy finishes leaving over it.
   ─────────────────────────────────────────────────────────────────────────────── */

/* ONE DEPARTURE, NOT FOUR.

   The first build animated four parts of the old hero on four different
   timings - 320ms, 260ms, 220ms, 200ms - across three different curves, and it
   sent the copy UP (-10px) while sending the CTA row and the corner pill DOWN
   (+6px). Each part was individually reasonable and the sum read as several
   things twitching: the eye cannot resolve a block that tears in two
   directions at four speeds.

   A departure is one gesture. So: one curve, one duration, one direction, and
   a stagger small enough to read as a wave rather than as separate events.
   Everything recedes UPWARD - away from the composer that is about to occupy
   the space - and the composer then rises from below. One axis of travel for
   the whole handover: the page moves up, continuously.

   WHY EASE-IN AND NOT EASE-OUT. Content that is arriving decelerates (ease-out)
   because it is coming to rest. Content that is leaving accelerates (ease-in)
   because it is going somewhere else. Using the arrival curve on the departure
   is what made it feel like a dissolve rather than a departure.

   THE STAGGER IS BY MASS, NOT BY TASTE. The headline is the largest object and
   goes first; the CTA row follows it because it is read with it; the empty
   ring column and then the 44px pill trail behind. 30ms steps - below the
   threshold at which the eye reads separate events, above the threshold at
   which the wave is visible. */
html[data-hero-v2][data-hero-v2-exiting] .hero-intro.is-retired {
  /* shipped: display:none (hero.css). Held for the departure only. */
  display: flex;
  position: absolute;
  top: 0;
  left: 0;
  right: 0;
  width: 100%;
  pointer-events: none;
  animation: heroV2FieldOut 220ms cubic-bezier(0.40, 0.00, 1.00, 1.00) both;
}

/* The CTA row is part of the old hero too. It used to be removed the instant
   auth landed - seconds before its column left. It now leaves with the copy,
   then the signed-in rule below removes it for real.

   ABSOLUTE DURING THE EXIT, and that is load-bearing: while both the exiting
   and the signed-in attributes are present this rule wins on specificity, and
   an in-flow CTA row would push the arriving composer down for the length of
   the departure. Out of flow it can fade over the space without occupying it. */
html[data-hero-v2][data-hero-v2-exiting] .hero-cta-row[data-hero-v2-retired="1"] {
  display: flex;
  position: absolute;
  left: 0;
  right: 0;
  pointer-events: none;
  animation: heroV2SettleOut 220ms cubic-bezier(0.40, 0.00, 1.00, 1.00) 30ms both;
}

/* The avatar itself belongs to hero.js and is untouched. What remains of her
   column at this point is the empty 200px box and its rings; it leaves with
   everything else instead of disappearing at the swap. */
html[data-hero-v2][data-hero-v2-exiting] .hero-weya-col {
  animation: heroV2ColumnOut 220ms cubic-bezier(0.40, 0.00, 1.00, 1.00) 50ms both;
}

/* The corner FAB is the one thing that must not be seen widening into the
   column. It says goodbye at its shipped 44px size, and the composer arrives
   at its final width. No intermediate width is ever painted. It leaves LAST:
   it is the object the avatar just landed in, so it is the last thing the eye
   should be holding. */
html[data-hero-v2][data-hero-v2-exiting] .weya-fab-root {
  animation: heroV2FabOut 220ms cubic-bezier(0.40, 0.00, 1.00, 1.00) 70ms both;
}

/* All four travel the same axis. The distances differ only by mass. */
@keyframes heroV2FieldOut {
  from { opacity: 1; transform: translateY(0); }
  to   { opacity: 0; transform: translateY(-14px); }
}
@keyframes heroV2SettleOut {
  from { opacity: 1; transform: translateY(0); }
  to   { opacity: 0; transform: translateY(-10px); }
}
@keyframes heroV2ColumnOut {
  from { opacity: 1; transform: translateY(0); }
  to   { opacity: 0; transform: translateY(-8px); }
}
@keyframes heroV2FabOut {
  from { opacity: 1; transform: translateY(0) scale(1); }
  to   { opacity: 0; transform: translateY(-6px) scale(0.96); }
}

/* Latent collision, made explicit. .weya-session-bar sits at top:18 right:20
   z:900 and .s5-header-chip at top:16 right:20 z:9400 — the same coordinates.
   The chip is the real control; the bar is a session-pip indicator that says
   nothing the chip does not. In the signed-in column the corner belongs to
   "Signed in / Sign out" and "My rooms", so the pip steps out of the way.
   Gated on authed, not signedin: the corner is true before the gesture ends. */
html[data-hero-v2][data-hero-v2-authed] .weya-session-bar {
  display: none;
}

/* THE CORNER IS NEVER PAINTED WHEN THE COMPOSER IS ALREADY DUE (2026-11-21).

   THE DEFECT. weya-fab.js runs BEFORE this file (index.html loads it at L1049;
   hero-v2.js is last) and its init calls refreshFabVisibility() ->
   setFabVisible(isSignedIn()), which REMOVES the `hidden` attribute
   index.html:259 ships. So a returning member's browser paints the 44px
   corner dock, and only then does boot() move the same node into the stage.
   FOUNDER, 2026-11-21: "i saw the fab icon on the bottom right for a second
   and then the composer showed up ... visually taxing". He is right: the
   element that flashes is the element about to become the composer, so the
   flash advertises a control that is leaving in the same breath.

   WHY `visibility` AND NOT `display`. The node must keep its box: the arrival
   origin and the stage rect are measured in the same frame the node moves, and
   a display:none root would measure 0x0. Invisible, never unlaid-out.

   WHY IT IS AN ATTRIBUTE AND NOT A JS STYLE WRITE. The reversal must be one
   removeAttribute: resetToAnonymous() already strips every attribute this file
   writes, and an inline style would have to be cleared separately or leak onto
   the anonymous page.

   WHEN IT IS SET. Only when NO gesture is owed (see markCornerPending in
   hero-v2.js). A first-ever member is owed the avatar's flight, and during
   that flight the corner dock is still the shipped hero - it must be there.
   The existing heroV2FabOut exit (L181) already gives it a goodbye for that
   case; this rule covers the returning member, where there is no exit beat and
   the flash was pure loss. */
html[data-hero-v2][data-hero-v2-pending] .weya-fab-root {
  visibility: hidden;
}

/* ───────────────────────────────────────────────────────────────────────────────
   1. The stage — composer, then glimpse.
   hero-v2.js inserts #heroV2Stage as the first child of .hero-left and moves
   #weyaFabRoot and #heroForming into it, in that order.
   ─────────────────────────────────────────────────────────────────────────────── */

html[data-hero-v2] .hero-v2-stage {
  display: flex;
  flex-direction: column;
  gap: 16px;
  width: 100%;
  min-width: 0;
  /* The shrink chain: split → left → stage → fab-root → panel. Every link needs
     min-height:0 or the chain stops compressing at that link. */
  min-height: 0;
}

/* THE ARRIVAL IS THE SECOND HALF OF THE SAME GESTURE.

   The old hero recedes upward (§0b); the composer must therefore come to rest
   from below, on the same axis, with the opposite curve — decelerating,
   because it is arriving rather than leaving. 420ms/12px read as a snap next
   to a 220ms departure: the eye had barely registered the space emptying
   before the new surface had already stopped. 520ms over 18px lets the
   movement be seen.

   NO SCALE. The first build added scale(0.992) as well, which is invisible on
   its own and turns to mush when combined with a translate on a surface full of
   text — it re-rasterises the panel's type mid-flight. One property per axis:
   translateY for travel, opacity for presence.

   Opacity + transform only, and switched off under reduced motion (§7).

   THE ANIMATION NAME IS CHOSEN HERE, NOT BY A SECOND SELECTOR. The origin is
   carried in `--hv2-arrive-x` / `--hv2-arrive-y`; when hero-v2.js has measured
   one, the same rule swaps to the two-axis keyframes. One rule, one
   specificity, so the reduced-motion guards below can actually win - a second
   selector that added an attribute test to the same element scored higher than
   them and silently defeated reduced motion (MEASURED 2026-11-20). */
html[data-hero-v2][data-hero-v2-signedin]:not([data-hero-v2-opened]) .hero-v2-stage {
  --hv2-arrive-anim: heroV2ComposerIn;
  animation: var(--hv2-arrive-anim) 520ms cubic-bezier(0.16, 0.84, 0.30, 1.00) both;
}

html[data-hero-v2][data-hero-v2-signedin]:not([data-hero-v2-opened]) .hero-v2-stage[style*="--hv2-arrive-x"] {
  --hv2-arrive-anim: heroV2ComposerInFromAvatar;
}

@keyframes heroV2ComposerIn {
  from { opacity: 0; transform: translateY(18px); }
  to   { opacity: 1; transform: translateY(0); }
}

/* THE ARRIVAL STARTS FROM WHERE SHE STOOD (Founder direction, 2026-11-20).

   The keyframes above are kept as the fallback and the ones below take over
   when hero-v2.js has measured an avatar origin. The origin is written as two
   custom properties BEFORE the signed-in flip: her centre expressed as an
   offset from the stage's own resting centre. MEASURED at the swap frame:
   -290px/+80px on 1440x900, +0.5px/-625px on 390x844 - against the flat 18px
   settle the fallback uses.

   WHY A SECOND @keyframes RATHER THAN EDITING THE FIRST. `var()` inside a
   keyframe falls back per-property, so a single rule could carry both. It is
   kept separate so the shipped 18px rise remains literally readable in the
   file: a reader can see what a returning member gets without evaluating
   fallback chains. hero-v2.js switches the animation NAME, so exactly one of
   the two ever runs.

   TRANSLATE ONLY, NO SCALE. The ruling at 1 (line ~272) forbids scale on a
   surface full of text for a measured reason - it re-rasterises the panel's
   type mid-flight. A longer travel does not change that argument.

   THE CURVE IS THE DEPARTURE'S OWN, INVERTED. A 625px climb at constant speed
   reads as a slide, not an arrival, so the decelerating curve is kept: the
   composer arrives rather than lands. */
@keyframes heroV2ComposerInFromAvatar {
  from {
    opacity: 0;
    transform: translate(var(--hv2-arrive-x, 0px), var(--hv2-arrive-y, 18px));
  }
  to   { opacity: 1; transform: translate(0, 0); }
}

/* The switch is the custom property, set by the rule above when the origin was
   measured - there is deliberately NO second selector here. An earlier draft
   added `animation-name` on `[style*="--hv2-arrive-x"]`, which scored higher
   than the reduced-motion guards and defeated them; it also meant two rules
   fought over one property. One rule, one switch. */

/* ─────────────────────────────────────────────────────────────────────────────
   1b. THE FIRST OPEN IS A GESTURE, NOT A SWAP.

   MEASURED before this, 1440x900, one click on the resting bar:
     stage top      389 -> 189   (-200px, single frame, no interpolation)
     stage height   122 -> 522
     glimpse top    465 -> 665   (+200px)
   At 390x844 the stage went 118 -> 582 and the glimpse 218 -> 682 in the first
   sampled frame (~23ms). The panel's own 300ms heroV2PanelIn did play - opacity
   0 at 65ms, 0.468 at 102ms, 1.0 at 374ms - so the surface faded in correctly
   inside a layout that had already teleported 200px (464px on a phone). That is
   the whole of "it opens abruptly": the animation moves 6px and the geometry
   moves 200. Fading a card in is not the same as opening a composer.

   WHY NOT ANIMATE THE HEIGHT. max-height/height on this surface re-rasterises
   the panel's type on every frame and would re-open the reflow defects fixed at
   §2 and §3 - the log and the field would be re-laid-out mid-flight.

   WHY NOT SCALE. Standing ruling from §1: no scale on a surface full of text.
   Scaling a 720x60 bar into a 720x460 column is a 7.7x vertical stretch.

   SO: A CLIP ANCHORED TO THE BAR, AND A PUSHED GLIMPSE.
   hero-v2.js reads the bar's rect and the panel's rect BEFORE and AFTER the
   click, then writes the bar's own band inside the open panel as
   --hv2-clip-top / --hv2-clip-bottom and the glimpse's displacement as
   --hv2-glimpse-dy. The panel is then revealed growing outward from the band the
   member actually pressed - 200..260 inside the panel on 1440x900, 0..56 on a
   390px phone - while the glimpse starts where it stood and descends into place.
   One axis, one curve, no intermediate width, no second arrival.

   THE STAGE IS DELIBERATELY NOT TRANSLATED, and the rule below is the reason it
   must be stated. The obvious FLIP - move the stage back to its old top and let
   it travel - was built and measured first: it works on a desktop, where the
   centred column shifts the stage's top by 200px, and does NOTHING on a phone,
   where the hero is a flow section and the stage simply grows 118 -> 582. A
   gesture that is invisible on the device with the largest jump is not a fix, so
   the reveal is the primary motion and it is anchored to the pressed control,
   which exists in both layouts. */
html[data-hero-v2][data-hero-v2-signedin][data-hero-v2-opening] .hero-v2-stage {
  animation: none;
}

/* The reveal is anchored to the BAR, not to the panel's top edge.

   MEASURED, 1440x900: the bar sits at y=389; the open panel starts at y=189 and
   ends at 649. The column is CENTRED in the hero, so opening it grows the box in
   both directions - 200px up, 200px down. A reveal from the panel's own top edge
   would therefore start 200px above the control the member just pressed and read
   as the surface jumping upward. The clip starts at the bar's own band and grows
   outward from it, which is the only anchor the eye has.

   /* ONE ANIMATION, NOT TWO. §3 used to give .weya-fab-panel.open its own
   heroV2PanelIn. Two animations on one element is a restart waiting to happen:
   while [data-hero-v2-opening] matched, the reveal won on specificity, and the
   moment the gesture ended the name changed back to heroV2PanelIn and the panel
   faded in a SECOND time - MEASURED opacity 0.55 -> 1, then 0 at 422ms, then 1
   again. So heroV2PanelIn is retired for this layout (see §3) and the reveal is
   the only opening animation the panel has.

   THE SHIPPED OPACITY TRANSITION GOES WITH IT, AND THAT IS A CORRECTION.
   weya-fab.css:182 gives .weya-fab-panel `transition: opacity 0.18s ease`, so
   every open fades the composer in from transparent. MEASURED 60ms into a manual
   open: opacity 0.576 - the panel was more than 40% see-through while the
   drifting orbs sat behind it, which is the translucency §2c removed from the
   background for exactly this reason. A surface a member is about to type into
   is never semi-transparent, and the clip already carries the reveal, so the
   fade is redundant here as well as wrong. Transition off, opacity stays 1: the
   surface is opaque from its first painted pixel and still grows out of the bar.
   The ARRIVAL path loses nothing - the whole stage fades in under
   heroV2ComposerIn, so the panel arrives with its parent. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel {
  opacity: 1;
}

html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel.open {
  transition: none;
  animation: heroV2PanelReveal 340ms cubic-bezier(0.16, 1, 0.30, 1.00) both;
}

@keyframes heroV2PanelReveal {
  from {
    clip-path: inset(var(--hv2-clip-top, 0px) 0
      calc(100% - var(--hv2-clip-bottom, 100%)) 0 round 16px);
  }
  to   { clip-path: inset(0 0 0 0 round 16px); }
}

/* THE GLIMPSE IS PUSHED, NOT TELEPORTED.

   MEASURED, same run: the glance strip below the composer goes 465 -> 665 on a
   desktop and 218 -> 682 on a 390px phone - 464px in one frame, the largest
   single discontinuity on the surface. It cannot be eliminated (its final
   position IS lower), so it is made continuous: the strip starts where it was
   and descends into its new place on the same curve as the panel, emerging from
   under the panel's descending clip edge rather than out of empty space.

   .is-active is not decoration: §4 below sets `animation: none` on
   .hero-forming.is-active and would otherwise win on source order, which is
   exactly what the first build of this rule did - measured animationName: none,
   transform: none, glimpseTop 465 -> 665 in one frame. */
html[data-hero-v2][data-hero-v2-signedin][data-hero-v2-opening] .hero-forming.is-active {
  animation: heroV2GlimpseOpen 340ms cubic-bezier(0.16, 1, 0.30, 1.00) both;
}

@keyframes heroV2GlimpseOpen {
  from { transform: translateY(var(--hv2-glimpse-dy, 0px)); }
  to   { transform: translateY(0); }
}

/* ───────────────────────────────────────────────────────────────────────────────
   2. The composer.
   Same element (#weyaFabRoot > #weyaFab), same handler (togglePanel), same
   panel. It stops being an absolutely-positioned dock and becomes the first
   flow item of the column.
   ─────────────────────────────────────────────────────────────────────────────── */

html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root {
  /* today: position:absolute; bottom:20; right:20; align-items:flex-end */
  position: relative;
  inset: auto;
  bottom: auto;
  right: auto;
  display: flex;
  flex-direction: column;
  align-items: stretch;
  gap: 8px;
  width: 100%;
  min-height: 0;
  pointer-events: none;

  /* THE COMPOSER MUST OUTRANK THE DECORATION, NOT SIT UNDER IT.
     MEASURED: `.floating-orb` carries `z-index: 100` (hero.css:64) - five
     drifting orbs, absolutely positioned in the hero, each with a 36px glow -
     while the whole composer column lives inside `.hero-overlay`, which is
     `z-index: 2` (hero.css:175) and the orbs' SIBLING, not their descendant.
     So the orbs paint over the composer no matter what z-index the composer or
     its root asks for: a child can never escape its parent's stacking context.
     That is why the first attempt (raising .weya-fab-root to 900) measured as
     correct on the root and still showed an orb on top of the tray.
     The overlay is therefore the element that must move, and 900 is the value:
     it clears the orbs at 100, stays under the conversation modal at 2000
     (conversation.css:551) and under the fixed My-rooms chip at 9400, and is far
     below every funnel layer at 9500+. The composer keeps losing to every real
     modal, which is right - decoration should lose to the surface, and the
     surface should lose to a dialog.
     `pointer-events` is untouched, so the orb links stay clickable wherever they
     do not overlap the column; only the paint order changes. */
  z-index: 900;
}

/* Belt and braces: the orbs must also stop competing for the surface itself.
   Raising the overlay fixes the paint order, but an orb is a pointer target
   with `pointer-events: auto` (hero.css:64), so one drifting across the panel
   would still swallow a click meant for the field. Scoped to the signed-in
   hero only; the anonymous page keeps the shipped behaviour untouched. */
html[data-hero-v2][data-hero-v2-signedin] .hero-overlay {
  z-index: 900;
}

/* The bar is the one thing that never shrinks. It is the member's way in. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root > .weya-fab {
  flex: 0 0 auto;
}

/* The bar itself. Not a pill any more: a pill says "button in a corner", a
   rounded rectangle says "type here". 60px tall so the avatar still has room
   to read as her face rather than an icon. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab {
  width: 100%;
  min-height: 60px;
  padding: 0 20px;
  justify-content: flex-start;
  gap: 12px;
  border-radius: 16px;
  font-size: 0.95rem;
  font-weight: 500;
  letter-spacing: 0;
  text-align: left;
  color: var(--text-muted);
  background: rgba(15, 21, 32, 0.92);
  border: 1px solid rgba(45, 212, 191, 0.22);
  box-shadow: 0 10px 34px rgba(0, 0, 0, 0.42), 0 0 0 1px rgba(45, 212, 191, 0.05);
}

html[data-hero-v2][data-hero-v2-signedin] .weya-fab:hover {
  color: var(--text);
  background: rgba(19, 27, 40, 0.96);
  border-color: rgba(45, 212, 191, 0.45);
  transform: none;
}

/* OPEN: THE BAR IS GONE.
   The panel is the composer. Its input row now carries her face (hero-v2.js
   moves the same node in), and the panel's own action row is the header. The
   shipped corner card used the bar as its title bar; in the column a second
   row above the panel saying "Weya" is the same word twice, and the Founder
   asked for the top label to go. Closing the panel brings the bar back, with
   the face restored, exactly as it was.

   Focus safety: closePanel() restores focus to this button. It is only hidden
   while aria-expanded is true, and closePanel() sets aria-expanded="false"
   before its deferred focus() runs — so the button is paintable again by then. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab[aria-expanded="true"] {
  display: none;
}

html[data-hero-v2][data-hero-v2-signedin] .weya-fab-icon-img {
  width: 30px;
  height: 30px;
}

/* Her face, in the field. The same <span class="weya-fab-icon"> that sits in
   the closed bar, moved into #weyaChatComposer while the panel is open. A
   face inside the input row is the composer's identity without a title bar:
   you can see who you are talking to at the point where you type. */
html[data-hero-v2][data-hero-v2-signedin] .hero-v2-composer-avatar {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  flex: 0 0 auto;
  width: 34px;
  height: 34px;
  border-radius: 50%;
  border: 1px solid rgba(45, 212, 191, 0.28);
  background: rgba(45, 212, 191, 0.06);
  overflow: hidden;
}

/* weya-fab.js may have suppressed the travelling face while the hero portrait
   was still on screen (DR-2026-09-19-18 Fix A). In the composer the face IS
   the identity, and the hero portrait is gone by the time this surface is
   painted, so hero-v2.js clears the inline suppression when it moves the node. */
html[data-hero-v2][data-hero-v2-signedin] .hero-v2-composer-avatar .weya-fab-icon-img {
  width: 30px;
  height: 30px;
}

/* The label, and the one state it has.
 
   CLOSED  → "Message Weya…"  the broad-composer read: her face and an
                               invitation on one bar. One click opens the field.
 
   The open state has no bar, so it has no label (§2). The string is the
   shipped chat placeholder (index.html) moved onto the control that opens it;
   no new copy is introduced. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-text {
  flex: 1 1 auto;
  min-width: 0;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
  text-align: left;
  font-size: 0.95rem;
  font-weight: 500;
  letter-spacing: 0;
  color: var(--text-muted);
}

/* ───────────────────────────────────────────────────────────────────────────────
   3. The panel — the column's own body, not a floating card.
   Today: absolute, bottom:58, right:0, width:380, max-height:min(82vh,720px).
   That card could not survive here: it would hang off the hero's bottom edge
   (#hero is overflow:hidden) and put a second anchor 400px from the bar the
   member just touched. In flow, it opens exactly where the conversation
   belongs and the glimpse simply moves down.

   THE HEIGHT CAP IS LOAD-BEARING. Signed in, #hero is 100vh / min-height:640
   and overflow:hidden. Stage = panel + gap 16 + glimpse 44, and the stage caps
   itself at calc(100vh - 132px). On the shortest desktop the hero promises
   that is 508px, so the panel may take 446px — enough for the greeting and a
   readable slice of conversation. The 46px cap keeps taller viewports exactly
   where they were.
   ─────────────────────────────────────────────────────────────────────────────── */

html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel {
  position: static;
  inset: auto;
  bottom: auto;
  right: auto;
  width: 100%;
  max-width: none;
  border-radius: 16px;
  transform: none;
  /* Shrinks before anything else does: the conversation is the part that can
     scroll. min-height:0 is required for a flex child to be allowed to.

     THE FLOOR IS MEASURED, NOT GUESSED. With both disclosures open at 640px the
     column has 424px for panel + glimpse. The panel's non-shrinkable content —
     header 69 + body padding 28 + the understanding note 66 + composer 41 +
     hint 37 + foot 19 + gaps ≈ 339 — is what the composer needs in order to
     stay whole. A 210px panel was measured slicing the input field in half.

     WHY 72vh AND NOT 56vh. At 56vh the panel capped itself at 358px on a 640px
     hero and the message log measured 19px: the opening greeting was a one-line
     sliver. 72vh lets the stage's own 508px cap bind first, so the log gets the
     remaining 107px — the whole greeting, with the option row one scroll away.
     Above 668px the 460px cap binds exactly as it did before this change. */
  flex: 1 1 auto;
  min-height: 278px;
  max-height: min(72vh, 460px);
}

/* BEFORE THE COMPOSITION EXISTS, THE CORNER DOES NOT PAINT THE PANEL.
   The shipped arrival auto-open fires the moment a session lands — well before
   the composer's column exists — and an open 380px card in the bottom corner
   that later becomes a 720px column is exactly the widening the Founder
   retired. The open STATE still belongs to weya-fab.js (unchanged); only the
   paint is deferred, and the panel appears with the composer that owns it.

   visibility, not display: weya-fab.js writes display:flex inline when it
   opens, and the preview does not fight inline state. A hidden element is
   also removed from the tab order, so the deferred surface cannot be reached
   before it exists. */
html[data-hero-v2][data-hero-v2-authed]:not([data-hero-v2-signedin]) .weya-fab-panel {
  visibility: hidden;
  pointer-events: none;
}

/* The panel's own opening is translateY(8px) scale(0.98) - a card rising out
   of a corner. In flow the column is already there, so the scale would read as
   a second arrival. What remains is the same sentence the old hero speaks on
   its way out (§0b): a short lift and a fade, on the release curve. This is
   the "open like the hero used to leave" the walk asked for, and it is also
   what a disclosure in flow should do - arrive, not pop.

   THE ANIMATION LIVES IN §1b NOW, NOT HERE, and there is exactly one of it.
   Splitting the open across two rules - the lift-and-fade here, the bar reveal
   there - is what produced the measured double open: opacity 0.55 -> 1 under the
   reveal, then the animation-name changed back to this one at the end of the
   gesture and the panel faded in from 0 again at 422ms. heroV2PanelReveal
   degrades to this same lift-and-fade when no bar band was measured, so the
   arrival (which nobody clicked for) still gets "arrive, not pop" and the manual
   open gets the gesture. One element, one animation, one owner. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel.open {
  transform: none;
}

/* The panel's own header row keeps its three controls but drops its title: the
   bar directly above it already carries her face and her name, so the <h2> is
   the same word twice in 60 pixels. The header's real job here is the action
   row (New room / reset / close), and that row stays exactly where it is. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel-title {
  /* Not display:none — the h2 is the panel's accessible name source for some
     readers, and removing it would leave the surface unnamed. Visually only. */
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}

/* With the title collapsed the header would shrink to the buttons' own height;
   the shipped 16px top padding was sized for a 1.05rem title beside them. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel-header {
  padding: 12px 14px;
  justify-content: flex-end;
}

/* THE TYPING ROW MUST NEVER BE CUT IN HALF.
   weya-fab.css:549 gives .weya-chat a min-height:220px — fine inside a floating
   card that can be 720px tall, wrong in a column that shares the hero with a
   glimpse. MEASURED with both disclosures open: the panel compressed to 369px
   while its content wanted ~600, and the input row was sliced at the panel's
   bottom edge. Half a text field is the one outcome this surface cannot ship.

   The shipped surface scrolls the WHOLE body (weya-fab.css:324-331), which is
   right for a card floating over a page — you scroll the card to reach the
   field. In a composer the field is the point, so the scroll moves one level
   down: the body stops scrolling, the message log takes it, and the input row
   stays pinned at the panel's foot. This is the behaviour a chat surface has
   when it has a fixed footprint. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-body {
  display: flex;
  flex-direction: column;
  overflow: hidden;
  min-height: 0;
}

html[data-hero-v2][data-hero-v2-signedin] .weya-chat {
  min-height: 0;
  flex: 1 1 auto;
  overflow: hidden;
}

html[data-hero-v2][data-hero-v2-signedin] .weya-chat-messages {
  max-height: none;
  flex: 1 1 auto;
  min-height: 0;
}

/* A LOG THAT CONTINUES BELOW THE FOLD MUST SAY SO.

   MEASURED, 390x844 at 100% with the composer open: the message log is 120px
   tall and holds 243px, so its fold lands 30px into the first intent chip and
   "Just talk" is not painted at all. The log DOES scroll - and its scrollbar is
   0px wide, because it is `thin` and an overlay style that stays unpainted until
   the member scrolls. So the surface was giving no signal whatsoever that the
   greeting continued: the chip read as a rendering fault, a pill sliced across
   its own label, rather than as content waiting below.

   THE HEIGHT IS NOT THE BUG AND IS NOT CHANGED. §6c measured 120px as the
   largest floor that keeps the composer, the understanding note and the field
   whole on a 700px phone, and the intended trade is "the whole greeting, the
   options one scroll away". What was missing is the affordance that makes that
   trade legible.

   SO: THE LOG DISSOLVES AT ITS FOLD, AND ONLY WHEN IT ACTUALLY OVERFLOWS.
   The mask fades the last 28px into the surface instead of ending on a hard
   edge, which is the same treatment §3c already gives the band above the pinned
   composer - one visual language for "there is more, in this direction" rather
   than a second one invented here. hero-v2.js writes data-hv2-more only while
   there is content past the fold, so a short log and a fully-scrolled log paint
   flat. The gradient is in `transparent` and black-alpha only, so it needs no
   per-theme colour and cannot drift from the token set.

   NOT A SCROLLBAR RESTYLE: a painted scrollbar would add a rail to the one
   surface on the page that has no chrome, and on a touch device it would still
   be invisible. The fade reads in both input models. */
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-messages[data-hv2-more] {
  -webkit-mask-image: linear-gradient(to bottom, #000 calc(100% - 28px), transparent 100%);
  mask-image: linear-gradient(to bottom, #000 calc(100% - 28px), transparent 100%);
}

html[data-hero-v2][data-hero-v2-signedin] .weya-chat-composer {
  flex: 0 0 auto;
}

/* ───────────────────────────────────────────────────────────────────────────────
   3b. The tip, across the composer (Founder walk, 2026-11-19).

   The understanding notice is the one place Weya states the deal in plain
   words. In the corner card it was capped at 260px: a narrow column of text
   beside a 380px surface. The composer is 720px, so the cap itself is the
   defect. The sentence now reads as a band the width of the field, with a
   quiet teal backing so it separates from the conversation without becoming
   an alert.

   COLOUR: the text is pinned to #c9d8e6, not var(--text-muted). On the tinted
   band over the panel gradient that measures ~9.4:1; the muted token falls to
   ~2.4:1 in the theme blocks where it ships dark — the same wrong-background
   defect the shipped rule documents in the other direction (PKT-17). The
   light theme overrides below.
   ─────────────────────────────────────────────────────────────────────────────── */
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-understand-note {
  max-width: none;
  width: 100%;
  box-sizing: border-box;
  align-items: center;
  gap: 8px;
  padding: 10px 12px;
  border-radius: 10px;
  background: rgba(45, 212, 191, 0.07);
  border: 1px solid rgba(45, 212, 191, 0.15);
  color: #c9d8e6;
}

/* The close stays a 44px target inside the band; it aligns to the text rather
   than pulling the band taller. */
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-understand-close {
  margin: 0 -4px 0 0;
}

/* THE DISMISS MUST SIT BESIDE THE FIRST LINE, NOT INSIDE THE PARAGRAPH.
   MEASURED at 1440x900 with text at 200%: the note's text box is 128px tall
   (about four lines) while the close is a 44px square, and the band centres its
   children - so the ✕ landed at y=386..430 against text running y=344..472, i.e.
   vertically in the MIDDLE of the paragraph. In the render it reads as a stray
   glyph floating between two words of a sentence ("...than you ✕ expected"),
   which is the worst possible place for a control: it looks like a typo and it
   is nowhere near the edge it dismisses from.
   At 100% the note is one line, the band is 44px, and centring is correct - so
   this is scoped to the two steps where the note wraps, not applied globally.
   `flex-start` pins it to the first line, which is where a reader looks for the
   control and where it stays out of the prose. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] .weya-chat-understand-close,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] .weya-chat-understand-close {
  align-self: flex-start;
}

html[data-hero-v2][data-hero-v2-signedin] .weya-chat-understand-close:hover,
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-understand-close:focus-visible {
  color: #ffffff;
  background: rgba(45, 212, 191, 0.12);
}

/* ───────────────────────────────────────────────────────────────────────────────
   3c. Composer-only appearance (Founder walk, 2026-11-19).

   TWO CONTROLS, ONE FENCE. Text size and theme change the composer and nothing
   else. The attributes live on #weyaFabRoot — the bar and the panel — never on
   the stage, so the glimpse beside it, the hero background and every modal are
   outside the fence by construction. (The stage was the first draft; the
   glimpse lives inside it, so the fence would have leaked.)

   WHY THESE TWO. A surface a member types into is a reading surface: the same
   person who needs 18px in the morning needs it at midnight, and a dark card on
   a dark hero is not always the right glass. Both choices persist per device
   (localStorage) and Reset is a real control, not a shrug. Defaults equal the
   shipped surface — dark, medium — so a member who never opens the tray sees
   exactly what ships today.
   ─────────────────────────────────────────────────────────────────────────────── */

/* The Aa disclosure. Same 34px circle family as reset/close, quiet until
   hover/focus so it never competes with "New room". */
html[data-hero-v2] .weya-fab-appearance {
  background: transparent;
  border: 1.5px solid rgba(45, 212, 191, 0.18);
  color: var(--text-muted);
  width: 34px;
  height: 34px;
  border-radius: 50%;
  display: flex;
  align-items: center;
  justify-content: center;
  cursor: pointer;
  font-family: var(--font);
  font-size: 0.8rem;
  font-weight: 700;
  line-height: 1;
  flex-shrink: 0;
}
html[data-hero-v2] .weya-fab-appearance:hover {
  background: rgba(45, 212, 191, 0.10);
  border-color: var(--teal);
  color: var(--teal);
}
html[data-hero-v2] .weya-fab-appearance:focus-visible {
  outline: 2px solid var(--teal);
  outline-offset: 2px;
}
html[data-hero-v2] .weya-fab-appearance[aria-expanded="true"] {
  background: rgba(45, 212, 191, 0.14);
  border-color: var(--teal);
  color: var(--teal);
}

/* The tray. A compact settings surface anchored under the header, spanning the
   conversation area — not a floating card of arbitrary height.

   WHY IT SPANS INSTEAD OF FLOATING. The first build sized it to its content
   (263px) and anchored it under the header. At 390px that ended at y=484 while
   the input ran 477–519, so 35px of the field peeked out beneath the tray's
   bottom edge — which reads as a rendering fault, not a menu. At 1440 the same
   box covered the log and the field entirely, with nothing telling the eye
   where the settings surface stopped. Neither is a menu; both look broken.

   So the tray now spans from just under the header to the panel's bottom edge,
   and hero-v2.js measures that span (positionTray) rather than hardcoding it,
   because the header's height moves with the site-wide font scale. It covers
   the conversation and the field while open — expected for a settings surface
   you deliberately opened — and closing restores both, because nothing was
   reflowed to make room. That was the failure of the in-flow version: it cost
   158px of a 448px panel and left the log at zero.

   It is a group, never a dialog, so anotherDialogOpen() does not see it. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel-inner {
  position: relative;
}
html[data-hero-v2] .hero-v2-appearance {
  position: absolute;
  /* top and max-height are set by hero-v2.js:positionTray(). The fallback keeps
     the tray inside the panel if it is ever painted before that runs. */
  top: 73px;
  bottom: auto;
  right: 10px;
  left: 10px;
  width: auto;
  max-width: none;
  max-height: 360px;
  /* SCROLL THE TRAY WHEN ITS OWN CHROME CANNOT FIT, RATHER THAN STARVING THE
     CONTROLS. The body has its own scroll (below), which is right at ordinary
     sizes: the head and the foot stay put and the six rows move. But the head,
     the sample and the foot are also text, and they scale with BOTH the page
     (rem) and --hv2-scale. MEASURED at page 200% x tray 200% on a 390px phone:
     head 207px + sample 18 + body 8 + Reset 44 + note 195 = 472 inside a 426px
     tray - the body window was 8px, and ZERO of the 17 controls were usable.
     Scrolling the tray is the legal answer under 1.4.4 and it is the one this
     file already chooses twice (§3, §6); clipping is not. */
  overflow-y: auto;
  overscroll-behavior: contain;
  z-index: 5;
  display: flex;
  flex-direction: column;
  gap: 0;
  margin: 0;
  padding: 0;
  border-radius: 12px;
  border: 1px solid rgba(255, 255, 255, 0.10);
  background: #101a27;
  box-shadow: 0 18px 44px rgba(0, 0, 0, 0.52);
}
html[data-hero-v2] .hero-v2-appearance[hidden] {
  display: none;
}
/* A head, a scrolling body, a foot. Without the head the tray was a border
   around some rows and read as a broken panel; without the foot the "stays on
   this device" line floated loose. Both are fixed; only the body scrolls, so at
   200% the controls stay reachable instead of pushing the note off the edge. */
html[data-hero-v2] .hero-v2-appearance-head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 10px;
  /* At large text the title and the readout cannot share a line. Without this
     the readout was painted past the tray's right edge - MEASURED at page 200%
     x tray 200% on a 390px phone: "READING SETTINGS" wrapped to three lines and
     "40..." was cut off at the border. Wrapping stacks them instead. */
  flex-wrap: wrap;
  flex: 0 0 auto;
  padding: 6px 14px 4px;
}
/* THE TRAY SCALES WITH THE TEXT IT CONTROLS.
   The controls were fixed at 0.6875/0.8125rem while the conversation they govern
   doubled. That is the wrong way round: a member raises text size because they
   cannot read small type, and the tray is the surface they must read to raise it.
   MEASURED before this: at the 200% step the tray's own labels stayed 11px while
   the message copy beside them reached 29px. Now every tray size multiplies by
   the same --hv2-scale the reading tokens use, so the ladder is honest end to end.
   The tray is a scrolling body, so at the top steps it grows and scrolls rather
   than clipping - the legal answer under 1.4.4. */
html[data-hero-v2] .hero-v2-appearance-title {
  font-family: var(--font);
  font-size: calc(0.75rem * var(--hv2-scale, 1));
  font-weight: 700;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  color: var(--text);
  /* It is an <h3> now, so the UA's margin must go: as a span it had none, and a
     default 1em block margin would push the six rows down and re-open the
     clipping defect the scrolling body exists to prevent. */
  margin: 0;
  line-height: 1.3;
}

/* THE EFFECTIVE-SIZE READOUT (syncEffectiveSize in hero-v2.js).
   It carries no visible label of its own - it sits beside the title it qualifies,
   reading "READING SETTINGS   400%" - so it takes the title's own rhythm one step
   quieter: numbers, not words, which is why it is the tabular figure and not the
   uppercase label style. */
html[data-hero-v2] .hero-v2-appearance-eff {
  flex: 0 0 auto;
  font-family: var(--font);
  font-size: calc(0.75rem * var(--hv2-scale, 1));
  font-weight: 600;
  font-variant-numeric: tabular-nums;
  letter-spacing: 0.01em;
  color: var(--teal);
  line-height: 1.3;
}
/* EMPTY MEANS ABSENT, INCLUDING IN THE LAYOUT.
   MEASURED at the site-wide scale of 200%: an empty span still occupies a line
   box, and those ~16px (2rem) were enough to push the six-row body past its
   window - bodyScrollH 170 against a bodyH of 131, so the last row sat under the
   fold of a popover with no scroll affordance. The readout is empty at 100% by
   design, so it must cost nothing there. */
html[data-hero-v2] .hero-v2-appearance-eff:empty {
  display: none;
}
html[data-hero-v2] .hero-v2-appearance-body {
  display: flex;
  flex-direction: column;
  gap: 6px;
  flex: 1 1 auto;
  /* A FLOOR, BECAUSE flex:1 1 auto IS ALLOWED TO RESOLVE TO ZERO.
     MEASURED at page 200% x tray 200% on a 390px phone: the head, the sample and
     the foot had taken the whole tray, and this box - the six reading controls -
     came out 8px tall. Two rows of 66px need ~140, so 120 is a real window rather
     than a token one, and the tray's own scroll (§3c) is what brings it into
     view. A control that exists but has nowhere to be drawn is not a control. */
  min-height: 120px;
  overflow-y: auto;
  overscroll-behavior: contain;
  padding: 2px 14px 6px;
}
html[data-hero-v2] .hero-v2-appearance-row {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 10px;
  /* A ROW MAY WRAP, AND AT LARGE TEXT IT MUST.
     MEASURED at the site-wide scale of 150% plus this tray's own 200% step: the
     label and the segmented control could not share a line, the segment kept its
     min-content width, and the right-hand column was painted outside the tray -
     "TYPE" and "CO..." visible as cut-off stubs at the panel edge while those
     controls were unreachable. Wrapping puts the segment under its own label
     instead of outside the surface. */
  flex-wrap: wrap;
  flex: 0 0 auto;
}
/* TWO COLUMNS ON WIDE TRAYS, ONE ON NARROW.

   MEASURED at 1440x900 with the tray at its shipped single-column shape: six
   rows of 50px + head + note = 375px inside a 377px window, and the body
   scrolled - so "Composer size", the last row, sat below the fold of a popover
   with no scroll affordance. A control a member cannot see is not a control.

   Two columns halve the height (three rows each) and the tray stops covering
   the conversation it is meant to sit beside. `grid-auto-flow: column` with an
   explicit three-row template is deliberate: it fills column one top-to-bottom
   first, so DOM order still equals visual order for a screen reader, instead of
   the left-right interleaving that `row` flow would produce.

   THE COLUMNS MUST BE ALLOWED TO BE NARROWER THAN THEIR CONTENT, or the grid
   grows past the tray instead of the tray staying put. MEASURED at page 150% x
   tray 200%: `1fr` resolves to min-content by default, min-content here is the
   full label + segment pair, and the second column was laid out beyond the
   tray's right edge - cut-off "TYPE" / "CO..." stubs, unreachable controls.
   `minmax(0, 1fr)` lets the track shrink, which is what makes the row's own
   flex-wrap do its job. */
@media (min-width: 769px) {
  html[data-hero-v2] .hero-v2-appearance-body {
    display: grid;
    grid-auto-flow: column;
    grid-template-rows: repeat(3, auto);
    grid-auto-columns: minmax(0, 1fr);
    column-gap: 18px;
    row-gap: 6px;
    align-items: center;
  }
}
html[data-hero-v2] .hero-v2-appearance-label {
  font-size: calc(0.6875rem * var(--hv2-scale, 1));
  font-weight: 700;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  color: var(--text-muted);
  white-space: nowrap;
}
html[data-hero-v2] .hero-v2-appearance-note {
  flex: 0 0 auto;
  margin: 0;
  padding: 2px 14px 8px;
  font-size: calc(0.6875rem * var(--hv2-scale, 1));
  line-height: 1.4;
  color: var(--text-dim);
  text-align: center;
}

/* THE LIVE SAMPLE. It must read as the conversation it previews, not as a note
   about the conversation, so it uses the reading tokens and the conversation
   bubble's own surface - the same --hv2-reading, --hv2-font and line box the
   .weya-chat-msg it stands in for uses. Bounded and scrollable so that at 200%
   it cannot become the thing that pushes the six controls off the tray.
   `aria-hidden` is correct here: it is the same sentence the member can already
   read in the log, repeated as a visual preview, and announcing it twice would
   be noise rather than information. */
/* THE SAMPLE YIELDS TO THE CONTROLS, ALWAYS.

   MEASURED at page 200% x tray 200% on a 390px phone: the sample (font-size
   var(--hv2-reading), capped at 4.5em of a doubled em) grew to 190px of a 426px
   tray, the six rows were pushed below the fold of a body with no scroll
   affordance, and ZERO of the 17 body controls were reachable - the sample
   demonstrating the text size had made the control that sets it unusable.

   The order is not negotiable: the sample is illustrative, the controls are the
   surface. So the sample is the only flexible item in the tray (flex: 0 1 auto
   with min-height:0, the two things a flex child needs to be allowed to shrink),
   and the body keeps its own scroll. At comfortable sizes nothing changes - the
   sample has room and takes it. */
html[data-hero-v2] .hero-v2-appearance-sample {
  flex: 0 1 auto;
  min-height: 0;
  overflow-y: auto;
  overscroll-behavior: contain;
  margin: 0 14px 4px;
  padding: 8px 10px;
  border-radius: 10px;
  border: 1px solid rgba(45, 212, 191, 0.18);
  background: rgba(45, 212, 191, 0.06);
  font-family: var(--hv2-font, var(--font));
  font-size: var(--hv2-reading, 0.92rem);
  line-height: 1.45;
  color: var(--text);
  text-align: left;
}
html[data-hero-v2] .hero-v2-appearance-seg {
  /* The segment may not exceed its row, and its buttons may wrap inside it.
     MEASURED at page 150% x tray 200%: four size buttons wanted 340px in a
     300px column and painted past the tray's edge. */
  display: inline-flex;
  flex-wrap: wrap;
  max-width: 100%;
  min-width: 0;
  gap: 2px;
  padding: 2px;
  border-radius: 999px;
  border: 1px solid rgba(255, 255, 255, 0.10);
  background: rgba(0, 0, 0, 0.18);
}
html[data-hero-v2] .hero-v2-appearance-seg button {
  min-width: 44px;
  min-height: 44px;
  padding: 0 8px;
  border: 0;
  border-radius: 999px;
  background: transparent;
  color: var(--text-muted);
  font-family: var(--font);
  font-size: calc(0.8125rem * var(--hv2-scale, 1));
  font-weight: 600;
  cursor: pointer;
}
html[data-hero-v2] .hero-v2-appearance-seg button:hover {
  color: var(--text);
}
html[data-hero-v2] .hero-v2-appearance-seg button:focus-visible {
  outline: 2px solid var(--teal);
  outline-offset: 1px;
}
html[data-hero-v2] .hero-v2-appearance-seg button[aria-pressed="true"] {
  background: rgba(45, 212, 191, 0.88);
  color: #04121a;
  font-weight: 700;
}
html[data-hero-v2] .hero-v2-appearance-reset {
  align-self: center;
  flex: 0 0 auto;
  min-height: 44px;
  padding: 0 6px;
  margin-left: -2px;
  border: 0;
  border-radius: 8px;
  background: transparent;
  color: var(--teal);
  font-family: var(--font);
  font-size: 0.75rem;
  font-weight: 600;
  text-decoration: underline;
  text-underline-offset: 3px;
  white-space: nowrap;
  cursor: pointer;
}
html[data-hero-v2] .hero-v2-appearance-reset:hover {
  background: rgba(45, 212, 191, 0.10);
}
html[data-hero-v2] .hero-v2-appearance-reset:focus-visible {
  outline: 2px solid var(--teal);
  outline-offset: 2px;
}

/* Text size. ONE MULTIPLIER, WCAG 1.4.4 AT THE TOP STEP.

   The earlier build hardcoded three token sets (0.84/0.92/1.02rem) whose top
   step was ~121% - a comfort control. The ladder is now a plain multiplier on
   the shipped reading sizes, `--hv2-scale`, set by hero-v2.js from the stored
   step: 0.875 / 1 / 1.25 / 1.5 / 2. The multiplier is applied to REM, not to
   a computed pixel value, so it compounds correctly with the site-wide
   --font-scale (variables.css:246) instead of fighting it: a member who has
   also raised the site scale gets both, which is what they asked for.

   The tray's four buttons are 87 / 100 / 150 / 200. 125 is reachable
   programmatically and by the site bar's own scale; it is not in the tray
   because five segmented buttons in one row is a puzzle, not a control. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root {
  --hv2-scale: 1;
  --hv2-reading: calc(0.92rem * var(--hv2-scale));
  --hv2-input: calc(0.95rem * var(--hv2-scale));
  --hv2-meta: calc(0.8125rem * var(--hv2-scale));
}

/* THE INPUT NEVER GOES BELOW 16px. iOS Safari zooms the whole viewport when a
   focused text input is smaller than 16px, which is a disorienting jump at the
   exact moment the member starts typing (Blueprint §4.5). 16px is the floor at
   EVERY scale step, including 87%. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-input {
  font-size: max(16px, var(--hv2-input, 0.95rem));
}
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-msg {
  font-size: var(--hv2-reading, 0.92rem);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-understand-note {
  font-size: var(--hv2-reading, 0.875rem);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-option-label,
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-option-desc {
  font-size: var(--hv2-reading, 0.875rem);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-type-hint,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-foot-note,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-status,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-capability-note {
  font-size: var(--hv2-meta, 0.8125rem);
}

/* THE CONVERSATION TAKES THE GROWTH, NOT THE COMPOSER. At 200% the reading
   copy doubles and the panel is capped by the stage; without this the field
   and the Send button would be pushed out of the surface the member is
   enlarging text in order to read. The log is the part that can scroll, so it
   is the part that yields - and the composer row stays pinned at the bottom of
   the panel where it is reachable. */
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-messages {
  max-height: none;
  min-height: 92px;
}
/* THE PINNED COMPOSER MUST OCCLUDE WHAT SCROLLS UNDER IT.
   MEASURED before this fix: `.weya-chat-composer` was `position: sticky` with
   `background: inherit`, and `inherit` resolved to TRANSPARENT - its parent
   `.weya-chat` carries no fill, so the inherited value was `rgba(0,0,0,0)`.
   At 100% nothing scrolls and the defect is invisible. At the top two steps on a
   phone the panel body DOES scroll, and the foot note was measured passing
   straight through the composer band: elementFromPoint 4px below the composer's
   top edge returned `weya-fab-foot-note` at 390x844 and 390x700, at both 150%
   and 200%, with or without the glimpse open. That is live text painted under a
   pinned control - the member reads a sentence through a text field.
   The matrix confirms the blast radius is exactly those eight combinations:
   every desktop size at every step, and mobile at 100%, are unaffected because
   their body never scrolls.
   The fill is the panel's OWN bottom stop (dark #0d1117, light #eef4f4), not a
   new colour: the panel is a subtle vertical gradient and the composer sits at
   its foot, so an opaque band in the terminal colour is indistinguishable from
   the surface it covers. The band therefore hides content without reading as a
   toolbar that was added to the design.
   `::before` adds the short fade above it so text dissolves into the band
   instead of being sliced by a hard edge - the standard treatment for a pinned
   footer over a scrolling list. It is decoration only: pointer-events are off so
   it can never intercept a click meant for the log.

   THE BAND MUST REACH THE PANEL'S FOOT, AND THE BODY'S PADDING STOPPED IT.
   MEASURED after the fill was added: `.weya-fab-body` carries
   `padding: 14px 18px 16px` (weya-fab.css:325), and `bottom: 0` on a sticky
   child resolves to the padding EDGE, not the border edge - so the composer
   parked 17px above the panel's inner bottom and a 17px strip of scrolling
   content stayed visible BELOW it. elementFromPoint in that strip returned
   `.weya-chat-understand-text`, i.e. live sentences readable underneath a
   pinned control, which is the same defect the fill was meant to close, just
   relocated. The preview states its own vertical rhythm through the panel, so
   the body's bottom padding is dropped here and re-expressed as a padding on
   the composer's own interior instead: the field keeps its breathing room and
   the band that occludes reaches the edge. LEFT/RIGHT padding is untouched -
   only the bottom value moved.
   Dark and light share one rule because the fill above already handles colour. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-body {
  padding-bottom: 0;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-composer {
  position: sticky;
  bottom: 0;
  z-index: 2;
  padding: 0 0 16px;
  background-color: #0d1117;
}
/* The fade is clipped to the composer's own padding box, so it must sit exactly
   on top of the band and not over the 16px of restored breathing room. */
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-composer::before {
  content: '';
  position: absolute;
  left: 0;
  right: 0;
  bottom: 100%;
  height: 16px;
  background: linear-gradient(to top, #0d1117, rgba(13, 17, 23, 0));
  pointer-events: none;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-composer {
  background-color: #eef4f4;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-composer::before {
  background: linear-gradient(to top, #eef4f4, rgba(238, 244, 244, 0));
}

/* AT THE TOP TWO STEPS THE PANEL ITSELF MUST GROW.
   MEASURED at 200% on a 900px viewport: the tip 150 + composer 60 + type hint
   56 + status 31 + foot note 75 = 372px of non-scrolling text, inside a 389px
   body. The log was left 4px - a slit, not a conversation - and that is a loss
   of content at exactly the zoom level WCAG 1.4.4 (Resize Text) requires to
   work. The 460px cap is a layout preference calibrated for default text, not a
   law, and it must yield to the text.
   Clarified: the panel is allowed to use the stage, which is capped at
   calc(100vh - 132px) and therefore still inside the hero. Everything below it
   keeps its own floor, and when even the stage cannot hold the doubled text the
   body scrolls - scrolling is a legal answer under 1.4.4; clipping is not. */
/* DESKTOP ONLY, AND THAT SCOPING IS THE FIX, NOT A TIDY-UP.
   calc(100vh - 132px) is a DESKTOP formula: it assumes the composer is centred
   in a 100vh hero that clips its own overflow, so the panel may use the stage.
   On a phone the hero is a flow section that grows (responsive.css) and the
   .mobile-sticky-cta bar is position:fixed at the bottom of the VIEWPORT. The
   unscoped rule gave the panel 712px starting at y=146 - a bottom edge of 858
   on an 844 viewport - and the fixed bar then sat on top of the input.
   MEASURED at 390x844, text 200%: elementFromPoint at the centre of
   #weyaChatInput returned .mobile-sticky-cta. The field was painted, focusable,
   and completely unusable: you could type into something you could not see.
   Scoping the growth to >=769px restores the desktop behaviour and leaves the
   phone to the mobile rule below, which knows about the bar. */
@media (min-width: 769px) {
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] .weya-fab-panel,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] .weya-fab-panel {
    max-height: calc(100vh - 132px);
  }
}
/* The glimpse is illustration, not conversation. At these steps it collapses to
   its 46px bar so the text above it has the room instead. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] ~ .hero-forming.is-active,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] ~ .hero-forming.is-active,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] ~ .hero-forming.is-active.is-open,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] ~ .hero-forming.is-active.is-open {
  min-height: 46px;
  flex: 0 0 auto;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] ~ .hero-forming .hero-forming-list,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] ~ .hero-forming .hero-forming-list {
  max-height: 0;
}

/* THE SEND BUTTON IS PART OF THE READING LADDER, NOT OUTSIDE IT.
   MEASURED before this, at the 200% step on 1440x900: the input field is 60px
   tall running 30.4px type, and the Send button beside it stayed exactly 64x40
   with 14px type at ALL FOUR steps - it is the only control in the composer that
   did not move. The primary action of the surface therefore rendered at less
   than half the size of the text it submits, and became the smallest interactive
   target on screen. A member raises text size because they cannot read small
   type; a control that refuses to follow the ladder reads as a rendering fault.
   `align-self: stretch` is the height half: the button already sits in the
   composer's flex row, so it takes that row's height (the input's) instead of a
   hard 40px, with no cap needed because the row is itself bounded by the panel.
   The font-size is the other half. */
html[data-hero-v2][data-hero-v2-signedin] .weya-chat-send {
  align-self: stretch;
  font-size: calc(0.875rem * var(--hv2-scale, 1));
}

/* ON A PHONE AT THE TOP TWO STEPS, THE BODY TAKES THE SCROLL AND THE COMPOSER
   STAYS PINNED.
   MEASURED at 390x844, text 200%: the chat column's own children want 1254px
   (log 551, understanding note 406, composer 60, type hint 93, status 31, foot
   note 113) inside a 419px column. Nothing can be arranged to fit, and
   .weya-chat is overflow:hidden by design (test/hero-v2.test.js check 11), so
   whatever does not fit is CLIPPED: the note measured as a 22px sliver with
   212px of text behind it, and the composer painted over the cut.
   Two wrong levers were measured first, and both are recorded here so neither is
   tried again. (1) Capping the note: it turned the sliver explicit and freed
   nothing. (2) Lifting the panel's 72vh cap so the panel grows: at 200% that
   makes the panel 1416px and puts the composer ~1200px down the page - it fixes
   the clipping by hiding the primary action below the fold, which is the same
   failure in the other direction.
   So the answer is the one 3c already states for this surface: when the content
   cannot fit, the BODY scrolls and the input row stays pinned at the panel's
   foot. That is the shipped behaviour (weya-fab.css:324-331) restored for these
   two steps only. `.weya-chat` must stop being the flex child that eats the
   height (it is what clipped the note), so it becomes content-sized and lets
   the body own the scroll. Scrolling is the legal answer under 1.4.4; clipping
   is not; and the member's field stays on screen throughout.
   The panel keeps its 72vh/520px cap - the comfort envelope is unchanged. */
@media (max-width: 768px) {
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] .weya-fab-body,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] .weya-fab-body {
    overflow-y: auto;
    overscroll-behavior: contain;
  }
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] .weya-chat,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] .weya-chat {
    flex: 0 0 auto;
    overflow: visible;
  }
}

/* ON A PHONE AT THE TOP TWO STEPS, SEND DROPS BELOW THE FIELD.
   MEASURED at 390x844: the composer row gives the field 177px of text width at
   100% and only 141px at 200%, because the Send button grows with the type and
   takes its share of a row that never wraps. 141px at 30.4px type is about four
   characters - and the placeholder alone lays out at 228px, so the member read
   "Message V", sliced at the field edge. A text field too narrow to show the
   word for what it is has stopped being a text field.
   `text-overflow: ellipsis` was tried first and does not work here: Chromium
   forces `overflow: clip` on a text input and ignores the declaration (measured
   - the computed value stayed `clip` even when set inline), so the only honest
   fix is to stop squeezing the field. The row wraps and the input takes the full
   width; Send keeps its natural scaled size and aligns right, so it still reads
   as the primary action rather than becoming a full-width banner.
   MEASURED after: field 141 -> 287px at 200%, 157 -> 287px at 150%; the
   placeholder fits at both, Send stays 96x55 / 80x46, and the composer still
   sits inside the panel. The cost is ~105px of composer height at these two
   steps, paid out of the body's own scroll - which is exactly the trade this
   section already makes. Desktop is untouched: 1440px never wraps. */
@media (max-width: 768px) {
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] .weya-chat-composer,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] .weya-chat-composer {
    flex-wrap: wrap;
  }
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] .weya-fab-input,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] .weya-fab-input {
    flex: 1 0 100%;
  }
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="3"] .weya-chat-send,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-scale="4"] .weya-chat-send {
    margin-left: auto;
  }
}

/* ───────────────────────────────────────────────────────────────────────────────
   TEXT SPACING — WCAG 2.2 SC 1.4.12 (AA).

   The four values are the ones the success criterion names, not round numbers:
   line height 1.5, letter spacing 0.12em, word spacing 0.16em, and paragraph
   spacing 2em. Applying them is a member right, so this is a control rather than
   a stylesheet a member would have to write.

   WHY EACH PROPERTY IS SET HERE AND NOT INHERITED. The panel's reading copy
   comes from weya-chat.js, which sets its own line-height on bubbles. The
   scoped selector below carries four class tokens and one element, so it
   outranks every shipped `.weya-chat-msg` rule on specificity alone - no
   importance flag, which this file forbids (test/hero-v2.test.js check 12).
   MEASURED at the 200% step: line 44.16px, letter 3.53px, word 4.71px, i.e.
   exactly 1.5 / 0.12em / 0.16em of the 29.44px reading size. The one place
   inline styles do win is the "similar room" listing card, which weya-chat.js
   builds with style attributes; that card is not reading copy, it is a card,
   and leaving it out of this rule is deliberate.
   ─────────────────────────────────────────────────────────────────────────────── */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-chat-msg,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-chat-understand-note,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-chat-option-label,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-chat-option-desc,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-fab-input,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-chat-type-hint,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .hero-v2-appearance-sample,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-fab-foot-note {
  line-height: 1.5;
  letter-spacing: 0.12em;
  word-spacing: 0.16em;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-chat-msg + .weya-chat-msg,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-spacing="relaxed"] .weya-chat-option + .weya-chat-option {
  margin-top: 2em;
}

/* ───────────────────────────────────────────────────────────────────────────────
   COMPOSER SIZE — the Founder's "compose size itself".

   The SURFACE envelope only: how much conversation is on screen. Three values,
   each expressed against the viewport rather than as a fixed pixel height, so
   the choice means the same thing on a 900px laptop and a 1200px monitor. Type
   is untouched here - see PREF_PANEL_KEY in hero-v2.js for why the two controls
   must stay independent.

   THE :not() GUARDS ARE THE POINT, NOT DEFENSIVE NOISE. The 150%/200% growth
   rule above has the SAME specificity as these two (five attribute/class tokens
   and one element each), so source order alone would decide - and these come
   later, which would let "compact" shrink the panel back to 380px and re-crush
   the message log to a slit at exactly the zoom level WCAG 1.4.4 requires to
   work. A comfort preference must never be able to undo a conformance
   mechanism. Excluding the top two text steps makes that explicit instead of
   accidental. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-panel="compact"]:not([data-hero-v2-composer-scale="3"]):not([data-hero-v2-composer-scale="4"]) .weya-fab-panel {
  max-height: min(58vh, 380px);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-panel="spacious"]:not([data-hero-v2-composer-scale="3"]):not([data-hero-v2-composer-scale="4"]) .weya-fab-panel {
  max-height: min(82vh, 620px);
}

/* LIGHT THEME. The composer becomes a pale glass card on the same dark hero —
   the page around it does not change. Every colour here is chosen for a light
   surface; the shipped dark values would drop to ~1.2:1 on it.
   MEASURED: #0e2230 on #f5f9f9 = 16.1:1; #44586a on #f5f9f9 = 7.4:1;
   #33475a on #eef4f4 = 8.3:1. The teal is darkened to #0f766e for text
   (5.4:1 on white) instead of the dark theme's bright #2dd4bf (1.8:1).

   THE TOKENS ARE THE FIX FOR INLINE STYLES. weya-chat.js gives every option
   pill `color: var(--teal)` inline (makeOptionButton), and its description
   reads var(--text-muted); no selector can beat an inline declaration short of
   the cascade's last resort. Re-declaring the tokens ON the composer root
   resolves both at
   the point of use, and the choice stays inside the fence: the glimpse and
   the rest of the page keep the dark-theme values. */
/* THE LIGHT BLOCK MUST CARRY --text AND --text-dim TOO.
   MEASURED before this fix, at 1440x900 with the tray open on the light theme:
     .hero-v2-appearance-title  -> rgb(226,234,243) on #ffffff = 1.21:1
     .hero-v2-appearance-note   -> rgb(132,146,168) on #ffffff = 3.15:1
   Both are the DARK theme's tokens. The block below remapped only --teal and
   --text-muted, so every rule that reads var(--text) or var(--text-dim) kept a
   near-white value and the light surface silently rendered them invisible. That
   is the accessibility panel failing 1.4.3 on its own title - the exact class of
   defect the strong-contrast block at 3d already avoids by remapping --text
   explicitly (it sets #0a1016). This is the same fix, one tier down.
   MEASURED after: title 16.3:1, note 9.59:1, label 7.37:1. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] {
  --teal: #0f766e;
  --text: #0e2230;
  --text-muted: #44586a;
  --text-dim: #33475a;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab {
  background: rgba(250, 253, 253, 0.97);
  border-color: rgba(13, 148, 136, 0.30);
  color: #44586a;
  box-shadow: 0 12px 34px rgba(2, 12, 18, 0.36);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab:hover {
  background: #ffffff;
  border-color: rgba(13, 148, 136, 0.55);
  color: #0e2230;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-text {
  color: #44586a;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-panel {
  background: linear-gradient(180deg, #fbfdfd 0%, #eef4f4 100%);
  border-color: rgba(13, 148, 136, 0.24);
  box-shadow: 0 24px 70px rgba(2, 12, 18, 0.44), 0 0 0 1px rgba(13, 148, 136, 0.06);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-panel-header {
  background: rgba(255, 255, 255, 0.86);
  border-bottom-color: rgba(15, 23, 42, 0.08);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-panel-title {
  color: #0e2230;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-new-room {
  color: #0f766e;
  border-color: rgba(13, 148, 136, 0.35);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-new-room:hover {
  background: rgba(13, 148, 136, 0.08);
  border-color: #0f766e;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-reset,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-appearance {
  color: #44586a;
  border-color: rgba(15, 23, 42, 0.16);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-close {
  background: rgba(13, 148, 136, 0.08);
  border-color: rgba(13, 148, 136, 0.30);
  color: #0f766e;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-msg-assistant {
  background: #0f766e;
  border-color: #0d9488;
  color: #f0fdfa;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-msg-user {
  background: rgba(13, 148, 136, 0.12);
  border-color: rgba(13, 148, 136, 0.28);
  color: #0e2230;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-msg-label {
  color: #0f766e;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-input {
  background: #ffffff;
  border-color: rgba(15, 23, 42, 0.14);
  color: #0e2230;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-input::placeholder {
  color: #62748a;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-input:focus {
  border-color: #0d9488;
  box-shadow: 0 0 0 3px rgba(13, 148, 136, 0.14);
}
/* The send button inherits `background: var(--teal); color: #04121a` from
   .weya-fab-btn. With the light token that would be dark text on dark teal;
   the filled button needs its own light pair. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-btn {
  background: #0f766e;
  border-color: #0f766e;
  color: #f0fdfa;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-btn:hover {
  background: #0d6a63;
  border-color: #0d6a63;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-btn-ghost {
  background: transparent;
  color: #0f766e;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-type-hint {
  color: #33475a;
  border-top-color: rgba(15, 23, 42, 0.10);
  border-bottom-color: rgba(15, 23, 42, 0.10);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-foot-note {
  color: #5b6d7d;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-fab-status {
  color: #44586a;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-understand-note {
  background: rgba(13, 148, 136, 0.10);
  border-color: rgba(13, 148, 136, 0.22);
  color: #123b3a;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-understand-close:hover,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .weya-chat-understand-close:focus-visible {
  color: #06201f;
  background: rgba(13, 148, 136, 0.14);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .hero-v2-composer-avatar {
  background: #ffffff;
  border-color: rgba(13, 148, 136, 0.28);
}
/* THE LIGHT TRAY NEEDS AN ELEVATION CUE ITS COLOUR CANNOT PROVIDE.
   MEASURED: the tray is #ffffff on a panel that tops out at #fbfdfd - a 1.02:1
   value difference. At that separation the old 10%-alpha hairline was the only
   boundary, and it is barely above the noise floor of an antialiased 1px line.
   The dark theme does not have this problem (16,26,39 on 15,21,32 reads as a
   raised card), which is why the light surface looked like a bordered region
   rather than a popover. A surface cannot be raised by colour here, so it is
   raised the other two ways: a defined stroke and a shadow tight enough to read
   as contact with the panel rather than a page-level drop. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .hero-v2-appearance {
  background: #ffffff;
  border-color: rgba(15, 23, 42, 0.16);
  box-shadow: 0 1px 2px rgba(15, 23, 42, 0.06), 0 12px 32px rgba(15, 23, 42, 0.14);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .hero-v2-appearance-label {
  color: #44586a;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .hero-v2-appearance-seg {
  border-color: rgba(15, 23, 42, 0.12);
  background: #eef4f4;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .hero-v2-appearance-seg button {
  color: #44586a;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .hero-v2-appearance-seg button[aria-pressed="true"] {
  background: #0f766e;
  color: #f0fdfa;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"] .hero-v2-appearance-reset {
  color: #0f766e;
}

/* ───────────────────────────────────────────────────────────────────────────────
   3d. Strong contrast (P2) and the readable typeface (P4).

   STRONG IS THE AAA STEP, NOT A NEW PALETTE. The composer already meets 1.4.3
   (Contrast, Minimum) on both themes; this raises every secondary token to at
   least 7:1 so the surface also meets 1.4.6 (Contrast, Enhanced). Only the
   tokens change - the layout, the spacing and the copy do not, because a
   member who asks for more contrast is asking for legibility, not a redesign.
   MEASURED on the dark surface: #f4f8fc on #101a27 = 17.6:1; #d8e2ee = 12.9:1;
   borders rgba(255,255,255,0.42). On light: #0a1016 on #fbfdfd = 18.4:1;
   #2b3a47 = 10.1:1.
   ─────────────────────────────────────────────────────────────────────────────── */

html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-contrast="strong"] {
  --text: #f4f8fc;
  --text-muted: #d8e2ee;
  --text-dim: #c8d4e2;
  --teal: #5eead4;
  --border: rgba(255, 255, 255, 0.42);
  --border-hi: rgba(255, 255, 255, 0.60);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-contrast="strong"] .weya-fab-panel {
  border-color: rgba(255, 255, 255, 0.42);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-contrast="strong"] .weya-chat-msg-assistant {
  background: #0d9488;
  border-color: #5eead4;
  color: #ffffff;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-contrast="strong"] .weya-chat-msg-user {
  background: rgba(94, 234, 212, 0.22);
  border-color: rgba(94, 234, 212, 0.62);
  color: #ffffff;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-contrast="strong"] .weya-chat-understand-note {
  background: rgba(94, 234, 212, 0.16);
  border-color: rgba(94, 234, 212, 0.55);
  color: #f4f8fc;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-contrast="strong"] .weya-fab-input {
  border-color: rgba(255, 255, 255, 0.42);
}
/* Light + strong: the light palette's dark ink, pushed to near-black, with the
   dark teal held at 7:1 rather than the standard step's 5.4:1. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"][data-hero-v2-composer-contrast="strong"] {
  --text: #0a1016;
  --text-muted: #2b3a47;
  --text-dim: #33424f;
  --teal: #0b5f59;
  --border: rgba(10, 16, 22, 0.42);
  --border-hi: rgba(10, 16, 22, 0.62);
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"][data-hero-v2-composer-contrast="strong"] .weya-chat-msg-assistant {
  background: #0b5f59;
  border-color: #0b5f59;
  color: #ffffff;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"][data-hero-v2-composer-contrast="strong"] .weya-chat-msg-user {
  background: rgba(11, 95, 89, 0.16);
  border-color: rgba(11, 95, 89, 0.55);
  color: #0a1016;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"][data-hero-v2-composer-contrast="strong"] .weya-fab-btn {
  background: #0b5f59;
  border-color: #0b5f59;
  color: #ffffff;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-theme="light"][data-hero-v2-composer-contrast="strong"] .weya-chat-understand-note {
  background: rgba(11, 95, 89, 0.12);
  border-color: rgba(11, 95, 89, 0.45);
  color: #0a1016;
}

/* READABLE TYPEFACE. Atkinson Hyperlegible is already self-hosted for the
   site-wide bar (variables.css:352-366), so this sets a family and nothing
   else: no request, no new asset, no fallback flash on a cold cache beyond the
   one the site bar already pays. Applied to the composer's own text only. */
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] {
  --hv2-font: 'Atkinson Hyperlegible', 'Outfit', sans-serif;
}
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] .weya-chat-msg,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] .weya-chat-understand-note,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] .weya-chat-option-label,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] .weya-chat-option-desc,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] .weya-fab-input,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] .weya-chat-type-hint,
html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root[data-hero-v2-composer-font="readable"] .weya-fab-foot-note {
  font-family: var(--hv2-font);
  /* Atkinson's x-height is smaller than Outfit's; one step of tracking keeps
     the line rhythm close to the standard typeface so the swap is a
     legibility gain rather than a reflow. */
  letter-spacing: 0.01em;
}

/* ───────────────────────────────────────────────────────────────────────────────
   FORCED COLOURS — WCAG 2.2 SC 1.4.1 (Use of Color) and EN 301 549 §11.2,
   which is the standard that makes Windows High Contrast a requirement rather
   than a courtesy.

   NO STYLESHEET ON THIS SITE HANDLED IT (grep: zero `forced-colors` blocks), and
   the composer is the surface where the failure is worst: every affordance in it
   is drawn with colour - the teal "Send", the teal-bordered option pills, the
   teal focus ring, the teal-on-translucent option labels. In forced-colours mode
   the UA replaces the palette, so those translucent borders and coloured labels
   collapse toward the same system colour and the composer's controls stop being
   distinguishable from its text.

   THE FIX IS NOT MORE COLOUR, IT IS SYSTEM COLOUR TOKENS. `CanvasText`,
   `Canvas`, `Highlight`, `ButtonText` are the keywords the UA guarantees to
   remap. Borders are re-declared so every control keeps an edge, and the focus
   ring switches to `Highlight` so it survives the palette override.

   Scoped to the composer, like every other rule in this file: the hero, the
   glimpse and every modal keep the shipped behaviour, because the preview's
   promise is that it changes the composer and nothing else. */
@media (forced-colors: active) {
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-input,
  html[data-hero-v2][data-hero-v2-signedin] .weya-chat-msg,
  html[data-hero-v2][data-hero-v2-signedin] .weya-chat-understand-note,
  html[data-hero-v2][data-hero-v2-signedin] .weya-chat-option,
  html[data-hero-v2][data-hero-v2-signedin] .hero-v2-appearance,
  html[data-hero-v2][data-hero-v2-signedin] .hero-v2-appearance-seg {
    border: 1px solid CanvasText;
    background: Canvas;
    color: CanvasText;
  }
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-btn,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-new-room {
    border: 1px solid ButtonText;
    background: ButtonFace;
    color: ButtonText;
  }
  /* The selected step must not be conveyed by fill alone (1.4.1): it gets a
     thicker system border as well, which is visible with every palette. */
  html[data-hero-v2][data-hero-v2-signedin] .hero-v2-appearance-seg button[aria-pressed="true"] {
    border: 2px solid Highlight;
    background: Highlight;
    color: HighlightText;
  }
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-input:focus,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-input:focus-visible,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-btn:focus-visible,
  html[data-hero-v2][data-hero-v2-signedin] .hero-v2-appearance-seg button:focus-visible,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-appearance:focus-visible {
    outline: 2px solid Highlight;
    outline-offset: 2px;
  }
}

/* ───────────────────────────────────────────────────────────────────────────────
   4. The glimpse, under the composer.
   Founder correction (2026-11-19): this is a COLLAPSED BUTTON showing rooms
   Weya made for different niches — for the member to understand the range of
   what she does. It is illustration, not activity and not suggestions. So it
   is one quiet line, and it opens only on the member's click (DR-2026-10-19-03
   already owns that gate; this file does not touch the gate).

   The frosted backing stays. DR-2026-09-18-10 added it because the list
   floated over the ambient blob motion and muted copy fell to 3.73:1. That
   finding does not go away because the column moved, so the backing stays —
   slimmed to a bar while collapsed, full when the list is open.
   ─────────────────────────────────────────────────────────────────────────────── */

html[data-hero-v2][data-hero-v2-signedin] .hero-forming.is-active {
  /* today: padding 32px 36px; radius 24px; gap 14px */
  padding: 14px 18px;
  border-radius: 14px;
  gap: 12px;
  animation: none; /* the arrival already landed; a second fadeUp is one too many */
  opacity: 1;
}

/* Open: the list needs the height the closed bar did not. */
html[data-hero-v2][data-hero-v2-signedin] .hero-forming.is-active.is-open {
  padding: 18px 20px;
  border-radius: 16px;
}

/* The glimpse is the last link in the shrink chain. It yields height to the
   conversation above it, and its list scrolls inside whatever it is given. */
html[data-hero-v2][data-hero-v2-signedin] .hero-forming.is-active {
  flex: 0 1 auto;
  min-height: 46px;
  overflow: hidden;
}

/* Open, it keeps a usable floor: the heading plus a slice of list. MEASURED —
   without this floor the glimpse collapsed to a sliver at 640px and, worse, the
   flex algorithm took the panel down with it until the input field was sliced.
   The secondary disclosure yields first; it does not yield to nothing. */
html[data-hero-v2][data-hero-v2-signedin] .hero-forming.is-active.is-open {
  display: flex;
  flex-direction: column;
  min-height: 132px;
}

/* 340px of scrollable list would push the column past the hero's floor. The
   list keeps its own scroll, it just scrolls in a shorter window here — and it
   is allowed to shrink below its content so the column can always fit. */
html[data-hero-v2][data-hero-v2-signedin] .hero-forming-list {
  max-height: min(38vh, 300px);
  min-height: 0;
  flex: 1 1 auto;
}

/* The heading is the gate. Left-aligned inside a bar, with the +/- at the
   right edge, is what a disclosure looks like; centring it would make it read
   as a caption. Copy is untouched, byte for byte. */
html[data-hero-v2][data-hero-v2-signedin] .hero-forming-heading {
  font-size: 0.8125rem;
}

/* ───────────────────────────────────────────────────────────────────────────────
   5. "My rooms" — top right, under the chip (Founder instruction, 2026-11-19).
   hero-v2.js creates it and points it at window.openS5Modal(); this is only
   where it sits and how it looks. Same pill language as .s5-header-chip, one
   step quieter, so the corner reads as one cluster rather than two controls.

   The chip is min-height:44px at top:16, but MEASURED at 62px tall (8px padding
   around a 44px inner tap target). It therefore occupies 16..78, not 16..60, so
   the 8px gap under it is 86. Without a chip (a session the server has not
   answered yet) the button takes the chip's own slot rather than leaving a hole.
   ─────────────────────────────────────────────────────────────────────────────── */

html[data-hero-v2] .hero-v2-myrooms {
  position: fixed;
  top: 86px;
  right: 20px;
  z-index: 9400;

  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 18px;

  border-radius: 50px;
  border: 1px solid rgba(45, 212, 191, 0.22);
  background: rgba(15, 21, 32, 0.85);
  backdrop-filter: blur(8px);
  -webkit-backdrop-filter: blur(8px);

  color: var(--text);
  font-family: var(--font);
  font-size: 0.8125rem;
  font-weight: 600;
  letter-spacing: 0.01em;
  white-space: nowrap;
  cursor: pointer;

  box-shadow: 0 6px 24px rgba(0, 0, 0, 0.34);
  transition: background 0.18s ease, border-color 0.18s ease;
}

html[data-hero-v2] .hero-v2-myrooms:hover {
  background: rgba(45, 212, 191, 0.14);
  border-color: rgba(45, 212, 191, 0.45);
}

html[data-hero-v2] .hero-v2-myrooms:focus-visible {
  outline: 2px solid var(--teal);
  outline-offset: 2px;
}

/* No chip on screen: take the slot the chip would have used. :has is the only
   way to ask a body-level question from CSS; where it is unsupported the button
   simply keeps the 86px offset, which is a gap, never an overlap. */
html[data-hero-v2]:not(:has(.s5-header-chip)) .hero-v2-myrooms {
  top: 16px;
}

/* ───────────────────────────────────────────────────────────────────────────────
   6. Mobile — the same column, simply shorter.
   responsive.css:4-29 already turns the hero into a flow section at ≤768px
   (height:auto, min-height:100vh, padding 100px 0 60px), which is exactly what
   "everything stays inside the hero" needs: the keyboard pushes the section,
   not a fixed sheet. Two things must be undone, and only two.

   (1) .hero-split is column-REVERSE there, so the avatar came first. The
       avatar is gone; the column must read top-down.
   (2) weya-fab.css:798-810 makes .weya-fab-root position:FIXED at mobile so the
       pill follows the member down the page. That was right for a corner dock.
       It is wrong for a composer that belongs to the column — it would follow
       the member past the hero, which is the one thing this change must not do.
   ─────────────────────────────────────────────────────────────────────────────── */

@media (max-width: 768px) {
  html[data-hero-v2][data-hero-v2-signedin] .hero-split {
    flex-direction: column;
    align-items: stretch;
    gap: 0;
    max-width: none;
    /* The mobile hero is a flow section that GROWS (responsive.css:5 height:auto),
       so the desktop height cap must be lifted. Capping it here would clip the
       column instead of letting the page scroll — the opposite of what mobile
       needs. */
    max-height: none;
  }

  /* The corner stack needs vertical room the desktop column did not. MEASURED at
     390: the chip occupies 16..78 and "My rooms" 86..126, while the shipped
     overlay put the composer's top edge at 120 — a 6px collision, visible in the
     first mobile capture. 46px instead of 20 clears both and costs nothing,
     because the section is height:auto and simply gets 26px taller. */
  html[data-hero-v2][data-hero-v2-signedin] .hero-overlay {
    padding-top: 46px;
  }

  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-root {
    position: relative;
    inset: auto;
    bottom: auto;
    right: auto;
    z-index: auto;
    width: 100%;
  }

  html[data-hero-v2][data-hero-v2-signedin] .weya-fab {
    min-height: 56px;
    font-size: 0.92rem;
  }

  /* A bottom sheet is the wrong shape in flow. The panel keeps its cap but it
     is now a viewport fraction of a section that can grow, so the cap can be
     generous.

     MEASURED at 390: the shipped 62vh/260px-wide tip made the panel 520px and
     the column 646px, which put the glimpse 21px behind the fixed mobile CTA
     bar. 54vh cleared the bar but starved the message log to 56px — a clipped
     greeting, which is not a conversation.

     The width-spanning tip (§3b) is 107px instead of the old ~150px, and that
     is the room this uses. At 72vh the panel is 520px, the column 582px, and
     the glimpse ends 56px above the fixed CTA at 390x844; the message log
     measures 121px — the whole greeting, options one scroll away. The 520px
     cap keeps the composer from becoming the page on tall phones.

     On a 700px-tall phone the same rule gives the log 105px instead of 21px.
     The glimpse then starts under the fixed CTA and is reached by scrolling;
     that is the right trade for the surface the member is actually typing
     into. */
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel {
    width: 100%;
    max-height: min(72vh, 520px);
  }

  html[data-hero-v2][data-hero-v2-signedin] .hero-forming-list {
    max-height: min(46vh, 320px);
  }

  /* The corner still stacks: chip at 16 (62px tall, measured), My rooms under
     it with an 8px gap, so 86. */
  html[data-hero-v2] .hero-v2-myrooms {
    top: 86px;
    right: 16px;
    min-height: 40px;
    padding: 0 14px;
    font-size: 0.78rem;
  }

  html[data-hero-v2]:not(:has(.s5-header-chip)) .hero-v2-myrooms {
    top: 16px;
  }
}

/* ───────────────────────────────────────────────────────────────────────────────
   7. Reduced motion.
   The composer's new choreography is switched off — the layout still swaps, it
   simply does so without the departure/entrance frames. The panel's opening
   animation goes with it. Nothing else in this file animates.

   Every selector below is still gated on a session phase (signedin / exiting),
   so a reduced-motion ANONYMOUS page is untouched: hero-weya-col keeps its
   shipped fadeUp and the corner FAB keeps its own behaviour. */
@media (prefers-reduced-motion: reduce) {
  /* SPECIFICITY IS LOAD-BEARING HERE. The animated selectors carry
     :not([data-hero-v2-opened]) and an attribute test, which scores (0,4,1) or
     (0,5,1). A plain (0,3,1) `animation: none` LOSES to them - that is not a
     style preference, it is how the cascade resolves, and it meant a member who
     asked for reduced motion was still given the composer's travel.
     MEASURED 2026-11-20: `heroV2ComposerInFromAvatar` was applied under
     prefers-reduced-motion before this fix. The :not() below restores parity of
     specificity, which is cheaper than an override-with-priority and keeps the
     stylesheet's no-brute-force rule intact. */
  html[data-hero-v2][data-hero-v2-signedin]:not([data-hero-v2-opened]) .hero-v2-stage,
  html[data-hero-v2][data-hero-v2-signedin] .hero-v2-stage,
  html[data-hero-v2][data-hero-v2-signedin] .weya-fab-panel.open,
  html[data-hero-v2][data-hero-v2-exiting] .hero-intro.is-retired,
  html[data-hero-v2][data-hero-v2-exiting] .hero-cta-row[data-hero-v2-retired="1"],
  html[data-hero-v2][data-hero-v2-exiting] .hero-weya-col,
  html[data-hero-v2][data-hero-v2-exiting] .weya-fab-root {
    animation: none;
  }
}

/* visual-prefs.js's own switch (the tree reads 'reduce', not 'reduced'). */
html[data-hero-v2][data-hero-v2-signedin][data-motion="reduce"]:not([data-hero-v2-opened]) .hero-v2-stage,
html[data-hero-v2][data-hero-v2-signedin][data-motion="reduce"] .hero-v2-stage,
html[data-hero-v2][data-hero-v2-signedin][data-motion="reduce"] .weya-fab-panel.open,
html[data-hero-v2][data-hero-v2-exiting][data-motion="reduce"] .hero-intro.is-retired,
html[data-hero-v2][data-hero-v2-exiting][data-motion="reduce"] .hero-cta-row[data-hero-v2-retired="1"],
html[data-hero-v2][data-hero-v2-exiting][data-motion="reduce"] .hero-weya-col,
html[data-hero-v2][data-hero-v2-exiting][data-motion="reduce"] .weya-fab-root {
  animation: none;
}

/* The first-open gesture is switched off by the same two switches. It is
   [data-hero-v2-opening] rather than [data-hero-v2-signedin], so it needs its own
   line: the signed-in selectors above do not cover it, and a member who asked
   for reduced motion must not receive a 200px travel on the first click into a
   surface they have just been given. */
@media (prefers-reduced-motion: reduce) {
  html[data-hero-v2][data-hero-v2-signedin][data-hero-v2-opening] .hero-v2-stage,
  html[data-hero-v2][data-hero-v2-signedin][data-hero-v2-opening] .weya-fab-panel.open {
    animation: none;
    clip-path: none;
  }
}
html[data-hero-v2][data-hero-v2-signedin][data-hero-v2-opening][data-motion="reduce"] .hero-v2-stage,
html[data-hero-v2][data-hero-v2-signedin][data-hero-v2-opening][data-motion="reduce"] .weya-fab-panel.open {
  animation: none;
  clip-path: none;
}

/* ONCE THE GESTURE HAS RUN, THE ARRIVAL ANIMATION MUST NOT REPLAY.
   heroV2ComposerIn is keyed on [data-hero-v2-signedin] alone. Removing
   [data-hero-v2-opening] at the end of the gesture would re-satisfy that selector
   and restart a 520ms fade on a surface that has already arrived - the second
   arrival §1 rules out. [data-hero-v2-opened] is written once, when the first
   gesture ENDS, and stays for the life of the page.
   DELIBERATELY NO RULE HERE. The base selector already excludes it
   (`:not([data-hero-v2-opened])`), and a second rule at this point in the file
   would tie on specificity with §1b's opening animation and win on source order
   - which is exactly the bug that made the first build's gesture invisible on a
   desktop while the panel still revealed on a phone. One selector, one owner. */
