import type { LoadedGraph, LoadedModule } from "@telorun/analyzer";
import type { DefinitionResult } from "../types.js";
import type { ResolvedCursor } from "../completions/resolve-node.js";
import type { AliasQualifiedValue } from "./alias-qualified-value.js";
/** Whether the cursor sits in a slot whose value is an alias-qualified kind.
 *
 *  `x-telo-ref` is an `x-telo-*` annotation, unambiguous wherever it appears.
 *  `extends:` is only a kind at the top level of a definition doc, so it is
 *  gated on both. `kind:` is positional by nature: a map carrying a
 *  `<Alias>.<Kind>` value under `kind` IS an inline resource declaration as far
 *  as the analyzer is concerned too (`resourceKindOf`), so there is no further
 *  structure to check — an unresolvable value simply navigates nowhere.
 *
 *  `capability:` is deliberately absent — its values are kernel built-ins with
 *  no manifest to jump to (hover documents them instead). */
export declare function isKindSlot(resolved: ResolvedCursor): boolean;
/** Resolve an alias-qualified kind (`Http.Server`) to the `Telo.Definition` /
 *  `Telo.Abstract` doc that registers it, or — when the cursor sits on the
 *  alias — to the import that declares the alias.
 *
 *  `Self.<Kind>` is the declaring module's own kind; `Telo.<Kind>` is a kernel
 *  built-in with no manifest, so it resolves to nothing. Across an import the
 *  walk honors `exports.kinds` and follows `<Inner>.<Kind>` re-exports to the
 *  owning module, matching what the kernel resolves the kind to at runtime. */
export declare function resolveKindTarget(graph: LoadedGraph, currentModule: LoadedModule, kind: AliasQualifiedValue): DefinitionResult | undefined;
//# sourceMappingURL=resolve-kind-target.d.ts.map