/**
 * `dql compile` — Generate the DQL project manifest.
 *
 * Scans all blocks, business views, notebooks, and semantic layer definitions,
 * resolves dependencies, builds lineage, and writes dql-manifest.json.
 *
 * Usage:
 *   dql compile [path]                        Compile project at path (default: .)
 *   dql compile --dbt-manifest <path>         Import dbt manifest.json as upstream
 *   dql compile --datalex-manifest <path>     Validate datalex_contract refs
 *   dql compile --dbt-hops <n>               Limit upstream dbt hops (default: unlimited)
 *   dql compile --out-dir <dir>               Write manifest to a specific directory
 *   dql compile --format json                 Output manifest to stdout (no file write)
 *
 * Selective dbt import (automatic for projects > 200 models):
 *   Only imports the dbt models/sources that are reachable upstream from the
 *   tables your DQL blocks actually reference. This keeps dql-manifest.json
 *   small and fast even in 4000+ model repos.
 */
import { type TrackedFile } from '@duckcodeailabs/dql-project';
import type { CLIFlags } from '../args.js';
export declare function manifestCacheTrackedFiles(inputFiles: string[], dqlVersion: string): TrackedFile[];
export declare function readCliDqlVersion(): string;
/**
 * The compile result is deliberately small: callers such as `dql sync dbt`
 * need to know whether a cache hit also left the persisted retrieval snapshot
 * usable.  They must not infer that from the compiler cache alone because the
 * metadata/KG snapshot has an independent source-version contract.
 */
export interface CompileResult {
    cacheHit: boolean;
    /** True only when the project-root manifest was unchanged and the persisted
     * metadata + KG snapshot was already prepared for that exact source version. */
    reusedPreparedAgentIndex: boolean;
}
export declare function runCompile(pathArg: string | null, rest: string[], flags: CLIFlags): Promise<CompileResult | undefined>;
//# sourceMappingURL=compile.d.ts.map