import { type LoadedGraph } from "@telorun/analyzer";
import type { DefinitionResult } from "../types.js";
/** Resolve the kind suffix `name` exported by the module at `targetSource` to
 *  the `Telo.Definition` / `Telo.Abstract` doc that owns it.
 *
 *  The gate and the transitive re-export chain come from the analyzer's own
 *  `resolveExportedKinds` fixpoint rather than a local walk, so navigation
 *  cannot disagree with `telo check` about what an import exposes — including
 *  the two rules a hand-rolled walk gets wrong: `exports.kinds: []` gates
 *  everything while an absent block gates nothing, and a re-export FROM an
 *  ungated module resolves straight to it. */
export declare function resolveExportedKind(graph: LoadedGraph, targetSource: string, name: string): DefinitionResult | undefined;
/** Resolve the instance `name` exported by the module at `targetSource`,
 *  following `<Alias>.<name>` re-exports transitively. `seen` bounds cyclic
 *  import graphs.
 *
 *  Unlike kinds there is no permissive default: the kernel reads
 *  `exports.resources ?? []` and builds its export table strictly from that, so
 *  an absent block exports nothing and an unlisted name is an
 *  `UNRESOLVED_REFERENCE` — navigating to it would tell the author a wiring is
 *  real that the analyzer rejects. */
export declare function resolveExportedResource(graph: LoadedGraph, targetSource: string, name: string, seen?: Set<string>): DefinitionResult | undefined;
//# sourceMappingURL=resolve-export-chain.d.ts.map