/* =========================================================================
   INTRO-1 PIN-RELEASE — un-pin the page AFTER Matey has risen to full.  INTRO-1 ONLY.

   Matey's scroll is UNCHANGED: the base fixed .hero + the scrubbed card-rise + the
   title-cover + the rise-guard all stay exactly as-is over the #scrollTrack. The only
   addition is that, once the rise completes (scroll = trackHeight − viewport, i.e. the
   #scrollTrack bottom reaching the viewport bottom), js/pellmell-intro-release.js flips
   the hero from position:fixed to position:absolute, PARKED at that same scroll position —
   so it un-pins and scrolls away, and EF (below, in normal flow) follows with no overlap.

   The switch is seamless: at the release point the fixed hero already occupies doc
   riseEnd…riseEnd+100vh, and absolute top:riseEnd height:100vh is the same box → no jump.
   Base file untouched; this overrides via a JS-added class. v2/v3 never load this file.
   ========================================================================= */

/* Released state (class added by the release JS at scroll = rise-end). Compound selector
   .hero.hero--released beats the base .hero { position:fixed } on specificity + order. */
.hero.hero--released {
  position: absolute;
  inset: auto;                  /* cancel the base inset:0 so top can park it */
  left: 0;
  width: 100%;
  height: 100vh;
  /* top: <rise-end scroll px> is set inline by pellmell-intro-release.js */
}

/* Un-pinned document: drop the EF over-scroll layer (z-200) + occlusion fill — with the
   hero releasing there's nothing to scroll over or hide. Scoped to .js-unpinned so the
   reduced-motion / no-JS path keeps the base fixed-hero + z-200 fallback untouched.
   EF now flows normally below the released hero.

   .js-unpinned IS ADDED AT RELEASE, NOT AT LOAD (js v=2, 2026-08-28). It used to go on the
   moment the release JS ran, which meant EF could be transparent while the hero was still
   position:fixed — the two states superimpose and you see both containers at once. It is
   now added in release() and removed in refix(), so this rule is only ever live while the
   hero is genuinely absolute and out of the way. Pre-release, EF keeps the base z-200 +
   opaque #ffffff, which is the correct occlusion for a fixed hero. See the block comment
   in js/pellmell-intro-release.js. */
.js-unpinned .ef-project-screen {
  z-index: auto;
  background: transparent;
}