/**
 * virtual-documents — split a mixed-syntax source file into the plain
 * documents Eddie's validators already understand (#1827, #1864).
 *
 * AGENTS.md §2.5 tells every agent in every BFW consumer repo:
 *
 *   > `eddie_validate_file` — Validate a `.ts` / `.scss` / `.vue` / `.njk` file
 *   > for token-usage violations and naming convention issues. **Run this
 *   > before every commit that touches Eddie code.**
 *
 * The tool did not do that. `.vue` and `.njk` hit the extension gate and came
 * back `validated: false` — next to `issueCount: 0`, which a caller skimming
 * for issues reads as a clean bill of health. That is the §2.13a shape: the
 * absence of a failure looking identical to the absence of a check. And it hit
 * exactly where it hurts most, because every BFW content site is Eleventy +
 * Nunjucks and every Nuxt consumer writes its Eddie markup in `.vue` SFCs — the
 * files the rule most wants checked were the files the tool refused.
 *
 * The validators each self-select by extension (`token-validator` returns `[]`
 * for anything but `.scss`/`.css`, `spacing-validator` for anything but
 * `.scss`, and so on), so nothing here needs to know which validator wants
 * which region. It only has to hand each region a filename with the right
 * extension, and remember where in the real file that region started so line
 * numbers can be mapped back.
 */
/** One extractable region of a source file, as a document a validator can read. */
export interface VirtualDocument {
    /** Extension to give the temp file, chosen so the right validators self-select. */
    ext: '.html' | '.scss' | '.css' | '.ts';
    /** The region's own text. */
    content: string;
    /**
     * Zero-based count of lines in the original file BEFORE this region's first
     * line. Add it to a reported line number to get back to the real file.
     */
    lineOffset: number;
    /** Human label for the region, so an issue can say where it came from. */
    region: string;
}
/**
 * Blank out Nunjucks/Jinja syntax while preserving the line structure exactly.
 *
 * Line-for-line fidelity is the whole point: an issue reported at line 40 of the
 * neutralised text has to be line 40 of the file the author will open. So every
 * newline inside a replaced span survives, and only the non-newline characters
 * are dropped.
 *
 * `{{ ... }}` and `{% ... %}` are removed rather than replaced with a token,
 * because the common shape is interpolation *inside* an attribute —
 * `class="ed-c-card {{ modifier }}"` — where removing the expression leaves
 * valid markup with a real class list, and substituting a placeholder would
 * invent a class name that the naming validator would then flag. `{# ... #}`
 * comments go the same way.
 */
export declare function neutraliseTemplateSyntax(source: string): string;
/**
 * Blank out Vue's control-flow `<template>` wrappers inside a template.
 *
 * `<template v-if>` / `v-else-if` / `v-else` / `v-for` group children at
 * compile time and render no element; the children land in the enclosing
 * element. Left in place, a markup scanner sees `<template>` as a real child:
 * `ed-grid > template` reads as a non-grid-item on a correct page (#2000). The
 * tags are replaced with spaces of the same length, so offsets and line
 * numbers are unchanged.
 *
 * Slot templates (`#name`, `v-slot:name`) are kept: they say which slot their
 * children go to, which a validator needs to know.
 */
export declare function neutraliseControlFlowTemplates(markup: string): string;
/**
 * Split a Vue SFC into its `<template>` and `<style>` regions.
 *
 * `<script>` is deliberately NOT extracted. The template validators read markup
 * and the style validators read CSS; the only validator that reads script is
 * the naming validator's Lit-template extractor, and a Vue `<script setup>` has
 * no Lit templates in it. Handing it one would produce findings about a syntax
 * it does not speak.
 *
 * A `<style>` block becomes `.scss` when it says so via `lang`, and `.css`
 * otherwise — which matters, because `spacing-validator` and the naming
 * validator's style path both key on `.scss`, and running them over plain CSS
 * that was never written to Eddie's SCSS conventions would be noise.
 */
export declare function splitVueSfc(source: string): VirtualDocument[];
/**
 * Split a source file into the virtual documents its validators can read.
 *
 * For a file that is already a plain document, this returns a single entry with
 * `lineOffset: 0` — so the caller has one code path whether or not any
 * splitting happened.
 */
export declare function toVirtualDocuments(filePath: string, source: string): VirtualDocument[];
/** Extensions this module can split into validatable regions. */
export declare const SPLITTABLE_EXTENSIONS: RegExp;
/**
 * Materialise a file's virtual documents as real files a validator can read,
 * run `body` over them, and clean up.
 *
 * The validators take a path and read it themselves, so a `<style>` block has
 * to become an actual `.scss` on disk before the SCSS validators will look at
 * it. This owns that scratch directory and its removal, so the two call sites —
 * the `eddie_validate_file` MCP tool and the `validate` CLI, which had drifted
 * into disagreeing about which extensions exist — cannot drift again on the
 * mechanics.
 *
 * A file that needs no splitting is passed through untouched: `docPath` is the
 * original path, nothing is written, and no scratch directory is created.
 */
export declare function withMaterialisedDocuments<T>(filePath: string, source: string, body: (docs: Array<{
    docPath: string;
    doc: VirtualDocument;
}>) => Promise<T>): Promise<T>;
/**
 * Rewrite an issue found in a virtual document so it points at the real file.
 *
 * A line number counted from the wrong place is worse than no line number, so
 * the region offset is added back and the region is named in the message.
 * Mutates and returns the issue, which is what both call sites want.
 */
export declare function remapIssueToSource<T extends {
    file?: string;
    line?: number;
    message: string;
}>(issue: T, doc: VirtualDocument, filePath: string): T;
//# sourceMappingURL=virtual-documents.d.ts.map