import type { PipelinePhase } from '../types.js';
export interface BridgeResolverOutput {
    edgesCreated: number;
}
/**
 * Cross-language bridge resolution — links calls across an FFI/IPC boundary
 * that no single language's own import/call resolution can see (Wails'
 * generated Go<->JS bindings, Tauri's invoke() commands, Electron's IPC
 * channels, ...). Each adapter in bridge-adapters/ extracts (key, nodeId)
 * pairs from both sides; here they're matched by key and turned into CALLS
 * edges — reusing the existing relation so every existing consumer
 * (monograph_impact, monograph_neighbors, community detection) picks them up
 * with no changes on their end.
 *
 * Confidence is always INFERRED: a bridge edge is a name/key match, not an
 * AST-verified call. A key with more than one matching definition is
 * dropped rather than guessed at — the call site can't know which one was
 * meant, and a wrong edge is worse than a missing one. Multiple call sites
 * sharing one definition (the common case: several UI files calling the
 * same bound method) is normal and always kept.
 */
export declare const bridgeResolverPhase: PipelinePhase<BridgeResolverOutput>;
//# sourceMappingURL=bridge-resolver.d.ts.map