@charset "UTF-8";
/**
 * Shared BuddyBoss theme-token map.
 *
 * The BuddyBoss theme exposes its design tokens as runtime CSS custom
 * properties on :root / body. We never introduce new tokens — we alias BB's
 * with a safe fallback so a WCV surface still renders acceptably if a token
 * name differs between BB theme versions. Consumed by the theme re-skin
 * stylesheets (store #2679, dashboard #2683, directory #2684) via `@use`.
 *
 * Each value is a `var(--bb-*, fallback)` string held in a Sass variable, so
 * referencing the variable emits the custom property with its fallback intact.
 *
 * Source: includes/buddyboss/assets/src/css/_theme-tokens.scss (partial, not built)
 *
 * @since 2.0.9
 */
/**
 * BuddyBoss theme adapter — vendor Dashboard re-skin (#2683).
 *
 * Deliberately minimal — and for the same reason the store re-skin (#2679) is.
 * Under the BuddyBoss theme the vendor dashboard is already almost entirely
 * native, because the BuddyBoss theme ships its own WC Vendors compatibility
 * stylesheet (`wcvendors.min.css`) that re-skins WCV buttons, form controls
 * and links onto BB's button/colour tokens. A live A/B across every dashboard
 * surface (overview, products, orders, reports, ratings, commission,
 * statements, coupons, engage, settings) confirmed that nav, tables,
 * typography, spacing, form-control focus and the standard buttons all adopt
 * BB tokens without us.
 *
 * What the sweep left as genuine gaps are a few accent chips/labels the compat
 * sheet doesn't reach, still pinned to WCV's hard-coded blue (#0f62fe) — which
 * is visibly off from BB's primary on *every* BB site, default or customised.
 * This stylesheet re-points just those at BB's primary token.
 *
 * Deliberately NOT re-skinned:
 *   - Elements hard-coded to #385DFF (`.wcv-button` solid, `.text-blue`): they
 *     already match BB's default primary, so they only diverge on a customised
 *     primary, and `.wcv-button`'s cancel/danger/secondary variants make a safe
 *     override fragile. Left for a follow-up if custom-primary parity is wanted.
 *   - Semantic colours: sales-snapshot per-metric icons, error/danger reds,
 *     and WooCommerce notice accents. These carry meaning, not chrome.
 *
 * Scoped under body.wcv-bb-theme .wcvendors-pro-dashboard-wrapper (the body
 * class is added by the theme adapter only when the BuddyBoss theme is active
 * and the Theme touchpoint is enabled), so non-BB sites are untouched. No WCV
 * markup changes; no new design tokens.
 *
 * Source: includes/buddyboss/assets/src/css/theme-dashboard.scss
 * Built to: includes/buddyboss/assets/css/theme-dashboard.css (gulp compileStyles)
 *
 * @since 2.0.9
 */
body.wcv-bb-theme .wcvendors-pro-dashboard-wrapper {
  /* Store-setup wizard step marker. */
  /* Orders quick-link labels/counts — the active-state accent. The source
   * active rule (.quick-link-btn.black.active a .wcv-ql-*) out-specifies a
   * plain class, so match its shape to win without !important. */
  /* Selected item in a dashboard filter list. */
}
body.wcv-bb-theme .wcvendors-pro-dashboard-wrapper .wcv-store-setup-step-icon {
  background-color: var(--bb-primary-color, #4f46e5);
}
body.wcv-bb-theme .wcvendors-pro-dashboard-wrapper .quick-link-btn.active a .wcv-ql-label,
body.wcv-bb-theme .wcvendors-pro-dashboard-wrapper .quick-link-btn.active a .wcv-ql-count {
  color: var(--bb-primary-color, #4f46e5);
}
body.wcv-bb-theme .wcvendors-pro-dashboard-wrapper .wcv-select-item.selected {
  color: var(--bb-primary-color, #4f46e5);
}
/*# sourceMappingURL=theme-dashboard.css.map */