/* ═══════════════════════════════════════════════════════════════════════════
   OVERRIDES — rules that belong in css/index.css and cannot live there yet.

   css/style.min.css is a GENERATED bundle (grid + index + hero-anim + btn-fx).
   The script that builds it used to be in no repo, so a fix to a bundled rule
   edited a source the served file was never rebuilt from: the page kept the old
   behaviour and nothing errored. This file loads AFTER the bundle on every
   route — biiq_Theme::DisplayPage prepends it to `pagecss` — so it was the only
   place a bundled rule could actually be corrected.

   ✅ THAT PREMISE IS GONE — landing/build.js exists as of 2026-08-03.
   `cd landing && npm install && npm run build` rebuilds the bundle from these
   sources, so the rule below can finally go where it belongs.

   ⚠️ THIS FILE IS A HOLDING PEN, NOT AN ARCHITECTURE, AND IT IS NOW RETIRABLE.
   The one live rule belongs in css/grid.css. Moving it is the whole job; then
   delete this file AND the prepend block in biiq_Theme::DisplayPage. Do not
   delete either half alone — build.js refuses to build if overrides.css is
   neither prepended by biiq_Theme nor the LAST entry of its CSS manifest,
   because the failure it is guarding against (the nav silently stops sticking
   on every route) produces no error of its own.

   Keep it small. A rule added here to avoid thinking about where it belongs is
   how a codebase acquires a permanent "misc.css".
   ═══════════════════════════════════════════════════════════════════════════ */

/* ─── BELONGS IN grid.css — THE NAV WAS NOT STICKY AT ALL ───
   Reported 2026-08-02: the header scrolled away with the page.

   Cause is pure cascade order inside the hand-rolled Bootstrap subset:

       grid.css:126   .sticky-top { position: sticky; ... }
       grid.css:151   .navbar     { position: relative; ... }

   Same specificity — one class each — so the LATER rule wins and every
   `.navbar.sticky-top` computes `position: relative`. Measured before this fix:
   at scrollY 5000 the nav's top was -5000px, i.e. fully gone.

   Real Bootstrap does not have this problem because `.sticky-top` is a HELPER
   and helpers are emitted after components. This subset put them in the
   opposite order, so the helper it was meant to be lost to the component.

   The fix is specificity, not reordering: `.navbar.sticky-top` is two classes
   and wins wherever it sits, which means it also survives the day someone
   regenerates the subset in a different order.

   NOT z-index: `.site-nav` (index.css) deliberately sets 100 and that is
   working. Only `position` was wrong; changing more than the broken thing is
   how a fix becomes a regression. */
.navbar.sticky-top {
  position: sticky;
}