/* ── explore-chrome.css ─────────────────────────────────────────────────────
THE single shared-chrome bundle for every explore-family page:
asset · theme · gics · country · feed
Load this ONE instead of copy-pasting the 6 imports below into each
page's . That copy-paste is exactly what drifted and kept breaking:
· site-nav v11 (theme/gics/country) vs v14 (asset/feed)
· feed.css card6 (asset/theme/gics/country) vs card13 (feed)
· rail.css v4 (theme/gics/country) vs v6 (feed) — asset had NONE at all
One file → one set of versions → every page renders identically. Impossible
to "forget a link" on a new page again.
Order matters (cascade): fonts → design system → nav → cards → rail → chrome.
Page-specific sheets (asset.css · megatrend-valuechain.css · ex-immersive.css)
still load AFTER this bundle in each page so they can override.
BUSTING A CHILD after you edit it: bump its ?v HERE, then bump this bundle's
own ?v on the in every page. scripts/check-chrome.mjs asserts every
explore-family page loads this bundle at the same version (fails the build if
one drifts). */
@import url("/css/mdx-fonts.css?v=2");
@import url("/portfolio/css/taste.css?v=2");
@import url("/css/site-nav.css?v=14");
@import url("/feed/css/feed.css?v=card20");
@import url("/css/rail.css?v=8");
@import url("/explore/css/explore.css?v=13");