/**
 * Business-audience accent layer (docs/audience-split-plan.md).
 *
 * Loaded by inc/enqueue.php only when safi_is_business() is true, after every other
 * stylesheet, so anything declared here would win. It is deliberately EMPTY, and that is
 * now a decision rather than a placeholder.
 *
 * Phase 3 settled the question this file was originally holding open: there is ONE shared
 * palette for both audiences. The visitor and business experiences read the exact same
 * :root tokens from variables.css — the brand chrome is identical on both, and only the
 * navigation, wordmark line and content differ. Do not fill this file with a divergent
 * business colour system; two accent palettes on one install would double the contrast
 * surface to audit for no brand benefit.
 *
 * The hook stays because it costs nothing and keeps the option open: if a future phase
 * ever does want a business-side accent, the correct move is still to re-point tokens
 * under the audience body class rather than restyling components one by one —
 *
 *   body.audience-business { --safi-teal: <accent>; }
 *
 * — and any such override must be re-measured against docs/accessibility-audit.md, since
 * several tokens (--safi-teal, --safi-green, --safi-text-muted-6/7,
 * --safi-focus-ring-color) carry specific computed ratios and inline justifications.
 */

/* The audience body class is emitted by inc/audience.php's body_class filter and is
   available on every page. Intentionally no rules — see above. */