/**
 * bsx-pub shared design tokens — single source of truth for the
 * --bsx-* color/effect variables used by BOTH bsx-pub.css and
 * bsx-pub-article.css.
 *
 * NOTE: previously used a var(--bsx-bg-1, #fff)-style fallback chain,
 * intended to defer to the theme's own tokens if it ever defined them.
 * That was hijacked by the main bsx-design plugin's own --bsx-bg-1 etc.
 * Removing the indirection (setting values directly) wasn't enough
 * either — bsx-design ALSO defines the same bare names (--bsx-bg, not
 * just --bsx-bg-1) directly on its own :root rule. Since both rules
 * target :root with identical specificity, plain CSS cascade order
 * decides, and bsx-design's rule was simply loading after this one.
 * !important on every declaration forces these to win regardless of
 * load order, without needing to know bsx-design's actual enqueue
 * handle to sequence against it.
 */
:root {
	--bsx-bg:            #ffffff !important;
	--bsx-bg-raised:     #f1f1f1 !important;
	--bsx-bg-deep:       #e0e0e0 !important;
	--bsx-text:          #030204 !important;
	--bsx-text-muted:    #6b6b6b !important;
	--bsx-accent:        #6d0a20 !important;
	--bsx-accent-mid:    #6d0a20 !important;
	--bsx-accent-strong: #8a0e29 !important;
	--bsx-border:        #dddddd !important;
	--bsx-error:         #d9705f !important;
	--bsx-radius-lg:     8px !important;
	--bsx-shadow-md:     0 2px 8px rgba( 0, 0, 0, 0.08 ) !important;
	--bsx-transition:    0.15s ease !important;
}