/** One stale checkpoint the operator deliberately admitted, for the resume journal. */
export interface StaleCheckpointConsent {
    readonly name: string;
    readonly capturedAt: string;
    readonly ageMs: number;
    readonly horizonMs: number;
}
/**
 * Run section 2.2's gates over every seat checkpoint the cut wrote, restore the captured bytes,
 * then take custody of each seat.
 *
 * Gate 2 is told which lifecycle uids are live. On these paths that set is empty and the reason is
 * structural rather than an omission: a preserved resume is only reached from a `ready` journal,
 * which `down --preserve-state` publishes after it has proven every recorded process stopped and
 * the exact recorded endpoint unreachable. There is no roster to consult because there is no
 * broker. A destination that resumes against a live space supplies the roster instead.
 *
 * The restore runs inside the admission, after every gate and before any generation is claimed, so
 * a refusal costs nothing: no tree has been promoted, no claim has been made, nothing has started.
 */
export declare function admitAndRestoreSeatCheckpoints(root: string, space: string, attemptId: string, values: {
    "accept-stale-checkpoint"?: boolean;
}, inventory: unknown, 
/** Where the progress lines go. `up` keeps them on stdout; `backup restore` owns stdout for its one
 *  receipt and passes stderr. */
progress?: (line: string) => void): StaleCheckpointConsent[];
//# sourceMappingURL=seat-resume.d.ts.map