/**
 * Session key generation for persona sessions.
 *
 * When multiple steps share the same persona but use different providers
 * (e.g., claude-eye uses Claude, codex-eye uses Codex, both with persona "coder"),
 * sessions must be keyed by provider and model to prevent incompatible resume.
 *
 * Without provider in the key, a Codex session ID could overwrite a Claude session,
 * causing Claude to attempt resuming a non-existent session file (exit code 1).
 */
import type { WorkflowStep } from '../models/types.js';
import type { ProviderType } from '../../shared/types/provider.js';
export interface ResolvedSessionTarget {
    provider?: ProviderType;
    model?: string;
    /** Deterministic MCP server set identity including non-secret server structure. */
    mcpServerIdentity?: string;
}
/**
 * Build a unique session key for a step.
 *
 * - Base key: `step.sessionKey ?? step.persona ?? step.name`
 * - A resolved provider and model are encoded with the base key as a JSON tuple
 *   to disambiguate arbitrary component values.
 *
 * sessionKey is validated at parse time by Zod (z.string().trim().min(1).optional()),
 * so it is guaranteed to be a non-empty, trimmed string when present.
 *
 * Examples:
 *   - persona="coder", provider=undefined  → `["coder"]`
 *   - persona="coder", provider="claude", model="sonnet" → `["coder","claude","sonnet"]`
 *   - persona="coder", provider="codex", model="gpt-5" → `["coder","codex","gpt-5"]`
 *   - persona=undefined, name="plan"       → `["plan"]`
 */
export declare function buildSessionKey(step: WorkflowStep, resolvedTarget?: ResolvedSessionTarget): string;
//# sourceMappingURL=session-key.d.ts.map