import type { ArtifactBundle } from "../io/artifacts.js";
import type { AuditTask } from "../types.js";
/**
 * The single pending-set derivation (INV-PENDING-SINGLE-SOURCE): host workload
 * construction and the completion gate (`deriveAuditState`'s
 * `audit_tasks_completed` obligation) both consume THIS partition, so the two
 * can never disagree on which tasks still need work.
 *
 * Semantics (the O3 staleness gate's consume half): results resolve to the
 * CURRENT record per lineage (`selectCurrentResults`), and a task whose current
 * result has DRIFTED from its recorded content-key baseline is pending again —
 * it must return for review even though its stale result left it status
 * `complete`. Consumers layer their own presentation ordering on top.
 */
export interface PendingTaskPartition {
    /** Tasks whose current result drifted from its baseline (must be reviewed again). */
    staleResultTaskIds: Set<string>;
    /** Tasks with a current, non-drifted result (genuinely done). */
    completedTaskIds: Set<string>;
    /** Tasks that still need work, in `bundle.audit_tasks` order. */
    pendingTasks: AuditTask[];
}
export declare function derivePendingTaskPartition(bundle: ArtifactBundle): PendingTaskPartition;
//# sourceMappingURL=pendingTasks.d.ts.map