/* ==========================================================================
   Riddhi Weds Purvang
   Mobile-first. Artwork does the visual work; CSS positions and reveals it.

   Geometry note: every sprite is placed in % of the PSD's 1000x1500 canvas,
   taken from its actual layer bounding box. That is why the composition
   holds at any width without per-breakpoint repositioning.
   ========================================================================== */

:root{
  /* Sampled from the PSD opening artwork */
  --paper:      #f4efe4;
  --ink:        #6b4a3f;
  --ink-soft:   #8a6a5c;
  --gold:       #b98f57;

  --art-w: 1000;      /* PSD canvas width  */
  --art-h: 1500;      /* PSD canvas height */

  /* Slide-to-slide gap — zeroed per owner request 2026-09-12. Was
     clamp(20px, 4vh, 56px); see the SEAM block below for why a gap existed
     in the first place (the ground/paper surface still shows through
     everywhere else, so removing it here is safe — it only removes the
     card-to-card breathing room, not the connective surface underneath). */
  --slide-gap: 0px;

  /* Opening timings — measured from R2's source video (6.155s @30fps) */
  --t-converge: 2.00s;   /* doves fly in                    */
  --t-slit:     2.50s;   /* centre slit first visible       */
  --t-tear:     1.75s;   /* 2.50 -> 4.25 widening           */
  --t-peel:     1.50s;   /* 4.50 -> 6.00 halves peel open   */
  --t-total:    6.155s;

  --ease-fly:  cubic-bezier(.4,0,.2,1);
  --ease-peel: cubic-bezier(.16,1,.3,1);
  --ease-rev:  cubic-bezier(.22,.61,.36,1);
  /* easeOutExpo — measured from the R4 reference's own stylesheet. Used for
     scene arrival: covers most of the distance at once, then settles slowly. */
  --ease-arrive: cubic-bezier(.16,1,.3,1);
}

*{box-sizing:border-box}

html{
  scroll-behavior:smooth;
  /* The opening locks scrolling with body{overflow:hidden}. Releasing it at
     handover makes the scrollbar appear, which narrows the viewport and
     shifts the centred column left — a measured 7.67px jump on desktop.
     Reserving the gutter permanently removes the shift. */
  scrollbar-gutter:stable;
  /* Belt-and-suspenders alongside script.js's finish() fix (search that
     file for "overflow-anchor" for the full story): disables the browser's
     own CSS Scroll Anchoring, which silently shifts scrollY to compensate
     when off-screen content changes size above the anchor point. That
     compensation can be the FULL size of the change, not a small nudge —
     which is what made scene3's video-trigger observer fire from a
     transient scroll position that was never real. finish()'s instant
     scrollTo fixed the specific transition that caused it; this removes
     the general mechanism so nothing else on the page can do the same
     thing some other way. */
  overflow-anchor:none;
}

body{
  margin:0;
  background:var(--paper);
  color:var(--ink);
  font-family:'Aladin', Georgia, serif;
  -webkit-font-smoothing:antialiased;
  overflow-x:hidden;
}

img{display:block;max-width:100%}

/* Woo Multi Currency plugin — 2026-09-17 ("pls remove the inr and usd
   option from this page only"). The plugin injects a floating INR/USD
   switcher (.woo-multi-currency, class "wmc-sidebar") into every page's
   wp_footer() sitewide, including this one -- Block #40 in
   pikaaso-migration.php deliberately still fires wp_footer() (for
   LiteSpeed/GA4/Rank Math) even though it skips get_header()/get_footer(),
   so the plugin's own footer hook still runs here too. This stylesheet is
   ALREADY scoped to this page only (Block #40 enqueues it only when
   get_page_template_slug() is this template), so hiding it here is
   page-scoped without touching the plugin or any other page that uses it. */
.woo-multi-currency{display:none !important}

/* ==========================================================================
   SCENE 0 — OPENING
   ========================================================================== */
/* Deliberately NOT opaque. The tear has to reveal the real page underneath,
   the way R2's does — so the ground here is the body's own paper colour and
   Scene 1 sits behind it, visible through the opening as it grows. The two
   halves are opaque artwork, so nothing shows until the tear cuts them. */
.opening{
  position:fixed; inset:0; z-index:50;
  display:grid; place-items:center;
  overflow:hidden;
  transition:opacity .6s var(--ease-rev), visibility .6s;   /* 0.6s handover */
}
.opening.is-done{opacity:0; visibility:hidden; pointer-events:none}

/* The stage is a 2:3 box scaled to COVER the viewport, then centred. Every
   child positions in % of THIS box, so the seam, doves, ribbon and corner
   florals stay locked to the artwork no matter the screen shape. The art
   crops top/bottom (never left/right), preserving the seam and corners.

   width = max(100vw, 100vh * 1000/1500) is the cover formula. */
.opening__stage{
  position:absolute; top:50%; left:50%;
  transform:translate(-50%,-50%);
  width:max(100vw, 66.667vh);
  aspect-ratio: var(--art-w) / var(--art-h);

  /* The overlay is transparent so the tear can reveal the real page. On
     desktop the scene column is WIDER than this card, so without a mask
     Scene 1 would peek out around it before the tear even starts. This paints
     the paper ground everywhere outside the card, so only what the tear opens
     is ever visible. On mobile the card already exceeds the viewport, so this
     falls outside the screen and costs nothing. */
  box-shadow:0 0 0 100vmax var(--paper);
}

/* The paper halves live inside this SVG. Geometry is the PSD's own:
   Paper1 x0-507, paper2 x485-1000. They overlap by 22px at the centre and
   that overlap IS the seam — the tear opens along x=496, its midpoint.
   preserveAspectRatio="none" because the stage is already an exact 2:3 box;
   it guarantees full coverage with no sub-pixel letterbox seam. */
.opening__paper{
  position:absolute; inset:0;
  width:100%; height:100%; display:block;
}
#peelL,#peelR{will-change:transform}

/* --- dove-group: real illustrated asset the owner supplied on green screen.
   v3 (2026-09-14): owner correction on v2 — the idle state's `deco-hover`
   lift/tilt (a rigid transform on the whole static image) read as
   "shaking," not as the birds' own wing motion, and the birds were too
   small. Both <img>s are now real animated WebPs sourced directly from the
   GIF's own frames (see index.html for the full frame-range rationale) —
   idle genuinely flaps its wings via its own frame data, so NO CSS
   animation/transform belongs on either element any more; anything added
   here would fight motion that's already baked into the asset.

   Box: aspect-ratio still matches the asset's own crop (384x520, portrait
   ~0.74) — width enlarged 38.5%->48% ("increase the bird sizes"), with
   top/left recomputed so the box's CENTRE stays fixed (left 50%/top 47.6%
   of stage) as it grew, rather than only expanding downward/rightward. */
.dove-group{
  position:absolute; left:26%; top:25.9%; width:48%;
  aspect-ratio: 384 / 520;
  opacity:0; transform:scale(.7);
  transition:opacity var(--t-converge) var(--ease-fly),
             transform var(--t-converge) var(--ease-fly);
}
.is-ready .dove-group{ opacity:1; transform:scale(1); }

/* Fast, separate fade for when script.js finishes the untie playback and
   dismisses the group before the tear starts — deliberately NOT
   var(--t-converge) (2.0s, tuned for the slow initial fly-in). Shortened
   .4s->.15s (2026-09-14, "Opening page New.mp4" reference): the tear must
   start almost immediately after the pull finishes, not after a second
   visible pause. .is-finishing wins on specificity over the base rule
   above, overriding just the transition duration. JS removes the element
   from the flow entirely (hidden, not just opacity:0) once this completes,
   per the owner's earlier "must not still be visible/intercepting after
   open" correction. */
.is-finishing .dove-group{
  opacity:0;
  transition:opacity .15s ease;
}

/* Both <img>s just share position/size — each is a self-contained animated
   WebP now (idle loops its own wing-flap, tap plays its own pull-apart
   narrative once), so neither needs or should get any CSS-driven motion. */
.dove-group__art{
  position:absolute; inset:0;
  width:100%; height:100%;
}
/* Real bug, found 2026-09-14 while debugging v3's idle/tap overlap looking
   like a smeared extra ribbon: the global `img{display:block}` reset above
   (an AUTHOR-origin rule) silently wins over the browser's own
   `[hidden]{display:none}` (a USER-AGENT-origin rule) — author rules beat
   user-agent rules on ANY property they both set, regardless of selector
   specificity. So #doveAnim's `hidden` attribute was never actually hiding
   it — both <img>s have been painting on top of each other since v2, just
   invisibly, because v2's two starting frames happened to be identical
   poses. v3's idle loop (frames 0-19) and tap clip (starting at frame 20)
   are NOT identical, which is what made the overlap visible and caught
   this. Fix: re-assert display:none for hidden .dove-group__art elements
   as an author rule of our own, so it actually wins. */
.dove-group__art[hidden]{display:none}

/* Doves-flying-with-the-tear (2026-09-15) -- see index.html for the full
   "why". Position measured, not eyeballed: PSD x/y derived from the source
   frame's crop origin through the SAME 1.25x scale factor the established
   dove-group box already uses (260,388.5 + source_px*1.25 -- see
   recrop_doves.py). RE-MEASURED same day alongside the v2 re-crop (owner
   correction: "still i am seeing half pigeons" -- see index.html) --
   box/aspect-ratio below match the v2 crop (153x140, was 160x92: extended
   for the full tail, narrowed on the inner edge to stop short of the
   ribbon), not the original. opacity AND transform are both set by
   script.js as plain inline styles every render() frame, continuously
   computed the same way glowIn/glowOut already are for #tearGlow -- not a
   CSS class/transition, so there's one fade formula to reason about instead
   of a formula for the ribbon plus a separate transition curve for these
   that would need to be kept in sync by eye. transform (not left/top) is
   what tracks the peel drift, same reasoning as #peelL/#peelR already use:
   transform is compositor-only, left/top are not. */
.opening__dove-fly{
  position:absolute; top:31.9%; width:19.125%; aspect-ratio:153/140;
  opacity:0; pointer-events:none;
}
.opening__dove-fly--l{left:27.875%}
.opening__dove-fly--r{left:55%}

/* --- tap affordance --- */
.opening__prompt{
  position:absolute; left:50%; bottom:12%;
  transform:translateX(-50%);
  background:none; border:0; cursor:pointer;
  font-family:inherit; font-size:clamp(.95rem,4vw,1.3rem);
  letter-spacing:.22em; text-transform:lowercase;
  color:var(--ink-soft);
  padding:.8em 1.4em;
  animation:breathe 2.6s ease-in-out infinite;
}
.opening__prompt:focus-visible{outline:2px solid var(--gold); outline-offset:3px}
.is-ready .opening__prompt{opacity:1}
.is-driven .opening__prompt{
  opacity:0; pointer-events:none; animation:none; transition:opacity .3s;
}
@keyframes breathe{0%,100%{opacity:.55}50%{opacity:1}}

/* Tear sparkle burst (2026-09-14) — see index.html for why this exists.
   Compound selector overrides the shared `.reveal{opacity:0;transform:
   translateY(18px)}` base the SAME way the scene sparkles do (REVEAL
   SPARKLE, below) — a sparkle starts from scale(0), not translated down —
   except these carry no `.reveal` class at all: they're triggered directly
   by script.js's tear clock, not by IntersectionObserver/scroll, so there's
   nothing to override in the first place. `.opening__spark--N` sets
   position/size/stagger exactly like `.s3sparkle--N` does; `vw` rather than
   `cqw` because `.opening__stage` (unlike `.scene`) has no
   container-type:inline-size context to resolve `cqw` against — `.opening__
   prompt`'s own font-size two rules up already uses the same `vw` unit for
   the same reason. */
.opening__spark{opacity:0; transform:scale(0)}
.opening__spark.is-firing{
  animation-name:sparkle-twinkle;
  animation-duration:1s;
  animation-timing-function:ease-out;
  animation-fill-mode:both;
}
.opening__spark--1{top:8%;  left:44%; width:clamp(16px, 3.6vw, 28px); animation-delay:0ms}
.opening__spark--2{top:8%;  left:56%; width:clamp(15px, 3.3vw, 25px); animation-delay:60ms}
.opening__spark--3{top:26%; left:41%; width:clamp(18px, 4.0vw, 32px); animation-delay:120ms}
.opening__spark--4{top:26%; left:59%; width:clamp(16px, 3.6vw, 28px); animation-delay:180ms}
.opening__spark--5{top:46%; left:43%; width:clamp(17px, 3.8vw, 30px); animation-delay:240ms}
.opening__spark--6{top:46%; left:57%; width:clamp(15px, 3.4vw, 26px); animation-delay:300ms}
.opening__spark--7{top:66%; left:41%; width:clamp(18px, 4.0vw, 32px); animation-delay:360ms}
.opening__spark--8{top:66%; left:59%; width:clamp(16px, 3.6vw, 28px); animation-delay:420ms}

/* Falling petals (2026-09-15, "still opening... not good... research online
   and recheck the references" — direct finding from re-checking the live
   reference site: it rains small petals as its paper opens, ours had
   nothing falling at all). Pure CSS shape, no new image asset: two opposite
   corners fully rounded and two square reads as a simple petal/leaf
   silhouette at this size. Falls via `transform` only (translate + rotate),
   matching this project's motion rule (MOTION.md — transform/opacity only,
   structurally incapable of causing layout shift); `top`/`left` below are
   each petal's STATIC starting point, with the fall itself entirely a
   transform animated from there. `.is-falling` is added once, directly by
   script.js's own tear clock (at T_FULL, a beat ahead of the sparkle burst
   at T_PEEL) — not `.reveal`/`.is-in`, same reasoning as `.opening__spark`:
   this needs to fire off the tear's own progress, not off scrolling. */
.opening__petal{
  position:absolute; top:-6%;
  width:12px; height:12px;
  background:#eec3cf;
  border-radius:0 100% 0 100%;
  opacity:0; pointer-events:none;
  box-shadow:0 0 3px rgba(180,110,130,.35);
}
.opening__petal.is-falling{
  animation-name:petal-fall;
  animation-timing-function:ease-in;
  animation-fill-mode:both;
}
@keyframes petal-fall{
  0%   {opacity:0;  transform:translate(0,0)         rotate(0deg)}
  12%  {opacity:.85}
  40%  {transform:translate(3vw, 45vh)  rotate(120deg)}
  70%  {transform:translate(-2vw, 80vh) rotate(220deg)}
  100% {opacity:0;  transform:translate(2vw, 118vh)  rotate(300deg)}
}
.opening__petal--1{left:10%; width:11px; height:11px; animation-duration:1.7s; animation-delay:0ms}
.opening__petal--2{left:22%; width:14px; height:14px; animation-duration:1.9s; animation-delay:90ms}
.opening__petal--3{left:35%; width:10px; height:10px; animation-duration:1.6s; animation-delay:180ms}
.opening__petal--4{left:48%; width:13px; height:13px; animation-duration:2.0s; animation-delay:60ms}
.opening__petal--5{left:60%; width:11px; height:11px; animation-duration:1.8s; animation-delay:220ms}
.opening__petal--6{left:72%; width:15px; height:15px; animation-duration:1.7s; animation-delay:140ms}
.opening__petal--7{left:84%; width:10px; height:10px; animation-duration:1.9s; animation-delay:40ms}
.opening__petal--8{left:93%; width:12px; height:12px; animation-duration:2.1s; animation-delay:260ms}

/* ==========================================================================
   MAIN — R1's continuous vertical scroll
   ========================================================================== */
/* Visible from the first paint — the opening's paper halves cover it until
   the tear cuts them, and what shows through the tear must be the real page,
   not a stand-in. The reveal of the *text* is still held until handover. */
.invite{opacity:1}

/* Each scene is one full-bleed illustrated panel. No snap, no parallax —
   R1 has neither. The scroll boundary IS the transition.

   container-type gives us cqw units, so every text size and position below
   is a direct percentage of the PSD's 1000px canvas and scales exactly with
   the artwork at any width. 52.1px on a 1000px canvas == 5.21cqw. */
/* ONE SLIDE = ONE SCREEN.
   The artwork is 2:3, so height = width x 1.5. Left at full width, a slide
   was 1425 x 2138 on a 1440x900 window — 2.38 screens, with the text in the
   top 25% and 1.44 screens of painting below it before the next slide. That
   is what made the slide-to-slide movement feel wrong: the R4 reference runs
   ~0.9 screens per section, so one gesture takes you section to section,
   while ours took two and a half through mostly-static illustration.

   Capping the width at 66.667vh makes height exactly 100vh — the whole
   painting, title to foreground, in a single screen.

   `width:max(100%, 66.667vh)` — revised 2026-09-18 ("first slide should be
   adjusted to full screen height, no gaps between slides"). The comment
   this replaced claimed mobile was untouched ("100% wins") because a
   375px-wide card was "already 562px tall inside an 812px viewport" — that
   was the bug, not a safe case: 562px is SHORTER than 812px, so the next
   scene was visible below the first with zero scroll (reported via
   screenshot). A same-day `min-height` fix on `.card` closed the gap with
   blank paper instead of more art — reverted, "not at all look good".
   This is the real fix: reuse the SAME cover formula the opening stage
   already proves out (`.opening__stage`, above) instead of inventing a
   second one. When 66.667vh > 100%, `.scene` grows wider than its
   card — height follows via `.scene__art`'s own aspect-ratio below, always
   landing on exactly 100vh — and gets centred and cropped by `.card`'s own
   `overflow:hidden` (see that rule). Text/deco inside `.scene` measure in
   %/cqw of `.scene`'s OWN box, so they scale WITH it, not independently —
   nothing drifts out of place the way it would under object-fit:cover on
   just the `<img>`. Trade-off, same one the opening stage already accepts:
   on tall/narrow phones the outermost edge of the art (content flush to
   the PSD's own x=0/x=1000 boundary) can crop slightly. Desktop is
   genuinely unchanged — width there was already >66.667vh, so `max()`
   still picks 100% exactly as before. */
.scene{
  position:relative;
  /* width comes from `.card`, its new parent — see CORNER RADIUS below. */
  width:max(100%, 66.667vh);
  left:50%;
  transform:translateX(-50%);
  container-type:inline-size;
  /* A scene IS the PSD's 1000x1500 canvas, so anything outside it is cropped —
     exactly as Photoshop's own composite crops it. Two things rely on this:
     `.deco--corner-l` genuinely starts at x=-1 in the PSD, and a decorative
     sprite sitting flush to the canvas edge extends its *rotated* bounding box
     ~1px past that edge while swaying. Clipping here keeps both faithful and
     makes it structurally impossible for a scene to create page overflow. */
  overflow:hidden;
}
/* `aspect-ratio` is load-bearing, not cosmetic. The scene art is `loading="lazy"`
   from Scene 2 onward, and an <img> with no width/height attributes and no ratio
   has ZERO height until its bytes arrive. Measured on a cold first visit: scenes
   2-9 all collapsed to 0 and the document was 2138px instead of 19238px, so the
   scrollbar claimed a one-screen page and every scene's height appeared only as
   its image happened to load. Reserving the PSD's own ratio fixes the layout
   before the first byte; because the artwork really is 1000x1500, the reserved
   box matches the loaded image exactly and nothing shifts. */
