import { readSceneSelectionArtifact } from './scene-selection-store.js';
import { readSceneCandidatesArtifact } from './scene-candidate-store.js';
import { refreshExecutionStatus } from './execution-status.js';
import type { VideoProductionMode } from './types.js';
/**
 * Poll a just-submitted scene to completion. On async routes (e.g.
 * seedance-direct) `executeProject` returns after SUBMIT — the render finishes
 * later via polling — so auto-chain MUST wait for the scene's candidate to gain
 * a video output before the next scene can chain from it (otherwise the chain
 * seed resolves to a video-less candidate and `chain-from-prev-source-missing`
 * fires). Returns true once a video output exists; false if the job fails or the
 * attempts are exhausted. Dependencies are injectable for offline tests.
 */
export declare function waitForSceneVideo(projectSlug: string, sceneIndex: number, deps: {
    root: string;
    productionMode?: VideoProductionMode;
    refresh?: typeof refreshExecutionStatus;
    readCandidates?: typeof readSceneCandidatesArtifact;
    sleep?: (ms: number) => Promise<void>;
    intervalMs?: number;
    maxAttempts?: number;
}): Promise<boolean>;
/**
 * Adopt-in-flight guard (shared by all three unattended drivers). Returns the id
 * of a candidate that was ALREADY submitted for this scene on a prior/concurrent
 * pass — a candidate carrying a live provider job id (`source.externalJobId`),
 * not `failed`, for a scene with no selection yet — or null.
 *
 * The drivers' resume check is selection-only, so a scene that crashed AFTER the
 * provider submit but BEFORE `selectCandidate` (a poll window that can be many
 * minutes on async routes) reads as "not done" and gets RE-SUBMITTED → a second
 * paid render for the same scene. When this returns a candidate, the caller must
 * poll+adopt it via {@link resolveInFlightScene} instead of submitting again.
 * Prefers the highest generationRound (the most recent attempt).
 */
export declare function findInFlightCandidateId(root: string, projectSlug: string, sceneIndex: number, deps?: {
    readCandidates?: typeof readSceneCandidatesArtifact;
    readSelection?: typeof readSceneSelectionArtifact;
}): Promise<string | null>;
/**
 * Poll an in-flight scene (found via {@link findInFlightCandidateId}) to a
 * TRI-STATE outcome — deliberately NOT a boolean, because the distinction is
 * spend-critical:
 *   - `'rendered'`: a video output landed → the caller selects the adopted
 *     candidate (the common crash-during-poll case: the render finished server-
 *     side while the operator was away).
 *   - `'failed'`: the provider reported the job failed → the prior spend is
 *     definitively resolved, so a fresh submit is safe (NOT a double charge).
 *   - `'pending'`: still running at the provider after the poll budget → the
 *     caller must NOT re-submit (that WOULD double-charge); re-running later
 *     re-adopts it. Conflating this with 'failed' is what would reintroduce the
 *     double-submit, so they are kept distinct.
 */
export declare function resolveInFlightScene(projectSlug: string, sceneIndex: number, deps: {
    root: string;
    productionMode?: VideoProductionMode;
    refresh?: typeof refreshExecutionStatus;
    readCandidates?: typeof readSceneCandidatesArtifact;
    sleep?: (ms: number) => Promise<void>;
    intervalMs?: number;
    maxAttempts?: number;
}): Promise<'rendered' | 'failed' | 'pending'>;
//# sourceMappingURL=execute-autochain.d.ts.map