/**
 * The pure text transforms behind `svelte-docsmith archive-version`. Archiving
 * copies the docs root into a frozen version folder, and a verbatim copy gets
 * two things wrong: its links keep resolving to the current docs, and every page
 * looks like it changed on the day the archive was made. These fix both.
 *
 * Kept here rather than in `bin/` so they are typechecked and unit-tested; the
 * CLI is a thin wrapper over them. See `docs/adr/0002-archives-are-rewritten-source-copies.md`.
 */
/** Route files at the docs root that an archive nested inside it already inherits. */
export declare function isInheritedRouteFile(name: string): boolean;
/**
 * Point a page's docs links at the archive it is being copied into. An absolute
 * link like `](/docs/theming)` resolves to the *current* docs forever, so
 * without this an archive silently walks readers into newer content.
 *
 * Links already targeting a version folder are left alone, as are links inside
 * fenced code, which are sample code rather than navigation.
 */
export declare function rewriteDocsLinks(text: string, options: {
    docsBase: string;
    versionId: string;
    archivedIds?: Iterable<string>;
}): string;
/**
 * Write a page's real last-updated date into its frontmatter. The collector
 * prefers frontmatter over the git date, so an archive keeps the date each page
 * was actually accurate on instead of the day the archive was created. Leaves an
 * existing `lastUpdated` and any page without frontmatter alone.
 */
export declare function freezeLastUpdated(text: string, date: string | undefined): string;
/**
 * The specifiers a page's `<script>` imports from outside the freeze boundary,
 * deduplicated in source order. `pageDir` is the page's directory relative to
 * the docs root, which is what its relative imports resolve against.
 *
 * Archiving copies the docs root and nothing else, so anything reached from
 * outside it keeps resolving to current code: a live example on an archived
 * page demonstrates the current library rather than the version the page
 * documents, with a green build and nothing said. Hence `$lib`, bare npm
 * specifiers and relative paths that climb out all count, while a relative
 * import landing inside the docs root is frozen along with the page.
 *
 * `svelte-docsmith` itself is never reported. An archived page importing the
 * authoring components is the expected shape, and those are covered by the
 * stability promise rather than by this notice. See
 * `docs/adr/0005-an-archive-freezes-content-not-dependencies.md`.
 */
export declare function boundaryCrossings(source: string, pageDir: string): string[];