.scene__art{width:100%; height:auto; display:block; aspect-ratio: var(--art-w) / var(--art-h)}

/* Scene3's full-cover door-opening reveal (2026-09-14) — see index.html's
   comment on #s3DoorOverlay for why this exists and why it's the scene's
   LAST child rather than using a z-index. Unlike .scene__art (a normal-flow
   element that SIZES .scene via aspect-ratio) this is position:absolute;
   inset:0, sized off the box .scene__art already established — it must
   never be the element establishing .scene's own height, since a <video>
   with no intrinsic size hint would collapse it to 0 before metadata loads.
   object-fit:cover is technically redundant (the source is already the
   scene's own exact 2:3 ratio, no letterboxing) but cheap insurance if that
   ever stops being true. Fades via opacity, not display/visibility, so the
   700ms transition actually plays; script.js adds `hidden` only once that
   transition has finished, to drop it from paint/hit-testing/decode after.
   2026-09-22: briefly a CSS two-leaf swing (a misread of the request, built
   from what turned out to be a flattened single-frame image) — reverted
   back to this, the original video-based version, once the actual
   animated source came through. */
.scene__doorlay{
  position:absolute; inset:0; width:100%; height:100%;
  object-fit:cover; pointer-events:none;
  opacity:1; transition:opacity 700ms ease;
}
.scene__doorlay.is-open{opacity:0}

/* ==========================================================================
   CORNER RADIUS — shipped 2026-09-08. Prototyped on scene3 alone and
   confirmed before this rule was made to apply to all nine.
   ==========================================================================
   Checked before building anything: every scene's corner carries real
   artwork close to the true pixel edge (measured, scratchpad cornercheck.js
   + a saturation walk from each corner) —
     scene1 top-left    : first real colour  43px in
     scene3 top-left    : first real colour  20px in
     scene5 top-right   : first real colour   4px in
     scene6 bottom-left : first real colour   1px in (a neon-outline flower)
   A radius applied to the artwork itself would clip that content on at least
   scenes 5 and 6 — and the owner's own priority order puts reference
   fidelity above any convenience change, so rounding the art directly was
   off the table.

   Instead: a paper MAT sits between `.slide` and `.scene`. The artwork stays
   completely rectangular (zero content loss, zero clipping, on every scene),
   and the ROUNDED shape the eye reads as "the card" is the mat's own outer
   edge — the same device a physical picture frame uses. `.scene` is 100% of
   the mat's padded interior rather than carrying its own width, so the
   artwork renders a little smaller (making room for the visible mat) but
   every cqw/% measurement inside it stays self-consistent — the whole sizing
   system is relative to `.scene`'s own box, whatever that box is.

   radius <= padding at both breakpoints is deliberate: mobile pad 10px,
   radius 7.5px; desktop pad 18px, radius 14px (clamp caps it there). If the
   curve ever outgrew the straight mat margin, `.scene`'s own square corner
   would show past it — checked, not assumed. */
.card{
  /* Full-bleed, zero border, per owner request 2026-09-12: no whitespace or
     mat around any card, immediate edge-to-edge into the next slide. This
     removes the "paper mat" treatment above (was width:min(92%,66.667vh),
     padding, border-radius, box-shadow — the mat that made the rounded card
     read as a photo/invitation sitting on the fixed paper ground) and the
     side-effect that came with it: capping width at 66.667vh is what made
     one slide equal exactly one screen tall on wide desktop windows (see the
     comment above `.scene`). Full-width removes that cap too — on a very
     wide, short desktop window a slide can again be taller than the
     viewport. That is the direct trade-off of "no border anywhere"; flag it
     if it becomes its own complaint.
     `.ground`'s fixed paper layer is now permanently covered (cards are
     100% width, 0 gap, stacked edge to edge) — left in place, unused, rather
     than removed, since nothing asked for it to go and it costs nothing
     hidden behind the cards.

     2026-09-18: a `min-height:100dvh` fix briefly lived here (mobile scenes
     render shorter than the viewport, so scene2 was visible below scene1
     with zero scroll) — reverted same day, "not at all look good": it
     closed the gap with blank paper instead of more art, which read as a
     broken/empty layout rather than a full screen. Replaced by scaling
     `.scene` itself to cover the viewport (see that rule below) — the fix
     now lives there, not here. overflow:hidden added here to crop the
     small width overflow that approach produces. */
  width:100%;
  overflow:hidden;
  background:var(--paper);
  position:relative;
}

/* THE GROUND — what connects one slide to the next.
   ==========================================================================
   Two earlier attempts got this wrong, both for the same reason: the ground
   changed. First each slide carried its OWN blurred backdrop, so at every
   boundary the card AND the background swapped together and each slide read
   as an island. Then nine blurred layers cross-faded against scroll — better,
   but still a ground in permanent flux, so there was still nothing constant
   to tie the slides to each other.

   The R4 reference's connective device is simply that its ground NEVER
   changes: one paper tile behind all eleven sections, so crossing a boundary
   changes the content and nothing else. That is what this is now — a single
   fixed image, no blur, no cross-fade, no JS. The cards travel over a
   stationary surface, and every slide demonstrably sits on the same one.

   `fixed` so it does not scroll with the cards, which also reads as depth.
   An <img> rather than a CSS background-image: a CSS background resolves to
   the BunnyCDN pull zone on this host (with its documented 502-on-new-asset
   failure) while an <img> resolves to origin, and it keeps the stylesheet
   free of asset paths. */
.ground{
  position:fixed; inset:0;
  z-index:-1;
  overflow:hidden;
  pointer-events:none;
  background:var(--paper);   /* exact colour match beneath the texture */
}
.ground__paper{
  position:absolute; inset:0;
  width:100%; height:100%;
  object-fit:cover;
}

.slide{position:relative}
/* `.card` (not `.scene`) is now the direct child of `.slide` — see CORNER
   RADIUS. `.card` already declares its own `position:relative`, which is
   enough to paint above `.ground`'s explicit z-index:-1 fixed layer (checked
   on the scene3 prototype: stacked correctly with no extra z-index needed),
   so this rule has nothing left to do. `.scene` keeps its own
   `position:relative` independently, for its absolutely-positioned deco/text
   children. */

/* Some PSD layers sit ABOVE the animated sprites — a countdown plate, a light
   wash, a vessel. They ship as a separate transparent plane so the sprites stay
   in their true z-order instead of being lifted above everything. Without it,
   Scene 5's recomposition differed from the PSD by max 69 even when rendered
   losslessly; with it, every scene is at or below its own WebP noise floor. */
.scene__over{position:absolute; top:0; left:0; width:100%; height:auto; pointer-events:none;
  aspect-ratio: var(--art-w) / var(--art-h)}

/* ==========================================================================
   SEAM — the slide-to-slide transition
   ==========================================================================
   History: nine opaque full-bleed paintings butted at a zero gap meant every
   boundary was a razor cut between two unrelated colour fields. The first fix
   was to feather each painting's top/bottom edge and pull consecutive slides
   together with a negative margin, so they cross-dissolved through the body's
   paper colour at the join — a real fix, but only necessary because at that
   point nothing else was providing continuity.

   THE GROUND now does that job properly (see the GROUND block): one fixed
   paper surface behind every card, visible in the margin on every side, at
   every scroll position. With a real continuous surface underneath, the
   feather/overlap technique is no longer solving a real problem — it exists
   now only to avoid showing what IS the connective device. So it comes off,
   and a genuine gap takes its place: each card sits on the paper as a
   distinct, clean-edged panel, exactly the way a photograph or an invitation
   card would sit on a table, rather than nine paintings dissolving into each
   other.

   --slide-gap uses clamp() rather than a fixed vh so it holds proportionally
   at the extremes: never so tight it disappears on a short phone viewport,
   never so wide it reads as a second background on an ultra-tall window. */
.invite .slide + .slide{margin-top:var(--slide-gap)}

/* A scene may need sprites on BOTH sides of the overlay when the PSD
   interleaves decorative and static layers. Page 9 is the first:
   fire < thalis < lamps < frames < floral corners. Same plane geometry,
   just emitted after `.scene__over` so it lands above it. */
.scene__deco--front{position:absolute; inset:0; pointer-events:none}

/* Text plane sits exactly over the art. */
.scene__text{position:absolute; inset:0}

/* ==========================================================================
   SCENE 1 typography — every value measured from the PSD layer bboxes.
   left/top/width are % of the 1000x1500 canvas; font-size is cqw.
   ==========================================================================
   ⚠️ FONT SUBSTITUTION IN EFFECT — NOT FINAL, NOT SILENT.
   The PSD uses Afterglow-Regular, Tempting and AuthenticScriptRough-Regular.
   None is licensed for web embedding yet (BLUEPRINT §5 / typography report),
   so the stacks below are TEMPORARY stand-ins purely so layout can be
   verified. Letterforms WILL differ from the PSD until the real files or
   licences are supplied. Do not treat current typography as approved.       */
/* Candlescript Pro's @font-face is NOT here (owner-supplied 2026-09-15,
   "use this font for bride and groom names") — it was here first, and
   broke in production: CSS `url()` inside an external stylesheet resolves
   relative to THAT STYLESHEET's own location, not the page's. Locally
   styles.css sits flat next to assets/, so `assets/fonts/...` resolved
   correctly there — but the deployed copy lives one level deeper, inside
   its own css/ folder (rwp-vNN.css), so the SAME relative path silently
   pointed at a path that doesn't exist. Confirmed the hard way: the font
   FILE was fine (byte-identical on CDN, and a manual `new FontFace(...)
   .load()` on those exact fetched bytes succeeded) — it was specifically
   the @font-face rule's relative URL that failed, browser-reported as
   `document.fonts` status "error". This is exactly the "CSS/JS carry ZERO
   asset references" rule the very first comment in this file's $rwp
   section states, for precisely this reason — see index.html's own
   @font-face (local-preview path) and gen_template.py's matching one
   ($rwp-prefixed) for where it actually lives now, one per environment,
   same pattern already used there for the opening-sprite preloads. */

:root{
  /* Cormorant Garamond (SIL OFL) replaced the Georgia stand-in on 2026-09-08.
     Georgia is a screen serif with a large x-height and sturdy, utilitarian
     letterforms; Cormorant is a display garamond drawn for exactly this kind
     of invitation setting. It is still a SUBSTITUTE for Afterglow, not a
     match — but it is a deliberate, licence-clean one rather than a default. */
  --f-body:   'Cormorant Garamond', Georgia, serif;  /* stands in for Afterglow  */
  /* Candlescript Pro superseded Aladin/"Tempting" 2026-09-15 as every scene
     heading's face ("use this font for all headings in the all slides") —
     .s3-title through .s9-title all resolve through this one variable, so
     the single change here covers every scene without touching each rule.
     Aladin stays as the fallback (still genuinely loaded — see index.html's
     Google Fonts <link> comment — and still used directly, not through this
     variable, by every scene's SUBTITLE line and by .s1-weds, neither of
     which is a "heading"). */
  --f-script: 'Candlescript Pro', 'Aladin', cursive;
  --f-weds:   'Aladin', cursive;                     /* stands in for AuthScript */
  /* Candlescript Pro superseded Pinyon Script 2026-09-15 as the couple's
     names' primary face — Pinyon Script stays as the fallback (not removed:
     see index.html's own Google Fonts <link> comment for why it's still
     genuinely loaded, not orphaned). */
  --f-names:  'Candlescript Pro', 'Pinyon Script', 'Aladin', cursive;

  /* Label tracking. The R4 reference sets its small labels at 0.15em-0.30em,
     overwhelmingly 0.20em. Ours stay mixed-case (see the label tier below for
     why), and mixed-case lowercase needs materially less than uppercase does,
     so this is deliberately lighter than the reference's own figure. */
  --track-label: .08em;   /* mixed-case lines that are not part of the caps tier */
  --track-caps:  .20em;   /* the reference's own figure, for UPPERCASE labels  */
}

/* :where() — same fix as the per-scene `:where(#sceneN .scene__text > p)`
   rules already use, applied to the one place it was missed. A plain
   `.scene__text > p` selector is specificity (0,1,1) — ONE class PLUS the
   `p` type — which beats every single-class override in the file: every
   `:where(#sceneN...){line-height:1.47}` shared rule (0,1,1 vs (0,1,0)? no —
   :where() is explicitly (0,0,0), so it never had a chance), AND explicit
   per-element overrides like `.s2-gparents{line-height:1.40}` and
   `.s3-venue{line-height:1.42}` (both (0,1,0)). Confirmed live on
   pikaaso.com, not assumed: computed line-height on l3Venue measured
   12.667px — that's 1.18x its 10.7px font, not the 1.42 the rule states.
   Every scene's running-prose line-height (the :where 1.47 rules) and every
   explicit venue/parentage override (1.40-1.42) has been silently rendering
   at 1.18 site-wide since those rules were written — this is the fix for
   BOTH slide2's cramped body text AND slide3's overlapping venue lines, not
   two separate bugs. */
:where(.scene__text > p){margin:0; position:absolute; text-align:center; line-height:1.18}

/* Enlarged 2026-09-09, same pass as scene3: measured content bottom was
   55.2% with 2.4-5.6% gaps between every line (scratchpad
   measure_whitespace.js) — real slack, not assumed. Names get the same
   permanent soft-glow highlight as scene3's title (their own accent colour,
   low-opacity bloom); "Are getting married" moves to Cormorant Garamond
   ITALIC, matching the italic treatment on scene3's subtitle rather than a
   one-off. Countdown numerals/labels are UNCHANGED — they sit on the dark
   plates baked into the flat artwork (see the countdown comment below);
   growing them risks spilling off art that can't grow with them. */

/* “Riddhi” / “Piyush” — Pinyon Script, a formal copperplate calligraphy
   face. Its x-height is tiny and its hairlines are fine, so it needs to run
   MUCH larger than a normal display font to read as the hero line
   ("still too small" — 2026-09-10). No letter-spacing (it would snap the
   joined strokes) and no weight (single-weight face). The text-shadow does
   double duty: the tight 1px same-colour pass thickens the hairlines so
   they don't disappear, the wide soft pass is the warm glow ("increase
   opacity"). */
.s1-bride{
  left:0; right:0; top:11.4%;
  font-family:var(--f-names); font-size:13.0cqw; color:#c93a2a;
  text-shadow:0 0 1px rgba(201,58,42,.6), 0 0 24px rgba(201,58,42,.44);
}
/* “weds” — 458,357 → 546,405 */
.s1-weds{
  left:0; right:0; top:21.8%;
  font-family:var(--f-weds); font-size:4.10cqw; color:#1c421b;
}
/* “Piyush” — matches .s1-bride */
.s1-groom{
  left:0; right:0; top:26.0%;
  font-family:var(--f-names); font-size:13.0cqw; color:#c93a2a;
  text-shadow:0 0 1px rgba(201,58,42,.6), 0 0 24px rgba(201,58,42,.44);
}
/* “Are getting married” — 323,588 → 684,630 */
.s1-sub{
  left:0; right:0; top:39.4%;
  font-family:var(--f-body); font-size:3.40cqw; color:#1c421b;
  font-style:italic; font-weight:500; letter-spacing:.02em;
}
/* "10th December, 2026" — 291,659 → 712,700. Changed 2026-09-15 ("change
   the date font and make it prominent from slide 1") from the body serif to
   Candlescript Pro (the same face this session just made every scene
   heading's font — see --f-script) and grown 3.75cqw -> 5.5cqw, in the
   couple's own crimson (#c93a2a, matching .s1-bride/.s1-groom) with a
   matching soft glow, lighter than theirs since the date is smaller. 5.5cqw
   is the largest that still clears .s1-tprompt below it with a real margin
   (top: kept at 44.3%, unchanged) — probed directly: 6.0cqw left only
   0.54% before the two collided, 5.5cqw leaves 0.89%. font-weight dropped
   (Candlescript Pro is a single-weight script face, like Pinyon Script —
   600 does nothing real, just a synthetic-bold risk in browsers that fake
   missing weights). */
.s1-date{
  left:0; right:0; top:44.3%;
  font-family:var(--f-script); font-size:5.5cqw; color:#c93a2a;
  text-shadow:0 0 1px rgba(201,58,42,.55), 0 0 14px rgba(201,58,42,.35);
}
/* “Scratch to reveal timer” — 331,744 → 672,770 */
.s1-tprompt{
  left:0; right:0; top:50.4%;
  font-family:var(--f-body); font-size:2.65cqw; color:#1c421b;
}

/* Countdown. The four dark plates are part of the artwork — measured from
   scene-01.webp itself, they span y 818-902 and x 232-336 / 376-482 /
   520-626 / 666-770, i.e. centres 284, 429, 573, 718 (pitch 144.67).
   With four equal flex columns the centres fall at L+W/8 .. L+7W/8, so
   L=211.7 and W=578.7 puts each numeral exactly on its own plate.
   Numerals sit at PSD y 832 (white, on the plate); labels at y 916, which
   is BELOW the plate on flat light ground — hence the dark ink. Both are
   absolute so neither can drift into the plate edge. */
.s1-timer{
  position:absolute; left:21.17%; right:20.96%; top:55.5%;
  display:flex;
}
.cd-unit{position:relative; flex:1}
.cd-num{
  display:block; text-align:center;
  font-family:var(--f-body); font-size:5.21cqw; line-height:1;
  color:#ffffff; font-variant-numeric:tabular-nums;
}
.cd-lab{
  position:absolute; left:0; right:0; top:8.4cqw;   /* PSD y 916 - 832 */
  text-align:center;
  font-family:var(--f-body); font-size:2.08cqw; color:#2b402f;
}

/* Scratch cover sits over the whole timer block (numbers + labels).
   Nudged down + made taller 2026-09-10 — reported the countdown showing
   through above the cover ("needs to be little lower, its not visible"):
   the numerals render at ~55.5% and the labels reach ~63%, so the cover now
   starts a touch below the numerals' top and extends well past the labels,
   with enough margin to stay aligned across device widths.

   Sizing (left/right/top/height here are only the pre-JS fallback — the
   real box comes from script.js's positionOverCountdown(), tightened
   2026-09-12) plus a gold border+glow so a now-smaller card still reads as
   an obviously interactive scratch card rather than a plain cream box. Gold
   is the site's own --gold, already sampled from the opening artwork. */
.s1-scratch{
  position:absolute; left:18%; right:18%; top:55.2%; height:11.5%;
  width:64%; cursor:grab; touch-action:none;
  border:1.5px solid var(--gold); border-radius:6px; overflow:hidden;
  box-shadow:0 0 0 1px rgba(185,143,87,.25), 0 0 10px rgba(185,143,87,.35);
  transition:opacity .45s ease-out;
}
.s1-scratch.is-revealed{opacity:0; pointer-events:none}

/* .scene2__spacer existed to buy extra height for the PSD's 15-block dense
   letter. 2026-09-10: the letter is now the real couple's 9 short blocks and
   measures to ~80% of the art's own 2:3 height (scratchpad scene2_retall.js)
   — no extra room needed, so the spacer is back to zero and the scene is a
   normal 2:3 panel again like scenes 1 and 3. The element stays in the
   markup (harmless at height:0) rather than churn the template. */
