/**
 * `dql lineage` — Answer-layer lineage analysis.
 *
 * Shows how data flows from source tables through blocks, semantic metrics,
 * domains, and charts. Tracks trust chains and cross-domain impacts.
 *
 * Usage:
 *   dql lineage [path]                    Show full lineage graph summary
 *   dql lineage <name> [path]             Show upstream/downstream for a block, table, or metric
 *   dql lineage --term <name> [path]      Show lineage for a business term
 *   dql lineage --business-360 <name>     Show business definition, sources, consumers, and gaps
 *   dql lineage --business [name] [path]  Show business lineage, optionally focused on a view
 *   dql lineage --table <name> [path]     Show lineage for a specific source table
 *   dql lineage --metric <name> [path]    Show lineage for a specific metric
 *   dql lineage --domain <name> [path]    Show lineage within a domain
 *   dql lineage cross-domain [--domain <name>]
 *                                         Show cross-domain boundary flows
 *   dql lineage --impact <name> [path]    Impact analysis: what breaks if this node changes?
 *   dql lineage --trust-chain <from> <to> Show trust chain between two blocks
 *   dql lineage --search <term> [path]    Search lineage nodes by name
 *   dql lineage --focus <name> [path]     Show a focused lineage subgraph
 *   dql lineage --dashboard <name> [path] Show lineage for a dashboard/notebook
 *   dql lineage --dbt [path]              Show the dbt portion of lineage
 *   dql lineage --export [path]           Export lineage as JSON
 *   dql lineage --no-manifest             Force live scan (skip dql-manifest.json)
 */
import type { CLIFlags } from '../args.js';
export declare function runLineage(blockNameOrPath: string | null, rest: string[], flags: CLIFlags): Promise<void>;
//# sourceMappingURL=lineage.d.ts.map