import type { MessageRecord } from "../types.js";
/**
 * Reset internal counters. Exported for tests; production callers never
 * touch. Lets a test deterministically trigger or skip the probe sample.
 */
export declare function _resetProbeCounterForTests(): void;
/** Exported for tests — how many divergences have been logged this process. */
export declare function _probeDivergenceCountForTests(): number;
/**
 * Called from `handleGetMessages` AFTER the caller's result is computed.
 * Compares the MCP-path result set to a parallel raw-SQL query that
 * intentionally IGNORES session-partition state, so a v2.2.1-style
 * "session marked rows read, subsequent pending poll drops them"
 * regression surfaces as a count mismatch.
 *
 * Only `status === "pending"` samples — that's where the drops-pending
 * class of bug manifests. Other filters are out of scope for now.
 */
export declare function sampleGetMessagesConsistency(args: {
    agentName: string;
    status: string;
    limit: number;
    peek: boolean;
    mcpResult: MessageRecord[];
    /**
     * v2.7.0: the same `since` bound the MCP path applied. Pre-v2.7.0 the
     * filter ran in JS after the SQL fetch, so the probe's SUPERSET
     * query naturally matched. The external-review-flagged P1 fix moved the
     * filter into SQL; the probe must mirror it or every since-narrower-
     * than-all call emits false-positive "divergence" warnings.
     */
    sinceIso: string | null;
}): void;
//# sourceMappingURL=consistency-probe.d.ts.map