/**
 * Which events survive the bridge's rate cap.
 *
 * The cap exists because a busy app can emit faster than the bridge can absorb. But dropping
 * indiscriminately is the wrong sampling policy: event volume is inversely correlated with event
 * value. A React commit storm emits thousands of `render.commit`/`dom.*` per second, while the events
 * an assertion actually turns on — a network call, an uncaught error, a route change — are rare.
 * First-come-first-dropped therefore spends the whole budget on churn and loses exactly the signal
 * the agent asked about.
 *
 * So over the cap the high-volume/low-value kinds drop first and these keep a reserve. The
 * reserve is bounded (see RATE_CAP_HIGH_VALUE_RESERVE_RATIO) — a flood of errors is still a flood,
 * and going unbounded here would just move the overload rather than shed it.
 */
export declare const HIGH_VALUE_EVENT_TYPES: ReadonlySet<string>;
/**
 * The over-cap reserve for high-value events, as a multiple of the cap. Total admitted per second is
 * therefore bounded at `cap * (1 + ratio)` — still a hard bound, just one that spends its last slots
 * on the events worth keeping.
 */
export declare const RATE_CAP_HIGH_VALUE_RESERVE_RATIO = 1;
export declare function isHighValueEvent(type: string): boolean;