/**
 * activity-flush — drain the durable report store into the ledger file and
 * republish the ledger as the live snapshot (#1847). The CLI's `activity flush`
 * is a thin wrapper around this so the sequence is testable with an in-memory
 * backend: consume `report/*`, write the file, delete what was consumed, then
 * publish `snapshot/activity.json` — on EVERY run, pending beacons or not, so a
 * failed publish heals on the next run and a release that moved the file
 * ahead of the blob is caught up.
 */
import { ActivityLedger } from './activity-ledger.js';
import { type BlobBackend } from './report-store.js';
export interface FlushResult {
    /** Reports found in the store before this run. */
    pending: number;
    /** Reports that carried an identity and were folded into the ledger. */
    recorded: number;
    /** Identity-less entries consumed and discarded. */
    discarded: number;
    /** The snapshot blob was (re)published from the ledger this run wrote or held. */
    published: boolean;
    /** Why the publish failed, when it did. */
    publishError?: string;
    /** The file was written (only when something was recorded). */
    fileWritten: boolean;
}
export declare function flushReportStore(backend: BlobBackend, ledger: ActivityLedger, ledgerPath: string): Promise<FlushResult>;
//# sourceMappingURL=activity-flush.d.ts.map