/**
 * Un-strand sessions found by `chat-recall verify --deep`.
 *
 * A stranded session is one whose ledger cursor says "the server has all of
 * this" while the server demonstrably has less. Nothing re-ships it, because
 * `syncMode` reads that cursor and returns SKIP. Clearing the cursor is what
 * puts it back in the queue — the next sync then re-derives and re-ships from
 * scratch.
 *
 * Only the CURSOR is cleared, not the whole row: per-field coverage (`f`) is
 * owned by field reconciliation and dropping it would make every field re-scan
 * from zero. The mtime is cleared too, since leaving it would let the
 * mtime-unchanged branch SKIP the session straight back out again.
 *
 * Writes a timestamped backup first. This edits the file that decides what gets
 * uploaded, and a bad edit here re-ships a 10k-session corpus.
 */
/** Clear the sync cursor for `sessionIds` on `server`. Returns how many rows
 *  were actually cleared (ids with no ledger entry need no work). */
export declare function forceFullResync(server: string, sessionIds: string[]): number;
//# sourceMappingURL=verify-repair.d.ts.map