/**
 * SQLITE_BUSY retry helpers.
 *
 * Even with `PRAGMA busy_timeout=30000` configured on the leader connection,
 * rare write/write collisions can still surface (e.g. during WAL checkpoints
 * or when the busy_timeout is exhausted). Wrapping writes with
 * `withSqliteBusyRetry` absorbs those transient failures with a bounded
 * exponential backoff so callers never see `SQLITE_BUSY` / `SQLITE_LOCKED`.
 *
 * Reads don't need this helper: under WAL they never block.
 */
export declare const SQLITE_BUSY_RETRY_DELAYS_MS: readonly [10, 25, 50, 100, 250];
export declare function isSqliteBusyError(error: unknown): boolean;
export declare function withSqliteBusyRetry<T>(fn: () => T | Promise<T>, delaysMs?: readonly number[]): Promise<T>;
//# sourceMappingURL=retry.d.ts.map