import type { GenerationResult, GeneratorConfig } from '../../types';
/**
 * Main orchestrator for the documentation generation pipeline.
 * Coordinates all phases: Discovery → Extraction → Enrichment → Generation
 */
export declare class PipelineOrchestrator {
    private config;
    private startTime;
    private errorHandler;
    constructor(config: GeneratorConfig);
    /**
     * Execute the complete documentation generation pipeline
     */
    execute(): Promise<GenerationResult>;
    /**
     * Phase 1: Discovery - Find all components and their files
     */
    private discoveryPhase;
    /**
     * Phase 2: Extraction - Extract props, variants, inheritance, docs
     */
    private extractionPhase;
    /**
     * Phase 3: Enrichment - Add cross-references, validate examples, generate API data
     */
    private enrichmentPhase;
    /**
     * Derive the doc-route base from the API output directory. The API/LLM
     * generators write per-component files under
     * `<…/routes>/<target>/[<group>/]<slug>`, so the public URL base is exactly
     * the output path's tail after the `routes/` segment — e.g.
     * `../../apps/docs/src/routes/blocks` → `/blocks` (from which primitives
     * resolve to `/blocks/primitives/<slug>` and components to
     * `/blocks/components/<slug>`), `.../routes/docs` → `/docs`, etc.
     *
     * Falls back to `/components` when the output path is not under a `routes/`
     * segment (e.g. an aggregate single-file config), preserving prior behaviour.
     */
    private deriveRouteBasePath;
    /**
     * Phase 4: Generation - Generate API file, then LLM docs
     * CRITICAL: API must be generated FIRST, then consumed by LLM
     */
    private generationPhase;
    /**
     * Create error result for failed pipeline execution
     */
    private createErrorResult;
    /**
     * Get current configuration
     */
    getConfig(): GeneratorConfig;
}
//# sourceMappingURL=PipelineOrchestrator.d.ts.map