export interface MCPCatalogAssemblerConfig {
    staticDirs: string[];
    recipesDir: string;
    outputPath: string;
    version: string;
}
/**
 * Assembles the final component-catalog.json from per-package _catalog.json
 * files and extracted recipe data.
 */
export declare class MCPCatalogAssembler {
    private config;
    constructor(config: MCPCatalogAssemblerConfig);
    assemble(): Promise<{
        outputPath: string;
        componentCount: number;
        recipeCount: number;
    }>;
    private collectComponents;
    private extractRecipes;
    private extractRecipeFromMeta;
    /**
     * Extract the `const recipeCode = …` live-preview source from a recipe
     * `+page.svelte`.
     *
     * A backslash escape is skipped whole. Without that, an escaped backtick
     * inside the literal — the legal way to write one, and the only way a prose
     * comment in the snippet can quote a prop name — closed the scan early, and
     * `get_recipe` shipped the recipe truncated at that point with nothing
     * reporting it. (An *un*escaped backtick is a syntax error the Svelte
     * compiler already catches, so this is the half no other gate sees.)
     */
    static extractRecipeCode(content: string): string;
    /**
     * Resolve template-literal escape sequences the way JS does when the page
     * renders the string. The literals escape more than the backtick: the
     * closing `<\/script>` and — since the 2026-08-16 rollout — the OPENING
     * `<\script` too (Vite's dependency scanner extracts script blocks from
     * .svelte files with an HTML lexer, so a raw `<script` inside a string
     * literal starts a phantom module whose `$lib/…` imports then fail the
     * whole scan with ENOENT). Shipping the raw source would hand consumers
     * those backslashes verbatim; what `get_recipe` must serve is the cooked
     * string — exactly what the code panel displays.
     */
    static cookTemplateLiteral(source: string): string;
    private extractString;
    /**
     * Read a `key: [ 'a', 'b' ]` array of string literals out of a `meta.ts`.
     *
     * Scans quote by quote rather than splitting on commas: a comma inside a
     * literal is a character, not a separator. Splitting was the rule until
     * 2026-08-14, so every feature line containing one arrived in the catalog as
     * two or more entries, and `get_recipe` served the fragments to agents as if
     * each were a feature of its own. Measured on filter-sidebar: its six lines
     * came out as eleven, four of them the pieces of "Mixed filter controls" —
     * "RadioGroup property type", "range Slider for rent", "SegmentGroup
     * bedrooms", "Checkbox amenities".
     */
    static extractArray(content: string, key: string): string[];
    private slugToTitle;
}
//# sourceMappingURL=MCPCatalogAssembler.d.ts.map