/**
 * i9 Core — Custom CSS.
 *
 * Your own overrides live here. This file is loaded AFTER every other i9 Core
 * stylesheet (base and all components), so at equal specificity your rule wins.
 * It ships empty and is yours to edit — the plugin never generates into it.
 *
 * ── How to override a component ──────────────────────────────────────────────
 *
 * Component styles are scoped under `.i9-scope` (specificity 0,2,0), so a bare
 * `.i9-btn { … }` (0,1,0) will NOT beat them. Match the scope by prefixing your
 * selector with `.i9-scope`, and it will:
 *
 *     .i9-scope .i9-btn--primary   { background: #0057b8; border-color: #0057b8; }
 *     .i9-scope .i9-card           { border-width: 4px; }
 *     .i9-scope.i9-trust--dark     { background: #101418; }
 *     .i9-scope .i9-centres__tab.is-active { background: #222; }
 *
 * The component class names to target are visible in your browser's inspector,
 * and in the plugin's own stylesheets under assets/css/.
 *
 * ── Prefer the settings screen first ─────────────────────────────────────────
 *
 * Colours, fonts, spacing, borders and button styling are all driven by design
 * tokens from i9 Core → Design Settings — change them there and every component
 * updates at once, no CSS required. Reach for this file only for rules the
 * settings do not cover.
 *
 * ── Notes ────────────────────────────────────────────────────────────────────
 *
 * • You can also override a token here, e.g. `:root { --i9-color-primary: #06c; }`.
 * • On a live site with a page cache (WP Rocket, LiteSpeed, …), clear it after
 *   editing so the change reaches visitors.
 *
 * @package I9\Core
 */

/* Add your custom CSS below this line. */