/* The instance brand slot (POP-6845). Deliberately empty in the engine.
 *
 * One immutable engine image serves every fleet, so the engine ships no brand
 * of its own beyond the bundled default: the SPA's own stylesheet reads brand
 * role tokens only (tests/test_packaging.py::test_the_browser_hard_codes_no_colour
 * pins that), and the bundled @admindio/makepop-brand-web/theme.css defines
 * them. This file is the seam an adopting instance writes through.
 *
 * THE INSTANCE CONTRACT
 *
 * An adopting image overwrites the three files in this directory and does
 * nothing else - the documented pattern is a Dockerfile of FROM plus
 * `COPY brand ./web/dist/brand`. Overwrite this file with your own brand's
 * theme CSS and redefine the SAME brand role tokens at the SAME selectors the
 * bundled theme.css uses, or a mode you leave out falls back to the bundled
 * default rather than to your brand.
 *
 * The bundled @admindio/makepop-brand-web/theme.css defines its tokens at
 * exactly these four selectors, so an instance file has to cover all four:
 *
 *   :root
 *   :root, [data-theme="light"]
 *   [data-theme="dark"]
 *   @media (prefers-color-scheme: dark) { :root:not([data-theme="light"]) { } }
 *
 * The last two are what make dark mode work: the explicit choice the fleet
 * theme toggle stamps on <html>, and the OS preference for a visitor who has
 * made no choice. Redefining only :root leaves a dark visitor on the bundled
 * dark palette, which is the wrong brand rather than a missing one.
 *
 * LOAD ORDER
 *
 * index.html links this file at the end of <body>, after the module script,
 * so it lands after the bundle CSS Vite injects into <head>. Later source
 * order wins at equal specificity, which is why an instance file needs no
 * !important and no extra specificity: use the same selectors and it wins.
 *
 * Asset URLs inside an instance copy of this file resolve relative to this
 * file, so fonts and images shipped beside it are referenced by bare
 * filename.
 */