import type { ManagedSessionRow } from "../../db/repositories/managed-sessions.repository";
/**
 * Which id can actually resume a registry row (persistence plan Phase 3, gap G6).
 *
 * Claude's session id is always resumable as-is: it was passed to the CLI as
 * `--session-id`, so the JSONL is named after it and `--resume <id>` finds it.
 *
 * Codex has no such flag. A fresh Codex session is keyed by a local placeholder
 * UUID and its real rollout id arrives later, via `watchForCodexRollout`, as
 * `bound_conversation_id`. `codex resume <placeholder>` fails, so the bound id
 * is the only usable one — and a row that never bound has none at all, which is
 * what the `null` here means. Callers must treat `null` as "not resumable",
 * never as "resume by session_id".
 */
export declare function resumeIdForRow(row: ManagedSessionRow): string | null;
//# sourceMappingURL=resumeIdentity.d.ts.map