@capgo/cli/dist/src/shared/two-factor-compliance.d.ts

A CLI to upload to capgo servers

export declare const TWO_FACTOR_COMPLIANCE_NETWORK_MESSAGE = "Cannot reach Capgo to verify 2FA compliance. Check your network connection and try again.";
export declare const TWO_FACTOR_PREFLIGHT_NETWORK_WARNING = "Could not verify 2FA compliance due to a network error. Continuing \u2014 Capgo will still enforce 2FA on this action if required.";
export declare const TWO_FACTOR_PREFLIGHT_MAX_ATTEMPTS = 3;
/**
 * User-facing 2FA compliance connectivity failure. Unlike CliUserError, this
 * remains eligible for PostHog `$exception` capture so operational connectivity
 * issues stay visible while the CLI shows a stable recovery message.
 */
export declare class TwoFactorComplianceNetworkError extends Error {
    constructor(message?: string);
}
/** Retries transient transport failures before the preflight fail-open path runs. */
export declare function callTwoFactorComplianceRpcWithRetry<T>(rpcCall: () => PromiseLike<{
    data: T | null;
    error: {
        message?: string;
    } | null;
}>): Promise<{
    data: T | null;
    error: {
        message?: string;
    } | null;
}>;
/** Warn, capture telemetry, and let the command continue when the preflight probe is unreachable. */
export declare function warnAndContinueTwoFactorPreflightNetworkFailure(options: {
    silent?: boolean;
    telemetryFunctionName: string;
}): Promise<void>;
/** Maps Supabase RPC transport failures to user-facing 2FA compliance errors. */
export declare function throwTwoFactorComplianceRpcError(error: {
    message?: string;
}): void;