/* The character's position is attached directly to document scroll. */
html{scroll-padding-top:32px;scroll-behavior:auto!important}
/* The layout the travel needs — half the viewport kept clear for her to cross,
   and the scene itself placed by the travel transform — is a desktop layout,
   so it is stated at a desktop width only. These four rules used to sit
   unconditionally in a sheet that loads last, which meant a phone reserved
   51vw of a 390px screen for the companion and left 162px to read in, no
   matter what the phone block further down this file or in experience.css
   asked for. A media query adds no specificity: an unconditional rule in a
   later sheet beats a @media rule in an earlier one, every time. */
@media(min-width:761px){
 .chapter,.tail,.close{padding-top:180px;padding-bottom:180px}
 .chapter.scene-left,.tail.scene-left,.close.scene-left{padding-left:51vw;padding-right:7.5vw}
 .hero{padding-top:120px;padding-bottom:150px}
 .companion-scene{width:43vw;height:76vh}
}
/* She travels at every width. Only her size is a question of screen: the
   half-viewport lane above is a desktop idea, the phone size is below. */
.companion-scene{left:0;right:auto;top:0;transform:translate3d(calc(var(--travel-x,75vw) - 50%),calc(var(--travel-y,50vh) - 50%),0) scale(var(--travel-scale,1));transform-origin:center;transition:color .3s;will-change:transform}
.motion-booting .companion-scene{visibility:hidden}
.motion-booting .particle-cloud{visibility:hidden}
.avatar-object{--scene-x:0px!important;--scene-y:0px!important;--scene-scale:1!important}
.at-demo .avatar-object{--scene-scale:1!important}
.avatar-touch{position:absolute;inset:0;border:0;border-radius:44%;background:transparent;z-index:3;cursor:pointer;pointer-events:auto;color:inherit}
.avatar-touch:focus-visible{outline:1px solid currentColor;outline-offset:8px}
.avatar-touch:active{background:#ffffff08}
.avatar-object.is-reacting .avatar-float{animation:companion-nod .8s ease-in-out}
.companion-response{position:absolute;z-index:5;left:8%;right:8%;bottom:4%;border:1px solid var(--color-grey-2);border-radius:16px;background:var(--color-white);color:var(--color-black);padding:20px 22px;box-shadow:0 10px 40px #00000016;pointer-events:auto;font-size:var(--fs-body-m);line-height:var(--lh);opacity:0;visibility:hidden;transform:translateY(8px);transition:opacity .25s,transform .25s,visibility .25s}
.avatar-speech{z-index:5}
.has-response .companion-response{opacity:1;visibility:visible;transform:none}
.response-action{display:inline-flex;align-items:center;gap:8px;margin-top:16px;border:0;padding:0;font:inherit;font-size:var(--fs-cta);letter-spacing:var(--ls);text-transform:uppercase;cursor:pointer;background:none;color:inherit;transition:gap 150ms var(--emraude-ease)}
.response-action:hover{gap:12px}
.response-close{position:absolute;right:7px;top:5px;background:none;border:0;padding:6px 10px;cursor:pointer;font-size:20px;line-height:1;color:inherit}
.response-text{padding-right:10px}
.has-response .scene-caption{opacity:0}
.has-response .keywords{opacity:0;visibility:hidden}
.journey-status{background:#FFFFFFE8;padding:7px 10px;border-radius:999px;left:calc(4.6vw - 10px)}
.dark-section .journey-status{background:#000000ED}
.traveling .keywords{opacity:.5}
.traveling .companion-response{opacity:0;visibility:hidden}
/* Pressing the caption used to draw a hard rule around whatever the companion
   was naming. It gets the card she speaks from at the close instead: a grey-1
   hairline, a generous radius and a shadow that reads as height.

   Every target left is a whole container with nothing beside it, so the card
   reaches past its edge as a spread shadow — no padding, so nothing inside it
   moves, and no pseudo-element, so a target that hides its own overflow cannot
   clip it. There was a second, lifted shape for a single item sitting inside a
   grid or a list, where a spread printed a white band across the neighbour;
   those chapters no longer point at anything, so it has gone with them. */
.is-highlighted{outline:0!important;transition:box-shadow .45s var(--emraude-ease),background-color .45s var(--emraude-ease),border-color .45s var(--emraude-ease)}
.cards.is-highlighted,.process.is-highlighted,.emraude-approach.is-highlighted,.phone.is-highlighted{
  box-shadow:0 0 0 var(--mat,18px) #FFFFFFEC,0 0 0 calc(var(--mat,18px) + 1px) var(--color-grey-1),0 28px 64px -36px #5C5D5F59}
/* The phone brings its own fill and radius and keeps them.
   The open grids take the card's, and step back whichever of their own outer
   hairlines would otherwise sit just inside its edge. */
.cards.is-highlighted,.process.is-highlighted,.emraude-approach.is-highlighted{border-radius:16px;background-color:#FFFFFFEC;border-top-color:transparent}
.cards.is-highlighted .card:nth-last-child(-n+2),.process.is-highlighted .card:last-child{border-bottom-color:transparent}
@media(max-width:760px){.is-highlighted{--mat:11px}}
@keyframes companion-nod{0%,100%{transform:translateY(0) rotate(0)}30%{transform:translateY(7px) rotate(3deg)}65%{transform:translateY(-5px) rotate(-2deg)}}
@media(min-width:1600px){.chapter.scene-left,.tail.scene-left,.close.scene-left{padding-left:51vw;padding-right:max(7.5vw,calc((100vw - 1400px)/2))}.companion-scene{width:43vw;right:auto}}
@media(max-width:1100px) and (min-width:761px){.chapter.scene-left,.tail.scene-left,.close.scene-left{padding-left:51vw;padding-right:5vw}.companion-scene{width:45vw}}
/* On a phone the companion docks instead of travelling, so this layer only
   has to undo what the travel rule at the top of this file asserts on her —
   left, top, width, height and the transform itself. The dock, and every
   other mobile decision, is the phone block in experience.css; this file
   used to restate all of it differently and win by load order. */
@media(max-width:760px){
 /* Her horizontal pose is a fraction of the viewport, which on a desktop puts
    her in one half or the other. At 72vw wide on a phone the same fraction
    hangs her off the edge — 64px past it at the close, with her own body 15px
    out, which is why the ending had her cropped against the send button. The
    clamp keeps her whole on screen at every chapter: her left edge between 0
    and the 28vw that is left over. */
 /* The close is side by side on a desktop — the dialogue on one half, her on
    the other. A phone stacks it instead: she slides down out of the card as
    the arrival ramps, so she ends standing below it rather than across its
    input rows. The ramp is the one the whole ending already runs on, so this
    is part of that movement rather than a jump at the end of it. */
 .companion-scene{width:72vw;height:34vh;
   transform:translate3d(clamp(0px,calc(var(--travel-x,75vw) - 50%),28vw),
     calc(var(--travel-y,50vh) - 50%),0)
     scale(calc(var(--travel-scale,1) * (1 - var(--arrival,0)*.18)))}
}
@media(max-width:360px){
 .companion-scene{width:68vw;height:36vh}
 .avatar-object{width:88px;height:108px}
}

