/**
 * Lib-side `<a>` wrapper for chat-rendered links (markdown bodies,
 * source-chip drill-ins, inline references).
 *
 * Reads the active `ChatRuntime` and routes clicks through
 * `handleChatNavClick`. Same single-source rules as source chips and
 * inline cards:
 *   - new-tab decision via `computeIsNewTab` (embed-mode short-circuit
 *     + `runtime.navigation.decideNewTab` + lib fallback)
 *   - `target` / `rel` via `newTabAnchorAttrs`
 *   - same-tab click → close the chat panel (via `ChatPanelContext`);
 *     new-tab click → leave panel open while the new tab loads
 *
 * Chat-only contract: uses `useRequiredChatRuntime`, which THROWS when
 * mounted outside a `<ChatRuntimeContext.Provider>`. That's by design —
 * the lib should never silently fall back when the runtime is missing
 * (the chat tree always provides one in both host + embed modes).
 *
 * For surfaces OUTSIDE the chat tree (header chrome, marketing pages, …)
 * the hub keeps its own `useNavLink`-based anchor.
 */
import type { ReactNode } from 'react';
export interface NavLinkAnchorViaRuntimeProps {
    href: string;
    path?: string | null;
    targetPlatform?: string | null;
    className?: string;
    /** Optional — matches `NavLinkAnchorComponent`'s contract so the
     *  markdown-anchor slot can render an empty anchor (rare but legal). */
    children?: ReactNode;
}
export declare function NavLinkAnchorViaRuntime({ href, path, targetPlatform, className, children, }: NavLinkAnchorViaRuntimeProps): import("react").JSX.Element;
//# sourceMappingURL=nav-link-anchor-via-runtime.d.ts.map