import type { Message, SessionEvent } from '@wrongstack/core/types';
import type { HistoryEntry } from './types.js';
/**
 * Canonical session-resume renderer. Rebuilds the visible TUI history for a
 * resumed session from the reconstructed `messages` (the conversation
 * backbone — user/assistant/system text, thinking blocks, and tool calls with
 * their input + output) and interleaves the audit `events` marker stream
 * (mode/compaction/checkpoint/skill/agent/error/retry/truncation) at their
 * chronological positions.
 *
 * Ordering is a two-pointer merge of two already-chronological sequences
 * (message backbone by construction, marker events by JSONL order) so the
 * conversation is never reordered — markers are only inserted between existing
 * turns. This is the single renderer used by BOTH the boot `--resume` path and
 * the in-session resume picker, replacing the previous message-only and
 * meta-only tool-chip variants.
 */
export declare function replaySessionMessages(messages: readonly Message[], events: readonly SessionEvent[], startId: number): HistoryEntry[];
/**
 * Raw-event replay: renders the JSONL stream directly, without the
 * reconstructed message backbone.
 *
 * @deprecated Not the resume renderer. Use {@link replaySessionMessages} —
 * it is the canonical one, and the only one both the boot `--resume` path and
 * the in-session resume picker use. This variant cannot reconstruct sessions
 * written through the exact message journal (`message_appended`/`_updated`/
 * `_replaced`), because those events carry the conversation and this function
 * ignores them. Kept for the legacy event-only tests and any embedder holding
 * a bare event array; deliberately absent from the package barrel.
 */
export declare function replaySessionEvents(events: SessionEvent[], startId: number): HistoryEntry[];
//# sourceMappingURL=replay.d.ts.map