/**
 * Memory-backed mission transcript sink — Phase 1.f wiring.
 *
 * `createMemoryTranscriptSink(memory, missionId)` returns a
 * `MissionTranscriptSink` the adapter hands to `runMission`. Each
 * step's `MissionTranscriptEntry` is serialised to JSON and persisted
 * via the shared `MemoryProvider` under the canonical
 * `mission:<id>` namespace.
 *
 * Why JSON content (and not the structured `MemoryRecord` fields):
 * `MemoryProvider.remember` only takes `content: string` (plus
 * optional tags/path). We pack the full step snapshot into `content`
 * so a downstream agent can `JSON.parse(record.content)` after
 * `memory_recall(namespace="mission:<id>")`. Tags are used as
 * coarse-grained filters (e.g. "step:ok" vs "step:error") for
 * future status queries.
 *
 * The returned sink is best-effort by contract — `runMission` already
 * swallows thrown errors, but we also defensively catch the await so a
 * mem0 outage never propagates back into the run loop.
 */
import type { MemoryProvider } from "./memory/index.js";
import type { MissionTranscriptSink } from "./mission.js";
/**
 * Build a transcript sink that writes each step's entry to memory.
 *
 * @param memory      Active memory provider (caller has already
 *                    confirmed `config.memory.enabled === true`).
 * @param missionId   Mission identifier. Surfaced as the namespace
 *                    and also embedded in the content for grep-ability.
 */
export declare function createMemoryTranscriptSink(memory: MemoryProvider, missionId: string): MissionTranscriptSink;
//# sourceMappingURL=mission-transcript-sink.d.ts.map