/** Schema-v1 routing evidence values shared by emitters and offline readers. */
export declare const PROXY_ACCOUNT_ROUTING_STRATEGIES: readonly ["round-robin", "fill-first"];
export declare const PROXY_ACCOUNT_ROUTING_MODES: readonly ["quota", "primary", "round_robin", "single_account"];
export declare const PROXY_ACCOUNT_ROUTING_REASONS: readonly ["single_account", "round_robin", "configured_primary", "insertion_order", "availability", "cooldown_recovery", "quota_evidence", "quota_probe", "session_headroom", "scoped_headroom", "session_reset", "weekly_reset", "weekly_utilization", "scoped_utilization", "headroom", "session_affinity", "preferred_primary", "spill_inflight", "routing_policy_error"];
export declare const PROXY_ACCOUNT_TYPES: readonly ["oauth", "api_key"];
export declare const ACCOUNT_COOLING_REASONS: readonly ["weekly", "session", "unified", "transient", "auth"];
/**
 * Longest a cooldown may last for each reason, measured from when it was set.
 *
 * A reason names a specific provider window, so it also bounds the wait: a
 * "session" cooldown describes a 5-hour window and can never legitimately run
 * for days. Without a per-reason ceiling a single bogus reset timestamp parks an
 * account for as long as the global 8-day clamp allows — observed in the wild as
 * a 206-hour "session" cooldown. Values carry slack so a genuine window that
 * resets slightly late is not cut short.
 */
export declare const MAX_COOLDOWN_MS_BY_REASON: Record<string, number>;