/**
 * `XY_TOKEN_BINDINGS` — React Flow's own palette, bound to BSuite role tokens.
 *
 * EXTRACTED FROM `SchemaCanvas.tsx` (v1.9.0) SO IT CAN BE IMPORTED WITHOUT
 * IMPORTING THE WHOLE CANVAS.
 *
 * This object had been copy-pasted THREE times across the estate —
 * `SchemaCanvas.tsx` (with `colorMode`), `business-suite-unified/src/lib/
 * xyflowThemeTokens.ts`, and a third, independently-authored copy in
 * `crm7/src/pages/sales/pipeline-flow-inner.tsx` — which is the anti-pattern
 * the estate's DRY doctrine forbids, tracked at
 * https://github.com/GaryOcean428/bsuite/issues/2550. `@bsuite/workflow-canvas`
 * needed a FOURTH; this export is what it consumes instead. The two app-level
 * copies can now be collapsed onto it, which is what closes #2550.
 *
 * Importing it from `SchemaCanvas.tsx` was not an option: that module pulls in
 * dagre and html-to-image, and bundle size is an explicit operator constraint.
 * Hence its own file with no dependencies but React's CSSProperties type.
 */
import type { CSSProperties } from 'react';
/**
 * React Flow ships its own palette as raw hex, split into `-default` values
 * under `.react-flow` and `.react-flow.dark`. Even with `colorMode` set
 * correctly that palette is the library's, not the tenant's: the minimap ground
 * would be the library's own near-white in light and its own near-black in
 * dark, regardless of what the surface
 * behind it actually is.
 *
 * `-props` is the layer the library reserves for the consumer (it is what the
 * component props write to), so overriding it here does not fight the
 * stylesheet's own cascade. Every value is a role token, so both themes and any
 * tenant branding follow automatically and nothing here needs a dark variant.
 */
export declare const XY_TOKEN_BINDINGS: CSSProperties;
//# sourceMappingURL=xyflowTokenBindings.d.ts.map