import type { ResolvedSdocsConfig } from '../types.js';
/**
 * The site's section/route map, derived from the doc files exactly as the
 * Explorer derives it.
 *
 * One validation, three consumers: `build` refuses to deploy a broken
 * structure, `check` reports the same problems without building, and the
 * Explorer routes with it at runtime. Structure errors used to be visible
 * only to `build`, so `check` — the command CI is told to gate on — passed a
 * site that could not be built.
 */
export declare function buildSiteMap(config: ResolvedSdocsConfig, cwd: string): Promise<import("../explorer/tree-builder.js").SectionMap>;
/**
 * Grammar diagnostics across the project, as `file:line — message`.
 *
 * `sdocs check` treats every one of these as an error and exits 1. `build`
 * used to see none of them: it validates the site structure and then lets Vite
 * compile, and a bad note type or an attribute that does not exist compiles
 * perfectly well. So a project whose CI ran only `build` deployed a site whose
 * notes rendered untyped and whose attributes were quietly ignored, with a
 * green pipeline.
 */
export declare function collectGrammarErrors(config: ResolvedSdocsConfig, cwd: string): Promise<string[]>;