:root{
  --tte-r-card:20px; --tte-r-img:16px; --tte-r-input:12px; --tte-r-pill:999px;
  --tte-shadow-sm:0 8px 20px rgba(44,39,51,.08);
  --tte-shadow-md:0 14px 34px rgba(44,39,51,.10);
  --tte-focus:0 0 0 3px rgba(122,79,176,.45);
  --tte-ease:cubic-bezier(.34,1.56,.64,1); --tte-dur:160ms;
}

/*
 * Blocksy's own compiled stylesheet (static/bundle/main.min.css, enqueued as
 * ct-main-styles-css) ships a rule `body,h1,h2,h3,h4,h5,h6{font-family:var(--theme-font-family)}`
 * (defaulting to the system font stack via --theme-font-stack-default). It has the
 * same specificity as theme.json's global-styles body rule but loads AFTER it, so it
 * silently wins the cascade and the brand fonts never render even though theme.json
 * names them correctly. These two rules re-assert the theme.json font tokens (no
 * hardcoded font names, just the same CSS custom properties theme.json defines) with
 * !important so the brand fonts actually apply.
 */
body{font-family:var(--wp--preset--font-family--body) !important;}
h1,h2,h3,h4,h5,h6{font-family:var(--wp--preset--font-family--display) !important;}