import type { AutomationManager } from '../../automation/index.js';
import type { FixSessionBrief, FixSessionStartOutcome } from '../../ci-watch/index.js';
/**
 * Start a one-shot fix-session pre-briefed with the failing CI jobs, and
 * return the REAL spawned session's id, the id session attach/resume
 * resolves. The automation job id ('auto-…') is a scheduling handle no
 * attach can resolve and must never be surfaced as the fix session; this is
 * pinned by test (job-id vs session-id confusion).
 *
 * Mechanics: the job is created DISABLED (the scheduler can never race a
 * second run) and executed immediately via runNow, whose returned run
 * carries the spawned ids. The job targets a pinned FRESH shared session
 * (never the operator's own preferred session), so the fix work lives in a
 * real attachable session with the spawned agent bound to it. A start that
 * produces no attachable session is an honest error outcome, never a dead id.
 */
export declare function startCiFixSession(automation: Pick<AutomationManager, 'createJob' | 'runNow'>, brief: FixSessionBrief): Promise<FixSessionStartOutcome>;
/**
 * Start a merge-conflict resolution session INSIDE the kept worktree, the
 * same seeded-session machinery as startCiFixSession, seeded with the tree
 * path, item branch, and the STRUCTURED conflict list. Returns the REAL
 * session id plus the job id (the run-completion hook keys on it to
 * re-attempt the merge and reclaim the tree), or an honest error.
 */
export declare function startConflictResolutionSession(automation: Pick<AutomationManager, 'createJob' | 'runNow'>, seed: {
    readonly workstreamId: string;
    readonly itemId: string;
    readonly title: string;
    readonly worktreePath: string;
    readonly branch: string | undefined;
    readonly files: readonly string[];
}): Promise<{
    sessionId: string;
    jobId: string;
} | {
    error: string;
}>;
//# sourceMappingURL=seeded-sessions.d.ts.map