/*
 * Prism's theme, loaded into a cascade layer.
 *
 * ⚠ WHY THIS FILE EXISTS — the roadmap's premise turned out to be wrong.
 *
 * The batch assumed prism-tomorrow's `pre[class*="language-"]` rules could
 * never match, because both this theme and the licence server's embed put the
 * language class on the <code>, never the <pre>. That is true of the HTML as
 * served — but Prism.highlightElement() COPIES the language class onto the
 * parent <pre> at runtime. Verified 2026-10-05: a <pre class="bc-recipe-code">
 * becomes <pre class="bc-recipe-code language-php"> the moment it is
 * highlighted, which hands those rules the match they were not supposed to get
 * — a #2d2d2d background and a .5em margin over whatever the host block set.
 *
 * Specificity alone is not a reliable defence. The theme's own blocks happen
 * to win (.bc-page .bc-recipe-code is 0,2,0 against Prism's 0,1,1), and so
 * does the embed while it carries the --full modifier (0,3,0). A code block
 * styled by a single class would lose.
 *
 * An unlayered rule beats a layered one whatever the specificity, so putting
 * the vendored theme in a layer restores exactly the arrangement the batch
 * intended: Prism's token colours apply, because nothing else targets
 * .token.*, while every background, padding and margin the site sets wins by
 * construction rather than by luck.
 *
 * ⚠ The vendored file is imported, never edited, so an upgrade is a
 * straight file replacement.
 */
@layer prism;
@import url( "../vendor/prism/prism-tomorrow.min.css" ) layer( prism );