/**
 * `/chain export`: the chain as one page, written beside the folders it ran in.
 *
 * pi's own `/export` shows none of a chain. A step is a `custom` entry, which
 * pi keeps out of the model's context and out of its HTML export alike, and
 * `/export` is built into pi with no event an extension can hook. The steps
 * are on disk already, one folder each, and this page reads them in order:
 * what each was asked, what it answered, and where its transcripts are.
 *
 * Markdown, because what a step answers is Markdown. Requests and outputs go
 * in fences, so a heading inside an answer cannot break the page's outline.
 */
import { type Relay, type RelayStep } from "./relay.ts";
/** The page's name in the chain's folder. */
export declare const CHAIN_FILE = "chain.md";
/** Writes {@link chainPage} into the chain's folder, replacing an older one, and returns its path. */
export declare function writeChain(relay: Relay): string;
/**
 * The page for a chain. `transcripts` lists a step's HTML transcripts, relative
 * to the chain's folder: injected, so the page can be checked without a disk.
 */
export declare function chainPage(relay: Relay, transcripts: (step: RelayStep) => string[]): string;
//# sourceMappingURL=chain-export.d.ts.map