.scene2__spacer{display:block; height:0}

/* Text veil — see the HTML comment at .scene2__veil for why this exists.
   Vertical band matching the text column's own envelope over the ART portion
   ONLY — the floral corners and hummingbirds live outside this band and must
   stay unveiled. Paper tone reuses the site's own --paper token rather than
   inventing a new colour. Feathered via a mask gradient on all four edges so
   it reads as a soft glow, not a hard card.

   Bottom bound updated for .scene2__spacer (2026-09-09 readability pass):
   the mandala this veil exists to soften is baked into the fixed-ratio ART
   ONLY, which is now just ~76% of the scene's new (taller) total height —
   the spacer below it is already flat --paper with no pattern to hide, so
   the veil doesn't need to reach it. Top/bottom are % of the WHOLE scene
   (art + spacer), same as every top:% in this file. */
/* Strengthened 2026-09-12 ("We cordially is not at all readable... decrease
   the background image top opacity") — the salutation sits at top:9% of the
   scene, only ~5.5% into this veil's own box (top:4% to bottom:6%). At the
   OLD stops (#000 60%, transparent 100%) that position fell deep in the
   radial mask's fade-to-transparent zone — around half-strength at best —
   so the mandala behind "We cordially..." stayed nearly full-strength while
   the veil did its job everywhere nearer the centre. Tightening the solid
   stop to 88% shrinks the fade to just the outer edge, so the veil now
   applies at near-full opacity almost everywhere inside its box, top and
   bottom included, not just the middle. Opacity raised too, for a visibly
   stronger dimming rather than a marginal one. */
.scene2__veil{
  position:absolute; left:4%; right:4%; top:4%; bottom:6%;
  background:var(--paper);
  opacity:.85;
  -webkit-mask-image: radial-gradient(ellipse 62% 54% at 50% 50%, #000 88%, transparent 100%);
          mask-image: radial-gradient(ellipse 62% 54% at 50% 50%, #000 88%, transparent 100%);
  pointer-events:none;
}

/* ==========================================================================
   SCENE 2 typography — REBUILT 2026-09-10 for the real couple's invitation.
   The PSD's 15-block formal letter is gone; this is 9 blocks and much less
   text (see config.js / index.html). The names use --f-names (Playfair
   Display, the refined-serif direction chosen for slide 1). Positions are
   cascaded from MEASURED rendered heights (scratchpad scene2_retall.js),
   not hand-computed. .scene2__spacer shrank right back down with the lighter
   content. The old per-block PSD-bbox measurements and the two-tier
   mobile-fix history are retired with the content that needed them.
   ========================================================================== */
/* :where() — zero specificity, so per-element rules below always win. */
:where(#scene2 .scene__text > p){line-height:1.47; color:#1c421b; font-family:var(--f-body)}

/* Re-cascaded 2026-09-12 in three passes, each correcting the last against
   direct feedback:
     1. "align text slide 2" — after the Event & Schedule block was removed,
        stretched the gaps between the remaining six blocks to ~6.4% each to
        fill the space it left. Read as awkward empty mandala between
        paragraphs, not a page put to good use.
     2. "still very small... lot of unnecessary spaces" — salutation font
        raised a little (12.5px floor to 16px) and every gap tightened to a
        flat 2.5%. Still too small: the 16px floor never actually got
        overridden by the cqw term at any real phone width, so it read as
        barely bigger than before.
     3. "why 2 lines, make it 3 lines everywhere... readable on mobile" —
        floors raised again and probed directly rather than guessed
        (scratchpad scene2_font_probe.js: 18px is where the salutation
        genuinely breaks to 3 lines at 375px; set to 19px for margin). The
        two parentage blocks and "with" raised to match, since this was
        asked for "everywhere". Every top:% below is recascaded from the
        ACTUAL rendered heights at these new sizes (scene2_realign.js), a
        flat 3.0% gap (bumped from 2.5% after a real overlap turned up at
        320px — scene height scales down with viewport width, but the font
        floors are fixed px, so text claims a slightly bigger share of a
        narrower scene; the extra 0.5% gap covers that margin), content now
        ending around 80%.
     4. "little decrease for cordially... 3 lines [with a clean break]...
        increase font for the paragraph text below both names" — salutation
        eased back down slightly (19px to 17px). The groom's parentage
        sentence now breaks at explicit phrase boundaries in config.js
        instead of wherever it happened to wrap (was landing mid-surname,
        "Agarwal-" / "Saraf") — 3 controlled lines instead of an
        uncontrolled wrap that happened to also produce 3. First attempt
        also raised both parentage floors from 14px to 16px, which
        overshot: the groom's third line wrapped again, AND it made
        bride's — untouched by config, still just 2 array lines — start
        wrapping too, orphaning "Dutharia" alone on its own line. Settled
        on 14px (back where it started) plus explicit breaks on BOTH
        parentage blocks now, not just groom's, so neither depends on
        wrapping behaving itself at whatever width it renders. Content
        ends around 82%, not 80% — bride's parentage gained a 3rd line.
     5. "decrease cordially font... grandson of in one line, remaining in
        2 lines... text going onto the flowers/leaves" — salutation eased
        down again (17px to 14px) AND given real side clearance (5% inset
        to 8%) from the top-corner floral sprites (.deco--s2-floral-tl/tr),
        which extend down from the very top of the scene into roughly the
        same band the salutation occupies. Groom's parentage restructured
        AGAIN: the whole first sentence is now one explicit config line
        (was split at "Geetadevi"), with the second sentence split before
        the surname instead. Fitting a 62-character sentence on one line at
        real mobile widths is genuinely tight — probed directly rather than
        guessed (scratchpad probe_onliner2.js): even at near-full-bleed 2%
        insets it needs an 11px floor, so both parentage blocks moved to
        that size and those insets. Bride's already matched this shape (her
        first sentence was always shorter), just resized to match. */
/* 1 — the invitation sentence (reused .s2-salutation slot). Superseded
   2026-09-15 ("make the text small and center align not on the flower or
   leafes designs") — the 2026-09-13 halo above (removed) papered over the
   overlap instead of clearing it, which the owner explicitly rejected on
   reappearance. Re-measured .deco--s2-floral-tl/tr per ACTUAL alpha pixels
   (not the bounding box the halo comment used) with a row-by-row profile,
   not just a single worst-case rectangle: the corner sprites are narrow
   near the very top of the scene and taper away fast — the box only has to
   clear roughly x=27%/73% right where line 1 sits (y~10-14%), not the
   26-40% band the full bounding box would suggest. A 22%/22% inset (44%-
   wide box) clears every wrapped line with a 2-4% margin, confirmed at
   320/375/390/430/700/800/1200px.
   font-size switched from a px-floored max() to a pure cqw value
   (max(11px, 4cqw), floor inert above ~275px) so the box-fill ratio — and
   therefore the line count and the safety margin — stays IDENTICAL at
   every viewport width instead of drifting (a flat px size wraps to fewer,
   wider-relative lines as the box gets more physical pixels to work with,
   which silently ate the margin back up at ~700px during testing). This is
   the same resolution-independence .s2-groom/.s2-bride already had from
   their own cqw sizing — confirmed live that neither of THEM ever actually
   overlapped the corner florals; only this line's old flat 16px did. Also
   makes the text visibly smaller, which was the other half of the request.
   One rule now covers every width — see the removed <=360px and >=769px
   overrides below, both no longer needed. */
.s2-salutation {left:22%; right:22%; top:9.00%; font-size:max(11px, 4cqw); font-weight:500}
/* 2 — groom's name — Pinyon Script, large; crimson + hairline-thicken +
   glow (see .s1-bride). Wide box because the script's capital swashes on
   "Piyush" / "Agarwal" reach well past the glyph body. */
.s2-groom      {left:3%; right:3%; top:25.06%; font-size:9.4cqw;
                font-family:var(--f-names); color:#c93a2a;
                text-shadow:0 0 1px rgba(201,58,42,.55), 0 0 20px rgba(201,58,42,.40)}
/* 3 — groom's parentage, 3 explicit lines (see config.js) — italic.
   Inset widened 2% -> 10% on 2026-09-15 (see .s2-salutation above): the
   long first sentence's own row-precise alpha profile against
   .deco--s2-floral-ml/mr showed a genuine, if narrow, overlap at the very
   bottom edge of line 1 (only ~0.6% of its height dips into where the mid
   florals first become visible, around y=42-43%). 10% clears that with a
   comfortable 7%+ margin at every width tested; font-size is untouched —
   it was never the problem, only the box width was. This does push the
   first sentence to wrap onto a second sub-line at some widths (verified
   harmless: still finishes well above "with" at top:49.50%).

   Original near-full-bleed reasoning kept for context: fitting the whole
   first sentence on one line needs every bit of available width at mobile
   sizes (probed directly, scratchpad probe_onliner2.js — even at 1% insets
   it needs ~11-11.5px, a real floor, not a stylistic choice). Raised again
   2026-09-13 ("increase the font size of parent and grandparents names")
   to 14px. `top:` for every block after this one is cascaded against this
   block's worst-case (most-wrapped) height, not its typical height — costs
   a bit of extra visual gap at widths where it wraps less; that's cheaper
   than an overlap with "with" at the narrowest tested width. */
.s2-gparents   {left:10%; right:10%; top:37.27%; font-size:max(14px, 2.5cqw);
                line-height:1.42; font-style:italic}
/* 4 — the connector word "with" (reused .s2-amp slot) — small, italic */
.s2-amp        {left:0; right:0; top:49.50%; font-size:max(15px, 2.9cqw);
                font-family:var(--f-body); font-style:italic; color:#1c421b}
/* 5 — bride's name — matches .s2-groom */
.s2-bride      {left:3%; right:3%; top:56.60%; font-size:9.4cqw;
                font-family:var(--f-names); color:#c93a2a;
                text-shadow:0 0 1px rgba(201,58,42,.55), 0 0 20px rgba(201,58,42,.40)}
/* 6 — bride's parentage, 2 lines — italic. Scene 2 now ends here — the
   Event & Schedule heading + date/venue row that followed was removed
   2026-09-12 (redundant with each event's own scene). */
.s2-bparents   {left:2%; right:2%; top:68.80%; font-size:max(14px, 2.5cqw);
                line-height:1.42; font-style:italic}

/* <=360px override removed 2026-09-15: .s2-salutation's cqw-based font-size
   (see above) makes its box-fill ratio resolution-independent, so the same
   22%/22% inset already holds a clean 3 lines at 320px — probed directly —
   with no narrow-phone exception needed. gparents/bparents never needed one
   (same 2%/10% inset as the base rule above). */

/* >=769px — desktop has no spacer, so the scene is its own 2:3 art height.
   The lighter content fits that comfortably; only the box insets tighten
   back toward the centred look a wide canvas wants. .s2-salutation and
   .s2-gparents dropped out of this block 2026-09-15 — both are now
   resolution-independent (cqw-scaled font / proportional inset) and were
   probed directly at 800px and 1200px with no override, so the single base
   rule already covers desktop too. Groom/bride/bparents positions are left
   as the mobile cascade — verified they still clear at desktop width. */
@media (min-width:769px){
  .s2-groom      {left:6%; right:6%}
  .s2-bride      {left:6%; right:6%}
  .s2-bparents   {left:12%; right:12%}
  .scene2__veil{top:6%; bottom:6%}
}

/* ==========================================================================
   SCENE 3 typography — PSD Page 3, 5 type layers.
   Accent is #ac034d here, not Scene 1–2's #c93a2a — the PSD's own choice.

   Enlarged 2026-09-09: measured content bottom was 37.95% of the scene —
   the 5 text blocks used barely a third of the canvas, with the peacocks and
   corner sprays not starting until ~72% (scratchpad measure_whitespace.js).
   Reported: "the 3rd slide has space, increase the font size" — confirmed,
   not assumed, before growing anything. Positions re-cascaded to keep the
   same generous rhythm at the larger sizes, still landing with ~25% of clear
   canvas above the peacocks — verified after the fact, not just before.

   "Highlight" treatment: title and date get a soft static glow in the
   scene's own accent colour (not the animated reveal-glow — a permanent,
   subtle bloom, same idea, always-on) so the two pieces of information a
   guest actually needs (what this event is, when) read as emphasized without
   shouting. Subtitle moved from full-phrase Aladin script (elegant but hard
   to read at a glance) to Cormorant Garamond ITALIC — the font this session
   already loads with a real italic face — larger and clearer while staying
   ornamental via the slant, not the letterforms. */
:where(#scene3 .scene__text > p){line-height:1.47; color:#1c421b; font-family:var(--f-body)}

/* Repositioned 2026-09-09 — reported venue text sitting on top of the palace
   artwork below it. Confirmed by sampling the actual pixels of scene-03.webp
   (scratchpad, PIL): the palace's topmost point (a side dome) starts at
   37.6% down the canvas, but venue's old top:38% + its own 3-line height
   put its BOTTOM edge at ~50.7% — a ~12% overlap into the roofline, not
   assumed, measured. Every top below is re-cascaded from MEASURED rendered
   heights at the current (enlarged) font sizes, tightened just enough that
   the whole block — title through venue — clears 37.6% with a real margin
   (scratchpad scene3_recascade.js: ends at 35.89%, 1.7% of clearance). Sizes
   are unchanged from the earlier enlarge pass; only vertical rhythm and
   the starting offset moved. */
/* Whole block shifted down 2.667% (owner correction 2026-09-14: "text in
   slide 3 is up make it 15px down" — 15px at this project's usual 375px
   test width / 562.5px scene height = 15/562.5 = 2.667% of scene height;
   every top: below carries that same +2.667% added, spacing between lines
   left exactly as it was, only the block's start moved). */
/* 1 — "Rajsi Aagman" */
.s3-title    {left:14%; right:14%; top:5.167%;  font-size:6.60cqw;
              font-family:var(--f-script); color:#ac034d;
              text-shadow:0 0 18px rgba(172,3,77,.30)}
/* 2 — subtitle, now one line ("A Royal Welcome" was the PSD original;
   2026-09-28 lengthened it to a wrapped 2-line description; 2026-09-30
   shortened it back to one line — see config.js's welcome.subtitle
   comment). */
.s3-subtitle {left:18%; right:18%; top:11.927%; font-size:3.30cqw; line-height:1.32;
              font-family:var(--f-body); font-style:italic; font-weight:500;
              letter-spacing:.03em}
/* 3 — date. 4 — time. 5 — venue.
   Repositioned 2026-09-30 (owner, screenshot with "KHANDALA" circled:
   "Overlapping with background element") — confirmed by sampling the
   artwork's own pixels (scene-03-bg-v4.webp), not by eye: the archway
   silhouette starts at native y=570 of 1500 = 38.0% down the scene, a
   fixed fact independent of viewport size since top:% here already tracks
   1:1 with the art's own fraction (verified: this scene's rendered %
   matched its CSS top: value exactly once the .reveal transition settles).
   The venue block's bottom edge at the OLD top:26.797% landed at 39.29% —
   past the archway start, a real overlap, not a mistaken report. That
   value predated the subtitle going from one line ("A Royal Welcome") to
   a wrapped two-line description (2026-09-28) without date/time/venue's
   fixed top:% ever being re-checked against the two-line subtitle's extra
   height — this is that missed check, plus the subtitle's own return to
   one line freeing further room. Recomputed date/time/venue from the new
   one-line subtitle's actual measured bottom (14.83%), keeping this
   scene's own tiny ~0.29% inter-line gap (the same spacing already used
   between every other line here) rather than inventing new spacing.
   Result: venue bottom 35.44% — a 2.56% (~23px) clear margin above the
   archway, verified with a live DOM measurement and a screenshot before
   shipping, not assumed. */
.s3-date     {left:12%; right:12%; top:15.12%; font-size:4.10cqw; color:#ac034d;
              font-weight:600; text-shadow:0 0 14px rgba(172,3,77,.22)}
.s3-time     {left:22%; right:22%; top:19.43%; font-size:3.30cqw}
.s3-venue    {left:16%; right:16%; top:22.95%; font-size:3.30cqw; line-height:1.42}

/* ==========================================================================
   SCENE 4 typography — PSD Page 4, 5 type layers.
   Accent shifts again: #ee8116 title, #de6e01 date — Holi warmth, per the PSD.
   ========================================================================== */
:where(#scene4 .scene__text > p){line-height:1.47; color:#1c421b; font-family:var(--f-body)}

/* Sizes corrected 2026-09-15 ("correct the text sizes in slide 4 based on
   slide 3") — the pixel-anchored sizes/insets in the comments below (e.g.
   "240,49 → 760,131") were measured against the OLD psd-tools background,
   which had its own baked-in type layers at those exact coordinates. That
   background was replaced 2026-09-15 with a real designer export that has
   no text of its own, so those anchors no longer correspond to anything —
   the old, much smaller sizes were an artifact of that stale measurement,
   not a deliberate design choice. Now sized and inset to match .s3-* (same
   font-size, same left/right) since scene3 is this site's own reference for
   "correctly sized" event-scene typography. Verified directly, not assumed:
   scene4's own `top` values already leave enough room for scene3's larger
   sizes with zero wrapping/collision changes versus before — confirmed by
   measuring every line's rendered box against its neighbours. (.s4-time/
   .s4-venue's font-size now comes from the shared rule near the end of this
   file, not a per-scene override — see that rule's own comment for why it
   no longer needs one.) Scenes 5-9 got the identical correction the same
   day — see their own typography blocks below. */
.s4-title    {left:14%;  right:14%;  top:3.27%;  font-size:6.60cqw;
              font-family:var(--f-script); color:#ee8116}
.s4-subtitle {left:18%;  right:18%;  top:10.60%; font-size:3.30cqw; line-height:1.32;
              font-family:'Aladin', cursive}
.s4-date     {left:12%;  right:12%;  top:17.630%; font-size:4.10cqw; color:#de6e01}
.s4-time     {left:22%;  right:22%;  top:21.570%} /* font-size: shared rule below */
.s4-venue    {left:16%;  right:16%;  top:25.370%; line-height:1.40} /* font-size: shared rule below */

/* Scene 4 — falling rose petals/flowers reveal, 2026-09-15 ("add rose
   pettles and flowers falling reveal to slide 4"). "Phoolon ki Holi" is
   literally a flower shower, so a fall of petals as the scene reveals is
   the scene's own theme, not a generic decoration borrowed from elsewhere.
   Base shapes and fall mechanics are adapted from the opening's
   `.opening__petal` (same teardrop trick, same transform-only fall) — see
   that rule's own comment for why transform-only matters (MOTION.md:
   structurally incapable of layout shift). Two differences from the
   opening version: these are triggered by the shared scene-reveal
   IntersectionObserver (grouped with `.firework.reveal` in script.js, not
   fired from the tear clock — there is no tear clock here), and the fall
   distance is in `cqw` rather than `vh`, because `.scene` is a
   container-query context and the opening's stage is not (see MOTION.md /
   this file's own established `vw`-vs-`cqw` split). A "flower" is a plain
   two-tone radial-gradient dot standing in for a marigold head — small
   enough at this size that a literal petalled shape wouldn't read any
   clearer, and it reuses the scene's own #ee8116/#de6e01 marigold oranges
   already established by .s4-title/.s4-date, not a colour invented here.

   Changed 2026-09-16 ("use the rose pettles falling continuesly") from a
   one-shot burst to a continuous loop: `animation-iteration-count:infinite`
   added, `animation-fill-mode` kept at `both` (not dropped) because it
   still does real work with an infinite count — `backwards` still holds
   each piece invisible at its own 0% keyframe during its own individual
   `animation-delay` before its first fall, which is what makes the initial
   entrance staggered rather than all 24 pieces starting at once; `forwards`
   is simply inert now since an infinite animation has no "after the last
   iteration" to hold. The loop restart is visually seamless with no extra
   gap needed: both the 100% and 0% keyframes are opacity:0, so one piece
   finishing and immediately restarting has no visible discontinuity to
   paper over. Each piece keeps its own distinct duration (2.3-3.4s, see
   the .s4-fall--N rules below), so even though every loop replays the
   identical per-piece path, the 24 pieces drift out of phase with each
   other for a very long time before any two would visibly resynchronise —
   no per-frame JS or randomisation needed for that. */
.falling-petal, .falling-flower{
  position:absolute; top:-5%;
  opacity:0; pointer-events:none;
}
.falling-petal.is-in, .falling-flower.is-in{
  animation-name:scene-petal-fall;
  animation-timing-function:ease-in;
  animation-fill-mode:both;
  animation-iteration-count:infinite;
}
@keyframes scene-petal-fall{
  0%   {opacity:0;  transform:translate(0,0)        rotate(0deg)}
  10%  {opacity:.9}
  45%  {transform:translate(4cqw, 70cqw)  rotate(130deg)}
  75%  {transform:translate(-3cqw, 125cqw) rotate(235deg)}
  100% {opacity:0;  transform:translate(3cqw, 168cqw) rotate(320deg)}
}
.falling-petal{
  width:1.1cqw; height:1.1cqw; min-width:8px; min-height:8px;
  background:#d9536a;
  border-radius:0 100% 0 100%;
  box-shadow:0 0 3px rgba(150,50,70,.35);
}
.falling-flower{
  width:1.3cqw; height:1.3cqw; min-width:9px; min-height:9px;
  border-radius:50%;
  background:radial-gradient(circle at 50% 50%, #ffb347 0%, #ffb347 40%, #de6e01 58%, #de6e01 100%);
  box-shadow:0 0 3px rgba(180,100,10,.35);
}
/* Densified 2026-09-16 ("more flowers and rose petals falling") — 11 -> 24
   pieces. Left positions are two interleaved passes across the width (16
   fairly even + 8 filling the gaps) rather than one even grid, so density
   varies slightly and reads as organic, not a ruled-off row. Durations and
   delays are assigned with no correlation to position (no left-to-right
   sweep pattern); delays now span 0-900ms (was 0-420ms) so the extra
   pieces stretch the shower into a longer, denser flurry instead of just
   thickening one quick burst. */
.s4-fall--1{left: 3%;  animation-duration:2.6s; animation-delay:0ms}
.s4-fall--2{left: 9%;  animation-duration:2.9s; animation-delay:420ms}
.s4-fall--3{left:15%;  animation-duration:2.4s; animation-delay:140ms}
.s4-fall--4{left:21%;  animation-duration:3.1s; animation-delay:680ms}
.s4-fall--5{left:28%;  animation-duration:2.7s; animation-delay:60ms}
.s4-fall--6{left:34%;  animation-duration:2.5s; animation-delay:540ms}
.s4-fall--7{left:40%;  animation-duration:3.0s; animation-delay:260ms}
.s4-fall--8{left:47%;  animation-duration:2.6s; animation-delay:800ms}
.s4-fall--9{left:53%;  animation-duration:2.8s; animation-delay:100ms}
.s4-fall--10{left:59%; animation-duration:3.2s; animation-delay:600ms}
.s4-fall--11{left:65%; animation-duration:2.3s; animation-delay:320ms}
.s4-fall--12{left:71%; animation-duration:3.3s; animation-delay:900ms}
.s4-fall--13{left:77%; animation-duration:2.7s; animation-delay:180ms}
.s4-fall--14{left:83%; animation-duration:2.9s; animation-delay:460ms}
.s4-fall--15{left:89%; animation-duration:2.4s; animation-delay:40ms}
.s4-fall--16{left:95%; animation-duration:3.4s; animation-delay:740ms}
.s4-fall--17{left:12%; animation-duration:2.8s; animation-delay:240ms}
.s4-fall--18{left:25%; animation-duration:2.5s; animation-delay:580ms}
.s4-fall--19{left:38%; animation-duration:3.1s; animation-delay:380ms}
.s4-fall--20{left:50%; animation-duration:2.6s; animation-delay:860ms}
.s4-fall--21{left:62%; animation-duration:2.9s; animation-delay:120ms}
.s4-fall--22{left:75%; animation-duration:2.3s; animation-delay:500ms}
.s4-fall--23{left:88%; animation-duration:3.0s; animation-delay:300ms}
.s4-fall--24{left:18%; animation-duration:2.7s; animation-delay:660ms}
/* Densified again 2026-09-16 ("more flowers should fall") — 24 -> 36. */
.s4-fall--25{left: 6%; animation-duration:2.5s; animation-delay:520ms}
.s4-fall--26{left:22%; animation-duration:2.9s; animation-delay:80ms}
.s4-fall--27{left:33%; animation-duration:2.4s; animation-delay:640ms}
.s4-fall--28{left:44%; animation-duration:3.2s; animation-delay:200ms}
.s4-fall--29{left:56%; animation-duration:2.7s; animation-delay:760ms}
.s4-fall--30{left:68%; animation-duration:2.6s; animation-delay:340ms}
.s4-fall--31{left:80%; animation-duration:3.0s; animation-delay:880ms}
.s4-fall--32{left:92%; animation-duration:2.3s; animation-delay:160ms}
.s4-fall--33{left:14%; animation-duration:2.8s; animation-delay:700ms}
.s4-fall--34{left:45%; animation-duration:3.3s; animation-delay:440ms}
.s4-fall--35{left:58%; animation-duration:2.5s; animation-delay:860ms}
.s4-fall--36{left:70%; animation-duration:2.9s; animation-delay:20ms}
/* Densified a third time 2026-09-16 ("add more flowers falling to slide 4
   phoolon ki holi") — 36 -> 52. Delays now span 0-1100ms (was 0-900ms), a
   fourth interleaved left-position pass fills the remaining gaps. */
.s4-fall--37{left: 4%;  animation-duration:2.4s; animation-delay:1040ms}
.s4-fall--38{left:16%;  animation-duration:3.1s; animation-delay:180ms}
.s4-fall--39{left:29%;  animation-duration:2.6s; animation-delay:620ms}
.s4-fall--40{left:41%;  animation-duration:2.9s; animation-delay:980ms}
.s4-fall--41{left:52%;  animation-duration:2.3s; animation-delay:300ms}
.s4-fall--42{left:64%;  animation-duration:3.4s; animation-delay:760ms}
.s4-fall--43{left:76%;  animation-duration:2.7s; animation-delay:60ms}
.s4-fall--44{left:87%;  animation-duration:2.5s; animation-delay:920ms}
.s4-fall--45{left:97%;  animation-duration:3.0s; animation-delay:400ms}
.s4-fall--46{left:10%;  animation-duration:2.8s; animation-delay:1100ms}
.s4-fall--47{left:36%;  animation-duration:2.4s; animation-delay:500ms}
.s4-fall--48{left:48%;  animation-duration:3.2s; animation-delay:140ms}
.s4-fall--49{left:73%;  animation-duration:2.6s; animation-delay:840ms}
.s4-fall--50{left:83%;  animation-duration:2.9s; animation-delay:280ms}
.s4-fall--51{left:20%;  animation-duration:2.5s; animation-delay:960ms}
.s4-fall--52{left:94%;  animation-duration:3.3s; animation-delay:580ms}

/* ==========================================================================
   SCENE 5 typography — PSD Page 5, 5 type layers. Accent #bb1219.
   ========================================================================== */
:where(#scene5 .scene__text > p){line-height:1.47; color:#1c421b; font-family:var(--f-body)}

/* Sizes/insets corrected 2026-09-15 to match .s3-* — same reasoning and
   same verification method as scene4's identical correction (see the SCENE
   4 typography block above): the small pixel-anchored sizes here were fit
   to the old psd-tools background's own baked-in type positions, not a
   deliberate design choice, and scene3 is this site's own reference for
   correctly-sized event-scene typography. .s5-time/.s5-venue's font-size
   comes from the shared rule near the end of this file. Subtitle is the one
   exception to the flat 22%/22% every other scene uses here: "Tilak Ki
   Shubh Shuruaat, Khushiyon Ka Aagaaz" is long enough that 22% wraps it to
   2 lines, colliding with .s5-date below it — probed directly (18% is the
   narrowest inset with real margin under the 19% single-line threshold). */
/* 1 — "Tilak Ceremony" — 256,110 → 744,214 · Tempting 44.6px */
.s5-title    {left:14%;  right:14%;  top:7.33%;  font-size:6.60cqw;
              font-family:var(--f-script); color:#bb1219}
/* 2 — "Tilak Ki Shubh Shuruaat…" — 211,225 → 792,265 · Aladin */
/* 2026-10-05 audit: the top-right leaf in the Tilak artwork reaches ~18% down
   and covered the end of the subtitle's first line; insets alone (18->20%)
   didn't clear it, so subtitle/date/time/venue move down 3.2-2.9% together
   (spacing unchanged) — the turbans don't start until ~46%, venue now ends
   ~38.8%. */
.s5-subtitle {left:20%;  right:20%;  top:18.20%; font-size:3.30cqw; line-height:1.32;
              font-family:'Aladin', cursive}
/* 3 — date — 207,285 → 793,328 */
.s5-date     {left:12%;  right:12%;  top:24.900%; font-size:4.10cqw; color:#bb1219}
/* 4 — time — 371,344 → 628,369 */
.s5-time     {left:22%;  right:22%;  top:28.830%}
/* 5 — venue, 3 lines — 324,401 → 677,510 · explicit leading */
.s5-venue    {left:16%;  right:16%;  top:32.630%; line-height:1.40}

/* ==========================================================================
   SCENE 6 typography — PSD Page 6, 5 type layers. A dark scene: all white.

   Four of the five blocks carry an OuterGlow in the PSD — size 10, 100%
   opacity, colour rgb(13,10,18), choke 10, Normal blend. That is a DARK halo
   behind white type, holding it legible over the neon background, and it is
   reproduced here as a text-shadow. The "Sangeet" title has no glow in the
   PSD and gets none here.
   ========================================================================== */
:where(#scene6 .scene__text > p){line-height:1.47; color:#ffffff; font-family:var(--f-body)}
.s6-subtitle, .s6-date, .s6-time, .s6-venue{
  text-shadow:0 0 .5cqw #0d0a12, 0 0 1cqw #0d0a12;
}

/* Sizes/insets corrected 2026-09-15 to match .s3-* — same reasoning as
   scene4/5 above. The title's old asymmetric insets (reproducing the PSD's
   own off-centre ink bbox for the substitute font) are dropped along with
   them: Candlescript Pro's ink centres differently than that measurement
   assumed, so keeping it would no longer reproduce anything real — plain
   symmetric insets like every other scene here. .s6-time/.s6-venue's
   font-size comes from the shared rule near the end of this file. */
/* 1 — "Sangeet" — 346,55 → 631,173 · Tempting 44.6px, no glow. */
.s6-title    {left:14%;  right:14%;  top:22.00%;  font-size:6.60cqw;
              font-family:var(--f-script)}
/* 2 — "Symphony Of Love" — 369,186 → 634,230 · Aladin */
.s6-subtitle {left:18%;  right:18%;  top:30.50%; font-size:3.30cqw; line-height:1.32;
              font-family:'Aladin', cursive}
/* 3 — date — 166,253 → 834,303 */
.s6-date     {left:12%;  right:12%;  top:40.500%; font-size:4.10cqw}
/* 4 — time — 354,321 → 644,349 */
.s6-time     {left:22%;  right:22%;  top:45.000%}
/* 5 — venue, 3 lines — 298,386 → 702,510 · explicit leading */
.s6-venue    {left:16%;  right:16%;  top:49.300%; line-height:1.40}

/* ==========================================================================
   SCENE 7 typography — PSD Page 7.

   ⚠️ The page holds TEN type layers, but only these FIVE render. The other
   five sit in a hidden group ("Text copy") — an alternate cream/white
   colourway for a different background, offset a constant 2.80% above these.
   Using all ten would print every string twice.
   ========================================================================== */
:where(#scene7 .scene__text > p){line-height:1.47; color:#043f40; font-family:var(--f-body)}

/* Sizes/insets corrected 2026-09-15 to match .s3-* — same reasoning as
   scene4/5/6 above. .s7-time/.s7-venue's font-size comes from the shared
   rule near the end of this file. */
/* 1 — "Baraat" — 376,79 → 628,161 · Tempting 44.6px */
.s7-title    {left:14%;  right:14%;  top:5.27%;  font-size:6.60cqw;
              font-family:var(--f-script); color:#74031a}
/* 2 — "A Royal Journey Towards Forever" — 294,194 → 709,233 · Aladin */
.s7-subtitle {left:18%;  right:18%;  top:12.93%; font-size:3.30cqw; line-height:1.32;
              font-family:'Aladin', cursive}
/* 3 — date — 217,254 → 783,297 */
.s7-date     {left:12%;  right:12%;  top:19.930%; font-size:4.10cqw; color:#74031a}
/* 4 — time — 364,313 → 635,338 */
.s7-time     {left:22%;  right:22%;  top:23.870%}
/* 5 — venue, 3 lines — 324,370 → 677,479 · explicit leading */
.s7-venue    {left:16%;  right:16%;  top:27.670%; line-height:1.40}

/* ==========================================================================
   SCENE 8 typography — PSD Page 8, 5 type layers. Accent #980525.
   ========================================================================== */
:where(#scene8 .scene__text > p){line-height:1.47; color:#2a4c1d; font-family:var(--f-body)}

/* Sizes/insets corrected 2026-09-15 to match .s3-* — same reasoning as
   scene4/5/6/7 above. .s8-time/.s8-venue's font-size comes from the shared
   rule near the end of this file. */
/* 1 — "Varmala" — 358,86 → 642,172 · Tempting 44.6px */
.s8-title    {left:14%;  right:14%;  top:5.73%;  font-size:6.60cqw;
              font-family:var(--f-script); color:#980525}
/* 2 — "Where Two Hearts Become One" — 295,207 → 707,237 · Aladin */
.s8-subtitle {left:22%;  right:22%;  top:13.80%; font-size:3.90cqw;
              font-family:'Aladin', cursive}
/* 3 — date — 204,269 → 795,315 */
.s8-date     {left:12%;  right:12%;  top:17.93%; font-size:4.10cqw; color:#980525}
/* 4 — time — 359,331 → 639,357 */
.s8-time     {left:22%;  right:22%;  top:22.07%}
/* 5 — venue, 3 lines — 315,391 → 685,505 · explicit leading */
.s8-venue    {left:16%;  right:16%;  top:26.07%; line-height:1.40}

/* ==========================================================================
   SCENE 9 typography — PSD Page 9, 5 type layers. Accents #601829 / #743811.
   ========================================================================== */
:where(#scene9 .scene__text > p){line-height:1.47; color:#743811; font-family:var(--f-body)}

/* Sizes/insets corrected 2026-09-15 to match .s3-* — same reasoning as
   scene4/5/6/7/8 above. .s9-time/.s9-venue's font-size comes from the
   shared rule near the end of this file. */
/* 1 — "Phera" — 387,34 → 613,120 · Tempting 44.6px */
.s9-title    {left:14%;  right:14%;  top:2.27%;  font-size:6.60cqw;
              font-family:var(--f-script); color:#601829}
/* 2 — "Seven Sacred Steps, One Beautiful Journey" — Aladin */
.s9-subtitle {left:18%;  right:18%;  top:10.60%; font-size:3.30cqw; line-height:1.32;
              font-family:'Aladin', cursive}
/* 3 — date */
/* 2026-10-05 audit: venue's last line sat at the canopy finial (~33.7%). A
   first attempt moving date/time/venue UP 2.5% collided with the two-line
   subtitle (ends 16.4%); corrected: date 17.0 (original 17.63), venue
   line-height 1.40 -> 1.28 so the 3-line venue ends ~33.4%, just above the
   finial. Measured on the live page, not guessed. */
.s9-date     {left:12%;  right:12%;  top:17.000%; font-size:4.10cqw; color:#601829}
/* 4 — time */
.s9-time     {left:22%;  right:22%;  top:21.300%}
/* 5 — venue, 3 lines · explicit leading */
.s9-venue    {left:16%;  right:16%;  top:24.900%; line-height:1.28}

/* ==========================================================================
   SCENE 10 typography — PSD Page 10, 4 visible type layers (a 5th, "Phera",
   is hidden — a leftover from an earlier draft, not this page's content;
   see config.js's own comment on `gala`). Sizes match the established scale
   scenes 3-9 already share; only the top positions are this page's own.

   No .s10-title (again): tried live text twice during the 2026-09-17
   redesign — first --f-script ("this font is not good"), then 'Aladin'
   two-line — but the owner asked for the exact original piece rather than
   a re-typeset, so the title is back to being an image, same as before the
   redesign, just now its own sprite instead of part of the base painting.
   See .deco--s10-title-art in the deco block below and index.html's own
   comment on that element for the extraction method. */
:where(#scene10 .scene__text > p){line-height:1.47; color:#e8e0c8; font-family:var(--f-body)}
/* Repositioned 2026-10-05 for the new Gala Dinner background (owner: "use
   this as the gala dinner slide background"). The new art has an open navy
   sky from ~8% to ~55% of the scene height (string lights/lanterns above,
   the dinner table's heads start ~58%), no baked-in title — so a live
   .s10-title (same script face as .s6-title) now leads a stack that fills
   that sky, using this page's usual tiny inter-line gaps. Values are
   starting estimates from measured per-line heights of the other scenes;
   verified against live DOM rects after deploy (see MOTION.md). */
.s10-title   {left:14%;  right:14%;  top:16.00%; font-size:6.60cqw;
              font-family:var(--f-script)}
.s10-subtitle{left:18%;  right:18%;  top:22.80%; font-size:3.30cqw; line-height:1.32;
              font-family:'Aladin', cursive}
.s10-date    {left:15%;  right:15%;  top:31.80%; font-size:4.10cqw; color:#e8e0c8}
.s10-time    {left:25%;  right:25%;  top:36.10%}
.s10-venue   {left:18%;  right:18%;  top:39.60%; line-height:1.40}

/* ==========================================================================
   SCENE 11 typography — PSD Page 11, 3 type layers. The closing card: a
   signed farewell, not an event, so it doesn't use the shared title/
   subtitle/date/time/venue shape every scene above does — three fields of
   its own instead (see config.js's `closing` and script.js's population).
   ========================================================================== */
:where(#scene11 .scene__text > p){line-height:1.47; color:#5c3a1e; font-family:var(--f-body)}
/* 1 — "Warm Regards," — 279,451 → 712,537 · Tempting */
.s11-greeting{left:20%;  right:20%;  top:30.07%; font-size:5.20cqw;
              font-family:var(--f-script); color:#980525}
/* 2 — "Agrawal & Dhutharia Family" — 161,591 → 843,647 */
.s11-family  {left:10%;  right:10%;  top:39.40%; font-size:4.60cqw; color:#5c3a1e}
/* 3 — "We look forward to your presence!" — 226,681 → 769,719 */
.s11-message {left:14%;  right:14%;  top:45.40%; font-size:3.40cqw}

/* ==========================================================================
   SCENE 12 — RSVP. New, not PSD-sourced. History: a full-bleed photo with
   one word over it (2026-09-23) -> a cream card with floral corners and a
   small framed/masked photo (2026-09-24, 2026-09-29) -> briefly a 3-photo
   swipeable gallery (2026-09-29) -> back to a full-bleed photo, 2026-09-30
   (owner, sending a new photo: "Full page photo, add text on top"),
   confirmed rather than assumed: this photo replaces the gallery outright,
   and the cream/floral decoration is dropped so the photo fills the scene
   edge-to-edge — the same full-bleed-photo pattern SCENE 6 and SCENE 10
   already use below. Type styling INITIALLY copied that precedent's white-
   on-dark-glow treatment, but that precedent's own photos are dark night
   scenes — this photo's text zone is a bright, hazy daylight patch
   (sampled directly from the shipped art: 74-84% average brightness across
   the whole heading/message/note/contact band, worst at the contact block,
   213/255), so white text with only a thin dark glow was fighting a
   background that was already nearly white. Confirmed as a real bug, not
   assumed — see the 2026-09-30 fix note below.

   FIXED 2026-09-30 (owner: "rsvp text have lot of gap between sentences
   and the text not visible pls check for color change") — two separate,
   confirmed problems:
   1. Colour: message/note/contact were white-on-dark-glow, illegible
      against this specific photo's bright zone (worst on "VIVAH BY
      CONNECTX" — smallest font, least ink per glyph for the glow to grip).
      Flipped to dark text (#3d2a10, this site's established brown) with a
      WHITE/light glow instead — the correct pairing for a light
      background, and the same "match the glow to what's actually behind
      it" principle scene6's dark-glow used, just inverted for a lighter
      photo. The crimson heading is untouched — it already read fine and
      wasn't part of the report.
   2. Spacing: the five lines' top:% values were leftover placeholders from
      before this photo was even chosen, with no relation to how tall each
      line actually renders — message and note in particular sat ~35-37px
      apart from their neighbours for no reason. Retimed from each
      element's own measured height (live DOM rects, not guessed) for even,
      tight gaps matching the rest of this page's convention. */
:where(#scene12 .scene__text > p){line-height:1.47; color:#ffffff; font-family:var(--f-body)}
.s12-message, .s12-note, .s12-contact-label, .s12-contact-phone{
  color:#3d2a10;
  text-shadow:0 0 .6cqw rgba(255,255,255,.95), 0 0 1.4cqw rgba(255,255,255,.85),
              0 1px 2px rgba(255,255,255,.9);
}

/* Type. All five lines stacked in the photo's own open sky/blur area above
   the couple's heads (measured live — see MOTION.md's 2026-09-30 entry for
   the exact rect check) so nothing sits across a face. */
/* Fonts changed 2026-10-05 (owner: "rsvp slide fonts are not easy to
   readable pls use fonts that match the slide and easy to readable").
   Two causes: the heading used the ornate Candlescript script, whose "RSVP"
   capitals read as a different word at a glance; and the body lines were
   Cormorant Garamond at 400 weight, partly italic — hairline strokes that
   vanish over a bright photo. Now everything is the page's own body family
   (Cormorant Garamond, already loaded, so it still matches the other
   slides) at 600 weight, upright, slightly larger; the heading is the same
   face in capitals with wide tracking. Light glow retained. */
.s12-heading{left:0; right:0; top:6.5%; font-family:var(--f-body);
             font-size:8.2cqw; font-weight:600; letter-spacing:.16em;
             text-transform:uppercase; color:#980525; line-height:1.1;
             text-shadow:0 0 .6cqw rgba(255,255,255,.95), 0 0 1.4cqw rgba(255,255,255,.85),
                         0 1px 2px rgba(255,255,255,.9)}
/* 2026-10-05 audit: 4.4cqw/12% -> 4.1cqw/14%; the one-line message ran
   almost edge to edge and could clip on narrower phones. */
.s12-message{left:14%; right:14%; top:15.5%; font-size:4.1cqw; font-weight:600}
.s12-note   {left:14%; right:14%; top:21.0%; font-size:3.8cqw; font-weight:600}
.s12-contact-label{left:0; right:0; top:29.5%; font-size:3.1cqw; font-weight:600;
                   letter-spacing:.1em; text-transform:uppercase}
.s12-contact-phone{left:0; right:0; top:33.0%; font-size:4.8cqw;
                   font-weight:700; letter-spacing:.03em}

/* Groom-side page (WP page 33183, /piyush-weds-riddhi/), 2026-10-15: its RSVP
   photo (scene-12-gs-v1.webp) has a very dark stone arch down the left third
   (mean luminance 15-53 in the text band) and bright sky centre/right (129-220),
   so the dark-brown text used on the original photo would vanish on the left.
   The whole text block moves into the bright right-hand area (left 38%, right
   16% — the 16% keeps it inside the phone crop, see --crop notes above) and
   wraps to more lines. Scoped by body.page-id-33183: no effect on any other page.
   Values are a first placement; verified against live DOM rects after deploy. */
body.page-id-33183 .s12-heading,
body.page-id-33183 .s12-message,
body.page-id-33183 .s12-note,
body.page-id-33183 .s12-contact-label,
body.page-id-33183 .s12-contact-phone{left:40%; right:19%}
/* first live check: right:16% put the first line flush against the phone's
   right edge (the 16% was computed against the crop but landed at 372/375px),
   so 19%; fonts trimmed one notch so the block wraps to fewer lines. */
body.page-id-33183 .s12-heading{top:6.5%}
body.page-id-33183 .s12-message{top:14.5%; font-size:3.8cqw}
body.page-id-33183 .s12-note{top:23.0%; font-size:3.5cqw}
body.page-id-33183 .s12-contact-label{top:33.0%}
body.page-id-33183 .s12-contact-phone{top:36.4%}

/* ==========================================================================
   DECORATIVE MOTION
   A small capability inside the existing scene system — not an engine, not a
   library. Six sprites, one keyframe rule, per-element custom properties.

   Rules it obeys:
   · Only clearly decorative assets move (peacocks, floral sprays). Structural
     artwork — sky, gold frame, palace, archway, and the peacocks' own ground
     shadows — stays in the flat base image and cannot move.
   · transform and opacity ONLY. No layout property is animated, so motion is
     incapable of shifting a measured text position or causing layout shift.
   · Entrance and idle motion are on DIFFERENT elements: the wrapper carries
     .reveal (opacity + translateY, fired by the existing IntersectionObserver),
     the inner <img> carries the idle sway. They never fight over `transform`.
   · Negative --delay starts each element mid-cycle, so six elements sharing
     one keyframe never move in lockstep.
   ========================================================================== */
.scene__deco{position:absolute; inset:0; pointer-events:none}
.scene__petals{position:absolute; inset:0; pointer-events:none}
.deco{position:absolute}
.deco img{
  width:100%; height:auto; display:block;
  transform-origin:var(--origin, 50% 100%);
  animation:var(--anim, deco-sway) var(--dur, 8s) var(--ease, ease-in-out) var(--delay, 0s) infinite;
  will-change:transform;
}

/* All four bird decos (scene1 + scene2, left + right), 2026-09-11 — real
   hummingbird footage ("Slide 2 BG 1.mp4", supplied), not a redraw. The clip
   contained BOTH a left- and a right-facing bird already, at nearly the PSD
   decos' own positions, so one file covers all four instances (scene1 and
   scene2 reuse the identical left sprite and the identical right sprite —
   same decorative motif in two places is normal, and it halves the asset
   weight and the browser's decode work).

   First pass used only 12 frames (0.5s) and read choppy against the source
   clip — reported directly ("in my mp4 video its smooth but in the website
   not look good"). Root cause, confirmed by measurement, not guessed: 12
   discrete steps() jumps is inherently coarser than 24fps video, AND that
   12-frame window's start/end frames didn't match, so the loop SNAPPED once
   every half-second — a rhythmic stutter on top of the coarseness. Fixed by
   searching the full 239-frame clip for a genuinely seamless loop (per-pixel
   diff between every candidate start/end pair at several loop lengths —
   scratchpad pipeline): 48 frames (2.000s, exactly the clip's own 24fps, no
   speed distortion), start=end diff ~0.15 — visually identical endpoints,
   confirmed side by side (scratchpad loop_endpoints_check.png). Same colour-
   key as before (flat rgb(221,233,240) background, soft threshold ramp,
   verified against the real site sky colour).

   Continuous wing-flap removed 2026-09-12, then RESTORED the same day
   ("Birds flying I need like a gif") — unlike the opening doves (a held
   moment before a single tap-triggered action), the birds are ambient
   scene decoration with no trigger to defer to, so a continuous loop is
   the actual intended effect here, not something to hold back until an
   interaction. Two animations on one element, exactly the pattern
   `.deco img` uses for the shared hover/sway — the flap is ADDITIVE: the
   wrapper's existing --anim/--dur/--lift/--tilt custom properties still
   drive the same up-down float every other bird deco has (transform),
   independent of background-position stepping through the flap frames —
   the two properties don't contend, so both run in parallel with zero
   conflict. */
.bird-flap{
  display:block; width:100%; height:auto;
  background-repeat:no-repeat;
  transform-origin:var(--origin, 50% 100%);
  animation:var(--anim, deco-hover) var(--dur, 8s) var(--ease, ease-in-out) var(--delay, 0s) infinite,
            bird-flap-frames var(--flap-dur, 2s) steps(var(--flap-n, 48)) infinite;
  will-change:transform, background-position;
}
/* Scene 1's birds were briefly simplified to a static drift (no wing-flap)
   2026-09-12, then reverted the same day ("wings open flying animation of
   birds") — back to matching Scene 2: real wings actually opening/closing
   via the flap frames, not just a still pose drifting. */
@keyframes bird-flap-frames{ from{background-position-x:0%} to{background-position-x:100%} }
/* Left sprite: 48 frames, tile 187x167. Right sprite: 48 frames, tile
   199x178 (each bird's own measured union bbox — see the pipeline note
   above). background-image is NOT set here — deliberately: this stylesheet
   deploys as-is into an assets/…/css/ subfolder that doesn't exist locally,
   while the deco images live one level up from THAT but at the SAME level
   as the local assets/ folder — two different relative depths, and a single
   url() here can only be correct for one of them. The existing pipeline
   already solves exactly this (every other asset reference lives in
   index.html as "assets/…", which gen_template.py rewrites to the PHP $rwp
   base for the server and leaves alone for local preview) — so the image is
   set as an inline style on each element in index.html instead. */
.bird-flap--l{ background-size:4800% 100%; --flap-n:48; aspect-ratio:187 / 167 }
.bird-flap--r{ background-size:4800% 100%; --flap-n:48; aspect-ratio:199 / 178 }

/* Three motion languages, chosen by what the object physically IS.

   deco-sway  — anything rooted: a stem, a branch, a bird's feet, a garland's
                hanging point. Rotation about that anchor, so the contact point
                never moves.
   deco-hover — anything airborne. Birds have no ground contact and no cast
                shadow, so a vertical bob is the honest motion; rotating them
                about a fixed point would look pinned rather than flying.
   deco-spin  — a disc. A record turns on its spindle, so it gets a real,
                continuous rotation (linear, never eased — a turntable does not
                accelerate and decelerate).

   Amplitudes were raised substantially after review: the first pass
   (0.3-0.6 degrees) was measurably running but not perceptible to a viewer,
   which defeats the point. These are tuned to be *noticed* while staying
   secondary to the artwork. */
@keyframes deco-sway{
  0%,100%{transform:rotate(calc(var(--sway,1.4deg) * -1)) scale(1)}
  50%    {transform:rotate(var(--sway,1.4deg)) scale(var(--breathe,1))}
}
@keyframes deco-hover{
  0%,100%{transform:translateY(calc(var(--lift,5%) * -1)) rotate(calc(var(--tilt,2deg) * -1))}
  50%    {transform:translateY(var(--lift,5%))            rotate(var(--tilt,2deg))}
}
@keyframes deco-spin{
  from{transform:rotate(0deg)}
  to  {transform:rotate(360deg)}
}

/* deco-flicker — fire. Scale about the base plus a small opacity dip, so the
   pit stays put and the flame reads as pulsing. Stops are deliberately
   asymmetric (0 / 35 / 70) so the loop does not feel mechanical, and the cycle
   is much shorter than any sway: fire moves faster than foliage. */
@keyframes deco-flicker{
  0%,100%{transform:scale(1);                    opacity:1}
  35%    {transform:scale(var(--breathe,1.045)); opacity:.93}
  70%    {transform:scale(1.015);                opacity:.98}
}

/* Positions are the PSD layer bboxes, verbatim. Durations are deliberately
   co-prime-ish and delays negative, so cycles never re-synchronise and the
   loop never becomes visible. */

/* --- Scene 1 --- hummingbirds fly; side vines sway from their top root --- */
.deco--s1-vine-l  {left: -0.4%; top: 0.000%; width:35.4%;
                   --origin:0% 0%;     --sway:1.4deg; --dur:7.4s; --delay:-3s}
.deco--s1-vine-r  {left: 65.0%; top: 0.000%; width:35.4%;
                   --origin:100% 0%;   --sway:1.4deg; --dur:8.1s; --delay:-8s}
.deco--s1-bird-l  {left: 12.2%; top:31.200%; width:16.2%;
                   --anim:deco-hover;  --lift:8.0%; --tilt:2.6deg; --dur:3.0s; --delay:-1s}
.deco--s1-bird-r  {left: 71.8%; top:31.200%; width:16.2%;
                   --anim:deco-hover;  --lift:7.4%; --tilt:2.3deg; --dur:3.4s; --delay:-3s}

/* --- Scene 2 --- two hummingbirds, four botanical sprays --- */
.deco--s2-floral-tl{left:-5.4%; top: 0.000%; width:32.8%;
                   --origin:0% 0%;     --sway:1.5deg; --dur:7.0s; --delay:-2s}
.deco--s2-floral-tr{left:70.2%; top: 0.000%; width:35.4%;
                   --origin:100% 0%;   --sway:1.5deg; --dur:7.7s; --delay:-7s}
.deco--s2-floral-ml{left:-3.4%; top:36.733%; width:22.4%;
                   --origin:0% 50%;    --sway:1.7deg; --dur:6.2s; --delay:-5s}
.deco--s2-floral-mr{left:80.8%; top:38.933%; width:22.4%;
                   --origin:100% 50%;  --sway:1.7deg; --dur:6.9s; --delay:-9s}
.deco--s2-bird-l  {left: -0.4%; top:22.933%; width:15.3%;
                   --anim:deco-hover;  --lift:8.0%; --tilt:2.6deg; --dur:2.9s; --delay:-2s}
.deco--s2-bird-r  {left: 84.3%; top:11.333%; width:15.4%;
                   --anim:deco-hover;  --lift:7.4%; --tilt:2.3deg; --dur:3.3s; --delay:-4s}

/* --- Scene 3 --- peacocks pivot at their feet, so the ground shadows left in
       the base image stay correct --- */
.deco--s3-spray-l  {left:  0.1%; top: 0.000%; width:38.3%;
                   --origin:0% 0%;     --sway:1.4deg; --dur:6.8s; --delay:-2s}
.deco--s3-spray-r  {left: 61.7%; top: 0.000%; width:38.3%;
                   --origin:100% 0%;   --sway:1.4deg; --dur:7.4s; --delay:-6s}
/* Macaw (2026-09-14 — see index.html for full provenance). Real animated
   WebP (its own wing-flap baked in), wrapped in the same --anim:deco-hover
   treatment scene1/2's flying hummingbirds use (gentle overall bob layered
   over the asset's own internal motion) rather than the standing/pivoting
   --sway treatment the grounded peacocks below use.

   Box centred on the OLD painted parrots' own measured centre (pixel bbox
   [208,870]-[258,941] / [756,870]-[802,939] in the 1000x1500 background
   art, scratchpad/find_parrot_bbox.py), sized generously (11.5%, well over
   the ~5%-wide originals) so it fully occludes them with margin to spare
   rather than needing pixel-perfect alignment.

   A second pair briefly existed flanking the title too (top:36%, same
   --anim:deco-hover treatment) — removed same day (owner correction: "why
   2 pairs of parrots... use only one pair which is best"). This one was
   kept: it fills a role the original artwork already had, the title pair
   was a bonus addition with nothing to replace. */
.deco--s3-macaw-l{left: 17.55%; top:55.680%; width:11.5%;
                   --anim:deco-hover; --lift:4.2%; --tilt:1.6deg; --dur:3.0s; --delay:-3s}
.deco--s3-macaw-r{left: 72.15%; top:55.680%; width:11.5%;
                   --anim:deco-hover; --lift:3.9%; --tilt:1.4deg; --dur:3.3s; --delay:-6s}
/* Peacock top/left shifted (was 7.8%/73.467% and 72.4%/74.133%) — owner
   correction 2026-09-14 ("the peacocks on flowers pls correct it"): the
   original values were tuned for the old static asset's own tight crop:
   the new animated v2 asset's crop is padded to cover its whole idle
   head-turn (union bbox across all frames, not one still pose), and at the
   old position that padding put the feet/tail low and outward enough to
   land on the corner flower-and-diya clusters instead of the lawn between
   them and the pathway (confirmed against the background art directly,
   scratchpad/peacock_area.png). Moved up and inward onto clean grass. */
/* .deco--s3-peacock-l/-r removed 2026-09-22 — see index.html's comment at
   the (now-removed) sprite markup: the new background art has its own
   baked-in, animated peacock pair, and the sprites on top doubled them. */
.deco--s3-corner-l {left: -0.1%; top:80.067%; width:29.0%;
                   --origin:0% 100%;   --sway:1.5deg; --dur:6.5s; --delay:-3s}
.deco--s3-corner-r {left: 71.0%; top:80.000%; width:29.0%;
                   --origin:100% 100%; --sway:1.5deg; --dur:7.1s; --delay:-7s}

/* --- Scene 4 --- the garland/bouquet sway sprites this comment used to
       describe were retired 2026-09-15: that background baked them in
       directly. The urli-bowl deco (.deco--s4-floral-pot) that replaced
       them is ALSO retired 2026-10-02 — the Haldi background that replaced
       the art underneath it (see index.html's scene4 comment) has its own
       urli baked in too; keeping this sprite would have doubled it up and
       misaligned it, same reasoning as the 2026-09-22 scene3 peacock
       removal just above. No .deco rules remain for scene4. */

/* --- Scene 5 --- no .deco rules here any more, and no .s5-tilak-reveal.
       2026-09-18 ("for tilak slide remove that big red tilak and use this
       as the reveal for it") — same full replacement as scenes 7/9/11's
       (see index.html's comment on this scene for the method). The 5
       botanicals, the marigold pair AND the red kumkum-plume reveal are
       all gone: the new animation bakes in its own palace/garden/corner
       florals and replaces the plume with a real hands-presenting-thali
       reveal instead. Full history of what each of these was — including
       the data-defer-url/LiteSpeed-CDN-rewriter trap the plume's own
       comment documented — is kept in MOTION.md's Scene 5 entry. */

/* --- Scene 6 --- no .deco rules any more (2026-09-20). Chandeliers, disco
       balls, neon clusters and the spinning record are baked into one
       animation (scene-06-v2.webp) — see index.html and MOTION.md. */

/* --- Scene 7 --- no .deco rules here any more. 2026-09-18 ("for baraat
       slide use this one, replace total background with this and add the
       text") — same full replacement as scene11's (see index.html's
       comment on that scene for the method, and on this one for what
       changed here specifically). The horse, both parasols, both
       botanical sprays and the flag cluster are all baked into
       scene-07-v2.webp's own frames now, already animated. Full history
       of what each of these rules was — including the horse's own
       2026-09-16 real-footage swap — is kept in MOTION.md's Scene 7 entry. */

/* --- Scene 8 --- no .deco rules any more. 2026-09-19: scene8 is now one
       full-scene animation (scene-08-v2.webp) with the garland stand baked
       in — see index.html's comment and MOTION.md's Scene 8 entry. */
/* --- Scene 9 --- no .deco rules here any more. 2026-09-18 ("pls replace
       the pehra slide with this and add the text") — same full replacement
       as scenes 7/11's (see index.html's comment on this scene for the
       method). The fire and both floral corners are baked into
       scene-09-v2.webp's own frames now, already animated (the fire
       genuinely flickers). Full history — including why this page needed
       a front deco plane at all — is kept in MOTION.md's Scene 9 entry. */

/* --- Scene 10 --- no .deco rules any more (2026-09-20). The disco balls,
       chandeliers, corner clusters and the extracted "GALA DINNER" title
       sprite from the 2026-09-17 redesign are all baked into one animation
       now (scene-10-v3.webp) — see index.html's comment and MOTION.md. */

/* --- Scene 11 --- no .deco rules here any more. 2026-09-18 ("pls replace
       the last slide with this and add the text to it"): the owner supplied
       a single unified animation (scene-11-v4.webp, see index.html's own
       comment on this scene) that bakes in everything 3 separate sprite
       generations used to build here — hands joining, both peacocks,
       all 3 butterflies, even the fountain's water and the sky wash-in —
       already composited and already animated. The `.deco--s11-hands`,
       `.deco--s11-peacock-l/-r` and `.deco--s11-butterfly-*` rules that
       used to live here are gone, not just unused: their sprites no longer
       exist in the markup, so a stale rule would just be dead weight.
       Full history of what each of those was and why — the green-screen
       hand extraction, the white-key peacock extraction, the base-art sky
       reconstruction — is kept in MOTION.md's Scene 11 entry, since it's
       genuinely useful record of methods proven out on this project, even
       though none of it still applies to what's live. */

/* ==========================================================================
   LABEL TIER — tracking
   ==========================================================================
   Measured from the R4 reference: its small labels run 10-12px with 1.5-3.6px
   of tracking (0.15em-0.30em), against a 48px display face. That contrast —
   tiny, widely-tracked supporting type under a large display line — is what
   gives it its composure. Before this, `letter-spacing` appeared exactly ONCE
   in this entire stylesheet.

   Approved 2026-09-08: UPPERCASE at the reference's own 0.20em, with the size
   reduction that requires. Caps plus 0.20em is materially wider than the same
   string in mixed case, and these lines sit in measured PSD boxes, so several
   would have wrapped at their old sizes. The reductions below are MEASURED,
   not chosen: each label's natural (unwrapped) width was compared against its
   own box and the required scale computed — see scratchpad capsfit.js.

   Applied ONLY to label-role lines: times, venues, prompts, section labels and
   the countdown units. NOT to running prose (the invocation, shloka,
   salutation and body of the letter), where caps and tracking would wreck
   readability, and NOT to the display/script lines, which carry their own
   optical spacing. (Scene 2's old date/venue/residence/schedule-heading
   blocks were excluded on the same reasoning — each held a label AND its
   value in one paragraph, so uppercasing would shout the value too — but
   that whole block was removed 2026-09-12, so the exclusion is now moot.)

   Selectors are single classes, matching the scene rules' specificity, and
   sit after them so they win on source order alone.
   ========================================================================== */
.s1-sub, .s1-tprompt, .cd-lab,
.s3-time, .s3-venue, .s4-time, .s4-venue, .s5-time, .s5-venue,
.s6-time, .s6-venue, .s7-time, .s7-venue, .s8-time, .s8-venue,
.s9-time, .s9-venue, .s10-time, .s10-venue{
  text-transform:uppercase;
  letter-spacing:var(--track-caps);
  /* Tracking adds width AFTER the last glyph, which shifts a centred line
     left by half of it. The matching indent puts that space back at the
     front so centred blocks stay optically true rather than relying on the
     shift being below the geometry gate's 0.5px tolerance. */
  text-indent:var(--track-caps);
}

/* --- measured size reductions -------------------------------------------
   Originally a 2.14cqw clamp applied to scenes 4-9 only, on the theory that
   scene3 was "the one scene of this group actually visible" (4-9 were
   slide--hidden) and so was the only one worth sizing generously. That
   stopped being true once scenes 4-9 were un-hidden — confirmed the hard
   way twice: scene4's text stayed visibly smaller than scene3's after its
   own sizing was corrected 2026-09-15, because this shared rule sat AFTER
   it in source order and silently won on equal specificity (an .s4-time/
   .s4-venue opt-out was added to fix that). Now that scenes 5-9 ("use this
   font for all headings in the all slides and do the font size changes in
   remaining slides", 2026-09-15) get the identical correction, every scene
   in this group wants the same 3.30cqw — so the clamp-plus-per-scene-
   opt-out arrangement is retired and this is just the one shared value
   directly, no exceptions left to encode. Scene 1's three prompt lines span
   the full canvas (left:0/right:0) so they were never constrained here. */
.s3-time, .s3-venue, .s4-time, .s4-venue, .s5-time, .s5-venue,
.s6-time, .s6-venue, .s7-time, .s7-venue, .s8-time, .s8-venue,
.s9-time, .s9-venue, .s10-time, .s10-venue{font-size:3.30cqw}

/* ---- scroll reveal — R1's only motion, one effect ----
   --reveal-y is the rise distance, +18px = starts 18px BELOW its resting
   spot and rises up into place. A CSS variable, not a hardcoded value, so
   one element type can flip direction (see .scene__text > p.reveal below,
   2026-09-17: "the text should come from top") without a second, near-
   duplicate rule set — every other .reveal (decos, washes, sparkles) keeps
   this exact rise-from-below motion, untouched. */
.reveal{
  opacity:0; transform:translateY(var(--reveal-y, 18px));
  transition:opacity .85s var(--ease-rev), transform .85s var(--ease-rev);
  /* 2026-09-30 (owner: "smoother animations" on scene transitions/reveals).
     Not a retune of the tuned duration/easing above — the reveal starts the
     instant a scene's own full-bleed WebP (several are 13-16MB, still
     decoding at that moment) scrolls into view; without a compositor-layer
     hint the browser can decode that image on the same thread it's trying
     to animate opacity/transform on, which is the standard cause of a
     scroll-reveal feeling like it stutters rather than glides. will-change
     promotes the element to its own layer ahead of the transition so it
     animates independently of that decode work. Paired with decoding=
     "async" added to every <img> in this file, which moves the decode
     itself off the main thread. */
  will-change:opacity, transform;
}
.reveal.is-in{opacity:1; transform:none}

/* ==========================================================================
   SCENE ARRIVAL — the transition between event slides
   ==========================================================================
   The scenes are discrete full-bleed panels butted together at a zero gap, so
   there is no boundary to animate: a slide simply ends and the next begins.
   Everything inside it then faded in at once, on one duration, which is why
   the change of scene registered as nothing at all.

   Two changes, both purely additive to the existing one-effect reveal:

   1. The lines arrive in READING ORDER rather than together — title, then
      subtitle, then date, time, venue. A ~95ms step is enough to be felt as
      composure without the last line feeling late (5 lines = 380ms of spread
      against a 850ms transition, so they overlap heavily and still read as
      one gesture, not a queue).

   2. The easing changes to the reference's own curve, cubic-bezier(.16,1,.3,1)
      — easeOutExpo. It covers most of the distance almost immediately and
      then settles for a long time, which is what makes an arrival feel
      weighted rather than mechanical. Measured from R4's stylesheet, where it
      is one of six easings in use.

   Still transform + opacity only, so this cannot cause layout shift, and the
   geometry gate's measured end-state positions are untouched.
   ========================================================================== */
/* Text descends from ABOVE instead of rising from below, 2026-09-17
   ("once it opens, then the text should come from top... line by line"),
   starting scene3 and tried scene-by-scene from there. -24px, not just the
   shared rule's +18px sign-flipped: a judgement call, not a measured one —
   picked slightly longer than the shared distance since "coming down from
   above" reads as a smaller motion than "rising into place" at the same
   number of pixels, to the eye. Reading-order stagger (nth-of-type, below)
   and the arrival easing are already correct for this and are untouched.

   Duration slowed 2026-09-17 ("make little slow the text reveal on all
   slides") — 0.85s -> 1.15s, TEXT ONLY: overrides just the shared rule's
   duration on this more specific selector, same mechanism already used
   above for --reveal-y and the timing-function, so every non-text .reveal
   (decos, washes, sparkles, falling petals) keeps the original 0.85s,
   untouched. A judgement call on the amount, same as the -24px above —
   easy to retune. The per-scene delay overrides (nth-of-type stagger
   below, and scene4/5's post-wash push) are unaffected: those control WHEN
   each line starts, this controls how long each one takes once started. */
.scene__text > p.reveal{--reveal-y:-24px; transition-duration:1.15s; transition-timing-function:var(--ease-arrive)}
/* animation-delay alongside transition-delay: a themed glow (see REVEAL GLOW
   below) plays as a plain @keyframes animation, which does NOT respect
   transition-delay on its own — it would start the instant `.is-in` lands,
   regardless of how long that line's own fade-in is staggered. Left
   unsynced, the glow's bright peak would land while opacity was still near
   zero, wasted on invisible text. Matching the two delays keeps them in
   lockstep. Harmless on any scene that has no `animation` set — a delay on a
   property nothing uses does nothing. */
.scene__text > p.reveal:nth-of-type(1){transition-delay:0ms;    animation-delay:0ms}
.scene__text > p.reveal:nth-of-type(2){transition-delay:95ms;   animation-delay:95ms}
.scene__text > p.reveal:nth-of-type(3){transition-delay:190ms;  animation-delay:190ms}
.scene__text > p.reveal:nth-of-type(4){transition-delay:285ms;  animation-delay:285ms}
.scene__text > p.reveal:nth-of-type(5){transition-delay:380ms;  animation-delay:380ms}
.scene__text > p.reveal:nth-of-type(6){transition-delay:475ms;  animation-delay:475ms}
.scene__text > p.reveal:nth-of-type(n+7){transition-delay:570ms; animation-delay:570ms}

/* Decorative sprites settle in behind the type, slightly later and slower, so
   the artwork feels like it is arriving with the scene rather than snapping
   into place. Left/right pairs are offset from each other so a symmetrical
   composition does not animate as one rigid unit. */
.scene__deco .deco.reveal{
  transition-timing-function:var(--ease-arrive);
  transition-duration:1.05s;
}
.scene__deco .deco.reveal:nth-of-type(odd) {transition-delay:120ms; animation-delay:120ms}
.scene__deco .deco.reveal:nth-of-type(even){transition-delay:230ms; animation-delay:230ms}

/* Scene5 sequencing, 2026-09-16 ("first the reveal then the slide will be
   visible and all text and assets") — text arrives ~1.3s after the scene
   is scrolled to, not immediately, so it doesn't overlap the reveal in
   progress. Originally timed to let 6 real-animated botanicals finish
   arriving first (see MOTION.md); those sprites are gone as of 2026-09-18
   (full replacement, see index.html's own comment on this scene), but the
   same pause still serves the owner's original intent now that the reveal
   is the new tilak.webp animation itself getting going — kept as-is rather
   than reverting to the generic shared timing. ID-scoped to outrank the
   shared `.scene__text > p.reveal:nth-of-type()` rule: adding #scene5
   makes specificity (1,3,1) vs the shared rule's (0,3,1) -- an ID beats
   any number of classes regardless of source order -- same technique
   #scene1's reveal-glow override uses above.
   Values are the shared rule's own 0/95/190/285/380ms reading-order stagger
   with a flat +1300ms push, not a new stagger scheme, so the lines still
   arrive in reading order relative to each other. */
#scene5 .scene__text > p.reveal:nth-of-type(1){transition-delay:1300ms; animation-delay:1300ms}
#scene5 .scene__text > p.reveal:nth-of-type(2){transition-delay:1395ms; animation-delay:1395ms}
#scene5 .scene__text > p.reveal:nth-of-type(3){transition-delay:1490ms; animation-delay:1490ms}
#scene5 .scene__text > p.reveal:nth-of-type(4){transition-delay:1585ms; animation-delay:1585ms}
#scene5 .scene__text > p.reveal:nth-of-type(5){transition-delay:1680ms; animation-delay:1680ms}

/* ==========================================================================
   REVEAL GLOW — PROTOTYPE, scene1 only
   ==========================================================================
   The owner's brief: colour the reveal itself to the scene's own theme — the
   worked example given was a haldi (turmeric) ceremony glowing yellow. Scene1
   is the title scene, not a specific ceremony, so rather than invent a colour
   it uses `--gold` (#b98f57), already sampled from the PSD opening artwork
   and already in use elsewhere on the site (the tap prompt, the music
   toggle) — a warm, wedding-appropriate glow drawn from the existing
   palette, not a new one.

   As each line/sprite reveals, a soft glow blooms brightly around it and then
   settles to a faint ambient warmth that stays for as long as the element is
   visible, rather than disappearing once the fade completes — "gently alive"
   applied to light the way the rest of the site applies it to motion.
   `--reveal-glow-rgb` is a per-scene hook: setting it (as #scene1 does below)
   is what turns the effect on, so applying this to another scene later is
   one variable, not new rules — kept deliberately unset everywhere else
   until each is reviewed and approved the same way this one was.

   text-shadow for text, filter:drop-shadow for the sprite <img>s (text-shadow
   has no effect on a raster image). `both` fill mode: the 0% frame (no glow)
   holds through each element's own animation-delay, and the 100% frame (the
   settled ambient glow) persists after the 1.5s animation completes.

   Reduced motion needs no separate override: the project's existing blanket
   rule (`*{animation-duration:.001ms !important}`) already collapses this to
   its end state instantly, which is a static warm tint, not motion. */
#scene1{--reveal-glow-rgb: 185,143,87}   /* --gold decomposed to r,g,b */
/* Scene3's OWN accent, not scene1's gold reused — #ac034d, already the
   measured colour of .s3-title/.s3-date (see scene 3's own CSS rules).
   Different reveal, different scene: "Rajsi Aagman"/A Royal Welcome gets a
   rose-crimson wash and sparkle field instead of gold, so the two scenes are
   visually distinct rather than the same effect recoloured once. */
#scene3{--reveal-glow-rgb: 172,3,77}

/* Longhand, not the `animation` shorthand. The shorthand sets EVERY
   sub-property at once, including `animation-delay` (defaulting it to 0s
   since none was given here) — and because this ID-scoped selector
   outranks the plain-class `:nth-of-type()` stagger rule on specificity,
   that silent 0s reset was WINNING over the 95ms/190ms/etc. delays set
   above, regardless of source order. Caught by reading the computed style
   directly (animationDelay was measured as "0s", not "95ms") rather than
   by trusting the screenshot. Longhand here leaves animation-delay alone,
   so the higher-specificity nth-of-type rule is free to set it. */
#scene1 .scene__text > p.reveal.is-in{
  animation-name:reveal-glow-text;
  animation-duration:1.5s;
  animation-timing-function:var(--ease-arrive);
  animation-fill-mode:both;
}
#scene1 .scene__deco .deco.reveal.is-in img{
  animation-name:reveal-glow-img;
  animation-duration:1.5s;
  animation-timing-function:var(--ease-arrive);
  animation-fill-mode:both;
}
/* Strengthened 2026-09-08 — the owner reported seeing no change at real page
   scale. The numbers below were measured at 5px/.25 alpha settled, 16px/.85
   peak; correct in isolation (confirmed by instrumenting computed style
   directly) but too small a fraction of a ~50px letterform to read at normal
   viewing size once off an extreme zoomed crop. Roughly doubled throughout,
   and the settled (rest) state — what is on screen for all but the first
   second — now carries its own two-layer halo instead of a single thin one,
   so the effect reads without needing to catch the transient peak. */
@keyframes reveal-glow-text{
  0%   {text-shadow:0 0 0 rgba(var(--reveal-glow-rgb),0)}
  40%  {text-shadow:0 0 26px rgba(var(--reveal-glow-rgb),1), 0 0 52px rgba(var(--reveal-glow-rgb),.6)}
  100% {text-shadow:0 0 10px rgba(var(--reveal-glow-rgb),.5), 0 0 22px rgba(var(--reveal-glow-rgb),.22)}
}
@keyframes reveal-glow-img{
  0%   {filter:drop-shadow(0 0 0 rgba(var(--reveal-glow-rgb),0))}
  40%  {filter:drop-shadow(0 0 20px rgba(var(--reveal-glow-rgb),.95))}
  100% {filter:drop-shadow(0 0 9px rgba(var(--reveal-glow-rgb),.5))}
}

/* ==========================================================================
   REVEAL WASH — scene1 and scene3, each its own colour
   ==========================================================================
   The per-element glow above colours individual letters and sprites as they
   settle. What was actually being asked for is bigger: the SCENE itself
   should reveal through a colour tied to its content — the worked example
   given was a haldi ceremony revealing through yellow. Scene1 holds the
   couple's names and the two hummingbirds ("its bird and groom details"),
   so it reveals through the gold already established for that scene.

   The trigger/keyframes here are scene-agnostic on purpose (no `#scene1`
   prefix) — the ONLY thing that makes a scene's wash a particular colour is
   its own `--reveal-glow-rgb` (see where each scene sets it), so a second
   scene with its own theme (scene3: rose/crimson, its own PSD accent) needed
   one variable and a `.scene__wash` div, not new rules.

   `.scene__wash` is the LAST child of the scene's own `.scene` (see
   index.html), so plain DOM order — no `.scene__over`, `.scene__deco` or
   `.scene__text` rule sets a z-index — puts it above the artwork, the
   sprites and the text alike with nothing extra needed. It is NOT a generic
   `.reveal`: that class starts an element at opacity:0 and fades it IN, the
   opposite of what a wash needs (start covering, then disperse), so the
   compound selector `.scene__wash.reveal` overrides the base rule's
   opacity/transform outright.

   pointer-events:none throughout — the wash sits visually above the
   scratch-to-reveal canvas (scene1) while it's covering the scene, but never
   blocks the touch/click that canvas needs, at any point in the animation. */
.scene__wash.reveal{
  position:absolute; inset:0;
  opacity:1; transform:none;         /* override — NOT the generic .reveal start state */
  pointer-events:none;
  background:radial-gradient(circle at 50% 42%,
    rgba(var(--reveal-glow-rgb, 0,0,0),.88) 0%,
    rgba(var(--reveal-glow-rgb, 0,0,0),.55) 32%,
    rgba(var(--reveal-glow-rgb, 0,0,0),.16) 58%,
    rgba(var(--reveal-glow-rgb, 0,0,0),0) 78%);
}
.scene__wash.reveal.is-in{
  animation-name:reveal-wash;
  animation-duration:1.6s;
  animation-timing-function:var(--ease-arrive);
  animation-fill-mode:forwards;
}
@keyframes reveal-wash{
  0%   {opacity:.9;  transform:scale(1)}
  100% {opacity:0;   transform:scale(1.16)}
}
/* Everywhere else without an override below, --reveal-glow-rgb is unset, so
   the gradient above falls back to rgba(0,0,0,...) — but this rule only
   ever applies to elements that also carry `.reveal`, and only scenes 1, 3
   and 4 have a `.scene__wash` div at all (scene5's own flat-colour wash was
   removed 2026-09-18 along with the rest of that scene's old sprite set —
   see this file's own Scene 5 comment and MOTION.md), so the fallback is
   inert defence-in-depth, not something that can actually paint a black
   wash anywhere. */

/* Scene4, 2026-09-16 ("add ... the simillar reveal for this slide" + a
   YouTube gulal/colour-blast reference) — an IMAGE wash, not a flat colour
   or the radial glow: a synthetic multi-colour Holi powder-burst PNG (no
   real gulal footage existed to extract; confirmed with the owner via a
   preview before building this for real). background-size:cover fills the
   same full-bleed area the flat/radial washes use via `inset:0` on the
   shared rule; background-position centres the burst on the same point the
   art was generated around.

   THIS PATH IS LOCAL-PREVIEW-ONLY. Deployed CSS lives one directory deeper
   (css/rwp-vNN.css) than local styles.css does, so a plain relative
   "assets/..." path here resolves wrong in production — the exact same
   trap the Candlescript Pro @font-face hit (see gen_template.py's header
   comment). Fixed the same way: gen_template.py's own <style> block carries
   a second, $rwp-prefixed, HIGHER-SPECIFICITY copy of this rule (an added
   [aria-hidden="true"] attribute selector) for production, since the two
   rules tie on selector otherwise and source order would make the LINKED
   stylesheet (this file) win over the inline <style> that precedes it in
   <head> — specificity, not cascade order, is what needs to decide here. */
#scene4 .scene__wash.reveal{
  background-image:url('assets/deco/s4-holi-wash.webp');
  background-size:cover; background-position:center 40%;
}

/* ---- music (hidden unless a track is configured) ---- */
.music{
  position:fixed; right:4vw; bottom:4vw; z-index:40;   /* also anchors the ::after mute-slash below */
  width:44px; height:44px; border-radius:50%;
  border:1px solid var(--gold); background:rgba(255,255,255,.9);
  color:var(--gold); font-size:1rem; cursor:pointer;
}
/* playing = filled gold, muted = outline (2026-09-20, music added) */
.music[aria-pressed="true"]{background:var(--gold); color:#fff}
/* 2026-09-22 (owner: "when click on music icon show cross line on icon so
   it easily understandable") — the fill-color change alone was too subtle
   to read as on/off at 44px. A diagonal slash across the note, the
   standard mute idiom, makes it unambiguous. Corner-to-corner across the
   circle (150% of the box, so it clears both edges at 45°), currentColor
   so it always matches the note glyph's own color in either state. Also
   covers the "autoplay was blocked" fallback in script.js's playMusic()
   catch — that sets aria-pressed="false" too, so a visitor whose browser
   silently refused to autoplay sees the same "tap to unmute" cue instead
   of a note icon that looks like it's already playing. */
.music::after{
  content:""; position:absolute; left:50%; top:50%;
  width:150%; height:2px; background:currentColor;
  transform:translate(-50%,-50%) rotate(-45deg);
  opacity:0; transition:opacity 150ms ease; pointer-events:none;
}
.music[aria-pressed="false"]::after{opacity:1}

/* ---- wider screens: the same composition in a centred column, per
   BLUEPRINT §responsive (769-1024 -> ~560px, >1024 -> ~600px, and
   "do not stretch 1000px art to full desktop width").

   The cap MUST go on .scene, not on .scene__art. .scene is the
   container-query context, so capping it is what keeps 1cqw = 1/1000th of
   the artwork — and therefore every font-size and every top/left value —
   locked to the art. Capping only the <img> leaves .scene__text and all
   cqw units sized off the full viewport instead (measured: art 620px but
   text plane 1440px, "Riddhi" at 75px instead of 32px).

   ---- FULL-BLEED SCENES (owner decision, 2026-09-07) ----

   Scenes carry NO width cap at any breakpoint: they span the full window, so
   there is no empty margin left or right on desktop. Scene height follows the
   artwork's 2:3 ratio, so nothing is cropped and every measured text position
   still lands exactly where the PSD puts it.

   Accepted trade-off, stated rather than hidden: the artwork is 1000px wide
   natively, so a 1920px window upscales it 1.92x and it will look softer than
   at native size. The blueprint advised against this; the owner asked for
   full-bleed explicitly after seeing the capped version. Sharper artwork would
   need larger exports from the designer (see ASSET-REQUIREMENTS §A.1) — the
   layout does not have to change for that, only the source files.

   --col-open stays capped by viewport HEIGHT: the opening is one held moment
   and the whole envelope must be on screen, or its corner florals crop. ---- */
@media (min-width:769px){
  :root{--col-open: min(560px, 66.667vh)}
  .opening__stage{width:var(--col-open)}
}
@media (min-width:1025px){
  :root{--col-open: min(620px, 66.667vh)}
}

@media (prefers-reduced-motion:__iw_disabled){
  *,*::before,*::after{animation-duration:.001ms !important; transition-duration:.001ms !important}
  .reveal{opacity:1; transform:none}
  /* The blanket rule above would freeze each sprite at the 0% keyframe —
     i.e. permanently rotated by -sway — which would leave the composition
     subtly wrong rather than merely still. Reset explicitly so reduced motion
     yields the exact designed composition. */
  .deco img, .bird-flap, .dove-group__art{animation:none !important; transform:none !important}
}

/* ==========================================================================
   REVEAL SPARKLE — scene1 and scene3, each its own colour and shape mix
   ==========================================================================
   Researched rather than invented: the wash+glow alone read as "good but not
   sufficient" — what was missing is an actual sparkle, a specific, named
   effect with an established CSS technique (not a vague embellishment). The
   base shape is the standard 4-point sparkle/glint polygon documented across
   multiple independent sources (an 8-vertex clip-path alternating four outer
   tips with four inner corners pulled toward centre). `.star` (below) adds
   the OTHER shape explicitly asked for — "sparkle AND stars" — the classic
   5-point star, a different, more literal star silhouette than the 4-point
   glint, mixed in alongside it for genuine shape variety rather than more of
   the same glyph. Twinkle-via-opacity+scale with staggered per-element delay
   is the same documented pattern used for CSS starfields, applied here as a
   one-shot burst tied to the scene's own reveal rather than an infinite loop.

   Trigger/keyframes are scene-agnostic (see REVEAL WASH above for why) — a
   second scene (scene3) reuses the identical mechanism with its own colour
   and its own positions, not a copy of scene1's rules.

   Scene1: positioned at the couple's names and the two hummingbirds — the
   same "bird and groom details" the wash and glow already target, using the
   SAME measured PSD bboxes those rules use (.s1-bride/.s1-groom/
   .deco--s1-bird-l/r above), so all three effects agree on where the content
   actually is rather than each guessing independently.

   Last children of `.scene`, after `.scene__wash` — DOM order alone puts
   them above the wash too, so a sparkle glints as the wash clears rather
   than being hidden under it while it's still opaque. */
.sparkle{
  position:absolute;
  aspect-ratio:1;
  clip-path:polygon(50% 0%, 60% 40%, 100% 50%, 60% 60%, 50% 100%, 40% 60%, 0% 50%, 40% 40%);
  background:rgb(var(--reveal-glow-rgb, 255,255,255));
  filter:drop-shadow(0 0 4px rgba(var(--reveal-glow-rgb, 255,255,255),.9));
  pointer-events:none;
}
/* Was a 5-point star; changed to a HEART 2026-09-10 — reported "the stars
   are not looking nice, can add flowers or hearts". The class name is kept
   (`.star` is on dozens of sparkle spans across scenes 1 and 3) but the
   silhouette is now a heart: a 16-vertex polygon with the top cleft and a
   pointed base, smooth enough to read cleanly at the 15-30px the sparkles
   render at. Still an additive modifier — `.sparkle.star` keeps every other
   `.sparkle` property and only swaps the clip-path. */
.star{
  clip-path:polygon(50% 88%, 20% 62%, 8% 46%, 4% 32%, 8% 18%, 18% 9%,
                     32% 7%, 43% 12%, 50% 22%, 57% 12%, 68% 7%, 82% 9%,
                     92% 18%, 96% 32%, 92% 46%, 80% 62%);
}
/* Colour variants — "very less... i want the reveal like a celebration".
   All-gold read as sparse even at 20 instances. Rather than invent new
   colours, these are the scene's OWN already-measured palette: crimson is
   #c93a2a (the couple's own names, .s1-bride/.s1-groom), green is #1c421b
   (the body text colour, .s1-sub/.s1-tprompt/etc). Mixing three colours
   already present in this scene reads as genuine confetti rather than a
   single hue repeated, without introducing anything not already in the
   design. */
.spark-red  {background:rgb(201,58,42);  filter:drop-shadow(0 0 4px rgba(201,58,42,.85))}
.spark-green{background:rgb(28,66,27);   filter:drop-shadow(0 0 4px rgba(28,66,27,.85))}
/* --gold explicitly, not the scene's own --reveal-glow-rgb — for mixing a
   second colour INTO a scene whose base colour is something else (scene3's
   rose-crimson), the way scene1 mixed red/green into its own gold base. */
.spark-gold {background:rgb(185,143,87); filter:drop-shadow(0 0 4px rgba(185,143,87,.85))}
/* Compound selector overrides the shared `.reveal{opacity:0;transform:
   translateY(18px)}` base — a sparkle starts from scale(0), not translated
   down, and `transition:none` hands full control to the animation below,
   so a lingering opacity/transform TRANSITION on the same properties the
   ANIMATION also drives can't fight it even briefly. */
.sparkle.reveal{opacity:0; transform:scale(0); transition:none}
.sparkle.reveal.is-in{
  animation-name:sparkle-twinkle;
  animation-duration:1s;
  animation-timing-function:ease-out;
  animation-fill-mode:both;
}
/* Peak scale raised 1.25 -> 1.55 and the settle floor 0.3 -> 0.45 — a
   noticeably punchier pop, applied uniformly to every sparkle (existing and
   new) via this one shared keyframe rather than editing each instance's own
   size. "Very less" was the reported problem; this is the fast, global lever
   for "bigger," with the per-instance clamp() sizes (below) as the second,
   additive lever. */
@keyframes sparkle-twinkle{
  0%   {opacity:0;  transform:scale(0)    rotate(0deg)}
  45%  {opacity:1;  transform:scale(1.55) rotate(24deg)}
  65%  {opacity:.9; transform:scale(1.05) rotate(16deg)}
  100% {opacity:0;  transform:scale(.45)  rotate(28deg)}
}

/* Position (% of the 1000x1500 canvas, matching the .s1-name and
   .deco--s1-bird- rules above) x size x stagger delay (varied so all seven
   do not pop in unison — an organic shimmer, not a synchronised blink).

   Width is clamp(px, cqw, px), not plain cqw — measured live on a phone-width
   card (331px): sparkle--1 peaked at 9.85px, 2.97% of the card, easy to miss
   at a glance on a real screen even though it renders exactly as designed
   (confirmed: fires, correct shape, correct settle state). The glow doesn't
   have this problem — its text-shadow radii are already fixed px, so they
   read RELATIVELY LARGER against mobile's smaller name text, not smaller —
   but a size expressed purely in cqw shrinks with the card and has no floor.
   The clamp floor guarantees a real minimum on a phone; the ceiling keeps
   desktop's card from growing sparkles past what still reads as delicate
   rather than gaudy. Roughly doubled throughout, matching how far the glow
   and the wash-vs-per-slide-backdrop rounds each needed to move before they
   read at real scale rather than only in a zoomed screenshot. */
.sparkle--1{left:33%; top:15.5%; width:clamp(22px, 5.6cqw, 45px); animation-delay:0ms}    /* Riddhi, upper-left  */
.sparkle--2{left:67%; top:15.5%; width:clamp(20px, 4.5cqw, 36px); animation-delay:40ms}  /* Riddhi, upper-right */
.sparkle--3{left:50%; top:22.5%; width:clamp(17px, 3.6cqw, 31px); animation-delay:80ms}  /* weds                */
/* top:44.5% first measured here was wrong — a bad manual conversion of
   Piyush's bbox centre (510/1500=34%, not 44.5%), caught only by actually
   looking at the render: the sparkles landed by the date line, nowhere near
   the name. 31.3% mirrors how the Riddhi pair sits 1.4 points below ITS own
   name's top:14.1% (-> 15.5%), applied the same way to Piyush's top:29.9%. */
.sparkle--4{left:32%; top:31.3%; width:clamp(25px, 6.2cqw, 48px); animation-delay:120ms}   /* Piyush, upper-left  */
.sparkle--5{left:68%; top:31.3%; width:clamp(21px, 5.0cqw, 39px); animation-delay:160ms}  /* Piyush, upper-right */
.sparkle--6{left:9%;  top:29%;   width:clamp(20px, 4.8cqw, 38px); animation-delay:200ms}  /* left hummingbird    */
.sparkle--7{left:91%; top:29%;   width:clamp(22px, 5.3cqw, 42px); animation-delay:240ms}  /* right hummingbird   */

/* A second, closer pair per name — see index.html for why. Below-left/right
   rather than repeating upper-left/right, so the cluster reads as scattered
   around the name rather than four sparkles on one shared edge. Riddhi's own
   box: top:14.1%-20.4% (bottom ~20%); Piyush: top:29.9%-38.0% (bottom ~38%). */
.sparkle--8 {left:38%; top:19.5%; width:clamp(15px, 3.1cqw, 27px); animation-delay:280ms}  /* Riddhi,  lower-left  */
.sparkle--9 {left:62%; top:19.5%; width:clamp(17px, 3.4cqw, 28px); animation-delay:320ms}  /* Riddhi,  lower-right */
.sparkle--10{left:37%; top:36.5%; width:clamp(17px, 3.4cqw, 28px); animation-delay:360ms}  /* Piyush,  lower-left  */
.sparkle--11{left:63%; top:36.5%; width:clamp(15px, 3.1cqw, 27px); animation-delay:400ms}  /* Piyush,  lower-right */

/* Full-card shower: sparkle--12 through --20 (nine, not the fourteen first
   tried), spread across the WHOLE 1000x1500 canvas rather than clustered
   near the names/birds (--1 to --11 above). Positions loosely follow the
   scene's own content bands: prompt (top), "are getting married"/date/
   scratch prompt (middle), the landscape below the timer (lower half) —
   never on top of the countdown numbers/labels themselves, which still need
   to read clearly once scratched open.

   Two things measured here, not assumed:
   1. All 14 originally, delays 550-1450ms: p95 33.3ms, 9/159 frames over
      20ms during the cascade. Real, not catastrophic (median still 60fps).
   2. Tried spreading delays wider (550-2800ms) to lower peak concurrency —
      measured WORSE (15/159 over 20ms), not better: it stretched the
      actively-animating window to cover almost the whole measured period
      instead of concentrating it early with idle time after, so MORE frames
      landed during "something is animating" than before. Reverted.

   Landed on keeping the tighter, better-measured delay range and trimming
   count instead (14 -> 9, total 20 rather than 25) for a real margin: */
.sparkle--12{left:15%; top:7%;   width:clamp(14px, 2.8cqw, 24px); animation-delay:440ms}
.sparkle--13{left:85%; top:7%;   width:clamp(15px, 3.1cqw, 27px); animation-delay:480ms}
.sparkle--14{left:20%; top:41%;  width:clamp(17px, 3.4cqw, 28px); animation-delay:520ms}
.sparkle--15{left:80%; top:41%;  width:clamp(15px, 3.1cqw, 27px); animation-delay:560ms}
.sparkle--16{left:10%; top:55%;  width:clamp(14px, 2.8cqw, 24px); animation-delay:600ms}
.sparkle--17{left:90%; top:55%;  width:clamp(17px, 3.4cqw, 28px); animation-delay:640ms}
.sparkle--18{left:14%; top:71%;  width:clamp(18px, 3.6cqw, 31px); animation-delay:680ms}
.sparkle--19{left:86%; top:71%;  width:clamp(17px, 3.4cqw, 28px); animation-delay:720ms}
.sparkle--20{left:50%; top:88%;  width:clamp(17px, 3.4cqw, 28px); animation-delay:760ms}

/* Round two: sparkle--21 through --36, filling the sky above the
   names and the busier middle/lower bands more densely. Delays
   continue the SAME ~85-100ms step from where --20 left off (1350ms),
   not a wider spread — spreading wider was measured WORSE earlier (see
   the comment above --12), so this keeps the proven cadence rather than
   repeating that mistake at a larger scale. */
.sparkle--21{left:22%; top:9%;  width:clamp(14px, 3.4cqw, 27px); animation-delay:800ms}  /* upper sky, left */
.sparkle--22{left:78%; top:9%;  width:clamp(15px, 3.6cqw, 28px); animation-delay:840ms}  /* upper sky, right */
.sparkle--23{left:50%; top:12%;  width:clamp(12px, 2.8cqw, 22px); animation-delay:880ms}  /* upper sky, centre */
.sparkle--24{left:62%; top:24%;  width:clamp(13px, 3.0cqw, 24px); animation-delay:920ms}  /* between Riddhi and weds */
.sparkle--25{left:38%; top:27%;  width:clamp(12px, 2.8cqw, 22px); animation-delay:960ms}  /* between weds and Piyush */
.sparkle--26{left:24%; top:47%;  width:clamp(16px, 3.8cqw, 30px); animation-delay:1000ms}  /* "are getting married", left */
.sparkle--27{left:76%; top:47%;  width:clamp(15px, 3.6cqw, 28px); animation-delay:1040ms}  /* "are getting married", right */
.sparkle--28{left:16%; top:52%;  width:clamp(14px, 3.2cqw, 25px); animation-delay:1080ms}  /* date line, left */
.sparkle--29{left:84%; top:52%;  width:clamp(14px, 3.2cqw, 25px); animation-delay:1120ms}  /* date line, right */
.sparkle--30{left:50%; top:58%;  width:clamp(13px, 3.0cqw, 24px); animation-delay:1160ms}  /* scratch prompt, centre */
.sparkle--31{left:30%; top:63%;  width:clamp(16px, 3.8cqw, 30px); animation-delay:1200ms}  /* above scratch timer, left */
.sparkle--32{left:70%; top:63%;  width:clamp(15px, 3.6cqw, 28px); animation-delay:1240ms}  /* above scratch timer, right */
.sparkle--33{left:22%; top:79%;  width:clamp(17px, 4.0cqw, 32px); animation-delay:1280ms}  /* landscape, upper-left */
.sparkle--34{left:78%; top:79%;  width:clamp(16px, 3.8cqw, 30px); animation-delay:1320ms}  /* landscape, upper-right */
.sparkle--35{left:40%; top:86%;  width:clamp(15px, 3.6cqw, 28px); animation-delay:1360ms}  /* landscape, lower-centre-left */
.sparkle--36{left:60%; top:86%;  width:clamp(16px, 3.8cqw, 30px); animation-delay:1400ms}  /* landscape, lower-centre-right */
.sparkle--37{left:45%; top:9%; width:clamp(13px, 3.0cqw, 23px); animation-delay:1440ms}  /* upper sky, centre-left gap */
.sparkle--38{left:55%; top:44%; width:clamp(15px, 3.6cqw, 28px); animation-delay:1480ms}  /* centre, between title and subtitle */
.sparkle--39{left:10%; top:19%; width:clamp(14px, 3.2cqw, 25px); animation-delay:1520ms}  /* Riddhi row, far left */
.sparkle--40{left:90%; top:19%; width:clamp(15px, 3.4cqw, 27px); animation-delay:1560ms}  /* Riddhi row, far right */
.sparkle--41{left:46%; top:52%; width:clamp(13px, 3.0cqw, 24px); animation-delay:1600ms}  /* date line, centre */
.sparkle--42{left:54%; top:66%; width:clamp(16px, 3.8cqw, 30px); animation-delay:1640ms}  /* scratch timer, centre-right */
.sparkle--43{left:8%; top:63%; width:clamp(14px, 3.2cqw, 25px); animation-delay:1680ms}  /* mid-left edge */
.sparkle--44{left:92%; top:63%; width:clamp(14px, 3.2cqw, 25px); animation-delay:1720ms}  /* mid-right edge */
.sparkle--45{left:30%; top:83%; width:clamp(17px, 4.0cqw, 32px); animation-delay:1760ms}  /* landscape, lower-left */
.sparkle--46{left:70%; top:83%; width:clamp(16px, 3.8cqw, 30px); animation-delay:1800ms}  /* landscape, lower-right */
.sparkle--47{left:50%; top:94%; width:clamp(16px, 3.8cqw, 30px); animation-delay:1840ms}  /* bottom edge, centre — closing burst */
.sparkle--48{left:18%; top:35%; width:clamp(15px, 3.4cqw, 27px); animation-delay:1880ms}  /* Piyush row, far left */

/* ==========================================================================
   SLIDE VISIBILITY
   ==========================================================================
   Scenes 4-9 were hidden 2026-09-09 (provisional artwork, see RWP-2) and
   unhidden 2026-09-12 per owner request — all nine scenes render now. The
   rule below is kept, unused, for the same purpose: `display:none` takes a
   hidden `.slide` completely out of the box tree, including its own
   `margin-top`, so hiding any slide again (e.g. a future scene still
   pending artwork) leaves no dangling gap or stray margin. Add
   `slide--hidden` back to a `.slide` wrapper in index.html to use it (and
   regenerate the WP template — see gen_template.py). */
.slide--hidden{display:none}

/* Positions: title (top 6-8%), subtitle (14-17%), date (19-21%), time
   (24-25%), venue (29-40%, 3 lines), the two peacocks (72-74%), and the
   remaining sky/landscape bands — matching scene3's own measured PSD
   text/deco positions, not scene1's. Delays 0-1470ms mirrors the SAME
   cadence measured acceptable for scene1 (not the wider spread that
   measured worse there). */
.s3sparkle--1{left:18%; top:6%;  width:clamp(16px, 3.8cqw, 30px); animation-delay:0ms}  /* above title, left */
.s3sparkle--2{left:82%; top:6%;  width:clamp(17px, 4.0cqw, 32px); animation-delay:45ms}  /* above title, right */
.s3sparkle--3{left:50%; top:3%;  width:clamp(13px, 3.0cqw, 24px); animation-delay:90ms}  /* top centre */
.s3sparkle--4{left:28%; top:14%;  width:clamp(15px, 3.4cqw, 27px); animation-delay:135ms}  /* title/subtitle gap, left */
.s3sparkle--5{left:72%; top:14%;  width:clamp(16px, 3.6cqw, 29px); animation-delay:180ms}  /* title/subtitle gap, right */
.s3sparkle--6{left:15%; top:19%;  width:clamp(14px, 3.2cqw, 25px); animation-delay:225ms}  /* near date, left */
.s3sparkle--7{left:85%; top:19%;  width:clamp(15px, 3.4cqw, 27px); animation-delay:270ms}  /* near date, right */
.s3sparkle--8{left:30%; top:24%;  width:clamp(13px, 3.0cqw, 24px); animation-delay:315ms}  /* near time, left */
.s3sparkle--9{left:70%; top:24%;  width:clamp(14px, 3.2cqw, 25px); animation-delay:360ms}  /* near time, right */
.s3sparkle--10{left:20%; top:31%;  width:clamp(16px, 3.8cqw, 30px); animation-delay:405ms}  /* near venue L1, left */
.s3sparkle--11{left:80%; top:31%;  width:clamp(15px, 3.6cqw, 28px); animation-delay:450ms}  /* near venue L1, right */
.s3sparkle--12{left:25%; top:38%;  width:clamp(14px, 3.2cqw, 25px); animation-delay:495ms}  /* near venue L2/3, left */
.s3sparkle--13{left:75%; top:38%;  width:clamp(15px, 3.4cqw, 27px); animation-delay:540ms}  /* near venue L2/3, right */
.s3sparkle--14{left:10%; top:50%;  width:clamp(17px, 4.0cqw, 32px); animation-delay:585ms}  /* mid sky, left */
.s3sparkle--15{left:90%; top:50%;  width:clamp(16px, 3.8cqw, 30px); animation-delay:630ms}  /* mid sky, right */
.s3sparkle--16{left:50%; top:58%;  width:clamp(14px, 3.2cqw, 25px); animation-delay:675ms}  /* mid sky, centre */
.s3sparkle--17{left:16%; top:66%;  width:clamp(15px, 3.4cqw, 27px); animation-delay:720ms}  /* upper landscape, left */
.s3sparkle--18{left:84%; top:66%;  width:clamp(16px, 3.6cqw, 29px); animation-delay:765ms}  /* upper landscape, right */
.s3sparkle--19{left:4%; top:72%;  width:clamp(18px, 4.2cqw, 34px); animation-delay:810ms}  /* left peacock */
.s3sparkle--20{left:96%; top:72%;  width:clamp(18px, 4.2cqw, 34px); animation-delay:855ms}  /* right peacock */
.s3sparkle--21{left:10%; top:88%;  width:clamp(15px, 3.4cqw, 27px); animation-delay:900ms}  /* lower corner, left */
.s3sparkle--22{left:90%; top:88%;  width:clamp(15px, 3.4cqw, 27px); animation-delay:945ms}  /* lower corner, right */

/* ==========================================================================
   SCENE 2 REVEAL — FIREWORKS, not the sparkle/star/wash mechanism above
   ==========================================================================
   Explicit feedback: "i did not want same revel for every slide... change
   the reveal like fireworks in slide 2". Scene1/scene3 share ONE mechanism
   (glow+wash+sparkle) because they're genuinely the same kind of moment —
   this is deliberately a DIFFERENT mechanism, not a recolour: a radial
   particle burst plus a bright flash, timed as a staggered rolling show (each
   shell fires ~170ms after the last) rather than sparkle's simultaneous
   twinkle-in. Reuses `.reveal`/`.is-in` (the scroll-trigger plumbing in
   script.js is scene-agnostic — see REVEAL WASH above) but its own keyframes,
   its own shape (circles + glow, no clip-path glint/star), its own timing
   curve (fast launch, brief hang, gravity-fall fade — real firework physics,
   not a twinkle).

   Fixed px, not cqw — same reasoning as SCRATCH SPARKLE below: this is a
   MOBILE-first burst radius tuned directly at real card width, not something
   meant to scale with an eventual desktop redesign (BLUEPRINT: mobile is the
   only focus now). 44px burst radius, verified against the actual 325-390px
   mobile card (scratchpad shot_scene2_fireworks.js) — big enough to read as
   an explosion, small enough that six of them don't collide.

   10 particles per shell, evenly spaced 36deg apart, offsets computed once
   (not eyeballed — scratchpad, R=44px) and shared by every `.firework`
   instance via nth-child, so adding a 7th shell costs one position+colour
   rule, not ten more particle rules. */
.firework{position:absolute; width:0; height:0; pointer-events:none}

/* The initial flash — a quick bright disc at the burst centre, gone before
   the particles finish travelling. `currentColor` so it tints toward the
   shell's own colour rather than reading as a flat white disc every time. */
.firework::before{
  content:"";
  position:absolute; left:0; top:0;
  width:30px; height:30px; margin:-15px 0 0 -15px;
  border-radius:50%;
  background:radial-gradient(circle, #fff 0%, rgba(255,255,255,.85) 32%, transparent 72%);
  opacity:0; transform:scale(.2);
}
.firework.reveal.is-in::before{
  animation-name:fw-flash; animation-duration:.4s; animation-timing-function:ease-out; animation-fill-mode:both;
}
@keyframes fw-flash{
  0%  {opacity:0;  transform:scale(.2)}
  30% {opacity:.9; transform:scale(1)}
  100%{opacity:0;  transform:scale(1.35)}
}

/* Rebuilt after the first pass rendered as a handful of near-invisible dots
   (verified via a zoomed crop, scratchpad fw_zoom_crop.png — not assumed).
   A round dot has no sense of DIRECTION, which is what actually reads as
   "firework" versus "sparkle" at this size. Rebuilt as a radiating STREAK:
   an elongated capsule with a gradient tail (opaque tip, fading toward the
   burst centre), rotated to point along its own travel angle and animated by
   `rotate + translateY` from a bottom-pivot origin — the standard CSS
   technique for a radial burst — rather than raw dx/dy translation. This is
   also why nth-child now sets an angle, not an offset. */
.fwp{
  position:absolute; left:0; top:0;
  width:3.5px; height:20px;
  margin:-20px -1.75px 0 -1.75px;   /* anchors the CAPSULE'S FAR END at the burst centre... */
  transform-origin:50% 100%;         /* ...and pivots there, so rotate() sweeps it like a clock hand */
  border-radius:2px;
  background:linear-gradient(to top, transparent 0%, var(--fw-color, #f2b705) 55%, #fff 100%);
  box-shadow:0 0 7px 2px var(--fw-color, #f2b705);
  opacity:0;
}
/* 10 particles, 36deg apart — see the section note above. */
.fwp:nth-child(1) {--ang:0deg}
.fwp:nth-child(2) {--ang:36deg}
.fwp:nth-child(3) {--ang:72deg}
.fwp:nth-child(4) {--ang:108deg}
.fwp:nth-child(5) {--ang:144deg}
.fwp:nth-child(6) {--ang:180deg}
.fwp:nth-child(7) {--ang:216deg}
.fwp:nth-child(8) {--ang:252deg}
.fwp:nth-child(9) {--ang:288deg}
.fwp:nth-child(10){--ang:324deg}
.firework.reveal .fwp{opacity:0; transition:none}
.firework.reveal.is-in .fwp{
  animation-name:fw-burst;
  animation-duration:1.05s;
  animation-timing-function:cubic-bezier(.18,.7,.32,1);
  animation-fill-mode:both;
}
/* Real firework physics, not a twinkle: fast launch to peak (0-45%), a brief
   hang at full brightness, then the streak lengthens and fades as it burns
   out (scaleY climbing past 1 at 100%) — what reads as "spark burning out in
   flight" instead of "shrinking dot". translateY is negative because the
   capsule's pivot is its FAR end (see margin above), so moving "up" in its
   own rotated frame is "outward" from the burst centre — screen-down gravity
   was tried and dropped: composed AFTER rotate() it moves in the rotated
   frame, not screen-down, so it read as broken rather than physical. */
@keyframes fw-burst{
  0%   {opacity:1; transform:rotate(var(--ang)) translateY(0)     scaleY(.35)}
  14%  {opacity:1; transform:rotate(var(--ang)) translateY(-19px) scaleY(.75)}
  45%  {opacity:1; transform:rotate(var(--ang)) translateY(-44px) scaleY(1)}
  100% {opacity:0; transform:rotate(var(--ang)) translateY(-54px) scaleY(1.3)}
}

/* Six shells, positioned around scene2's actual content (Ganesha crest,
   invocation, the couple's names, the schedule) rather than scattered
   arbitrarily — same "reveal matches what the scene actually contains"
   principle as scene1/3. Colours are the scene's OWN palette (crimson
   #c93a2a and gold #b98f57, already used by .s2-groom/.s2-bride and the
   mandala linework) plus one warm white shell, not new hues invented for
   this. Delays roll like a real fireworks show — staggered, not
   simultaneous — ~170ms apart so 2-3 are always mid-burst together. */
.fw--1{left:14%; top:4%;  --fw-color:#f2b705; animation-delay:0ms}     /* above invocation, left of the Ganesha crest */
.fw--2{left:86%; top:4%;  --fw-color:#c93a2a; animation-delay:170ms}   /* above invocation, right */
.fw--3{left:6%;  top:26%; --fw-color:#fdf6e3; animation-delay:360ms}   /* left, level with the hummingbirds */
.fw--4{left:94%; top:44%; --fw-color:#c93a2a; animation-delay:530ms}   /* right, level with the couple's names */
.fw--5{left:8%;  top:62%; --fw-color:#f2b705; animation-delay:710ms}   /* left, level with the invitation body */
.fw--6{left:92%; top:80%; --fw-color:#fdf6e3; animation-delay:880ms}   /* right, level with the schedule */

/* ==========================================================================
   SCRATCH SPARKLE — PROTOTYPE, scene1 only
   ==========================================================================
   Gold dust flicks off at each scratch stroke (see initScratch() in
   script.js), and a small burst fires when the countdown is fully revealed
   — the same 4-point sparkle shape used elsewhere on this scene (see REVEAL
   SPARKLE above), reused rather than a second shape invented for this one
   interaction. Fixed px, not cqw: this is a dynamic, JS-spawned effect tied
   to a touch point, not artwork-locked geometry, and fixed sizing is what
   the mobile-sizing lesson from the reveal sparkles already established —
   no reason to reintroduce a size that shrinks away on a phone. */
.scratch-spark{
  position:absolute;
  width:13px; height:13px;
  transform:translate(-50%,-50%) scale(0);
  clip-path:polygon(50% 0%, 60% 40%, 100% 50%, 60% 60%, 50% 100%, 40% 60%, 0% 50%, 40% 40%);
  background:rgb(var(--reveal-glow-rgb, 255,255,255));
  filter:drop-shadow(0 0 4px rgba(var(--reveal-glow-rgb, 255,255,255),.9));
  pointer-events:none;
  animation:scratch-spark-pop .6s ease-out forwards;
}
@keyframes scratch-spark-pop{
  0%   {opacity:0; transform:translate(-50%,-50%) scale(0)   rotate(0deg)}
  30%  {opacity:1; transform:translate(-50%,-50%) scale(1.3) rotate(15deg)}
  100% {opacity:0; transform:translate(-50%,-50%) translateY(-14px) scale(.4) rotate(30deg)}
}
/* 2026-09-19 ("the first slide background to continue for slide 2 too"):
   scene2's base is now scene-01.webp — slide 1's own sky+meadow art — in
   place of scene-02.webp's mandala. The veil's old job (muting the mandala
   behind all 15 text blocks) is moot up top, where the art is plain sky, so
   it's narrowed to ONLY the lower band where the bride's name + parents sit
   over slide 1's meadow/foliage (starts ~55% down; measured by screenshot —
   they were unreadable on it). Same paper tone + feathered mask as before,
   just a different box. */
.scene2__veil{top:51.5%; bottom:21.5%; left:2%; right:2%; opacity:.92;
  /* 2026-09-19 ("background color of riddhi chhajed and the names will be
     match with above background color"): sky colour sampled straight from
     scene-01.webp (rgb 212,231,238 — identical at y=20%..53%), not --paper,
     so the wash reads as more of the same sky above it instead of a cream
     patch. */
  background:#d4e7ee;
  -webkit-mask-image:radial-gradient(ellipse 66% 60% at 50% 50%, #000 78%, transparent 100%);
          mask-image:radial-gradient(ellipse 66% 60% at 50% 50%, #000 78%, transparent 100%)}
@media (max-width:480px){.scene2__veil{top:51.5%; bottom:21.5%}}

/* 2026-09-20: slide 2 now opens with slide 1's foliage mirrored across the
   boundary (scene-02-bg.webp), which puts the dark-green Ganesha line art on
   top of dark-green leaves. A soft pale-sky halo (the sky's own colour, lifted)
   lifts him off the foliage without recolouring or moving the artwork. */
#scene2 .scene__over{filter:drop-shadow(0 0 4px #eaf4f7) drop-shadow(0 0 7px #eaf4f7) drop-shadow(0 0 2px #fff)}

/* 2026-09-20 ("the sides in slide 2 are cut, the birds and flower designs
   not visible like slide 1"): .scene is `width:max(100%, 66.667vh)` (see its
   rule), so on a phone it's wider than the screen and ~83px per side is
   cropped by .card. Slide 1's birds/vines were placed inward and mostly
   survive that; slide 2's were placed at the PSD's edges (bird-l at
   -85..-2px, bird-r at 373..457px on a 375px screen — entirely off-screen,
   measured). --crop is exactly the per-side overflow (0 on wide screens, so
   desktop is untouched); left-side sprites move right by it and right-side
   sprites move left by it, landing their outer edge on the visible edge. */
#scene2{--crop:max(0px, calc((66.667vh - 100vw) / 2))}
.deco--s2-floral-tl{left:calc(-5.4% + var(--crop))}
.deco--s2-floral-ml{left:calc(-3.4% + var(--crop))}
.deco--s2-bird-l   {left:calc(-0.4% + var(--crop))}
.deco--s2-floral-tr{left:calc(70.2% - var(--crop))}
.deco--s2-floral-mr{left:calc(80.8% - var(--crop))}
.deco--s2-bird-r   {left:calc(84.3% - var(--crop))}
