/**
 * NativeHealDegradationBridge — surface NativeModuleHealer failures on the
 * user-visible DegradationReporter path.
 *
 * Without this bridge, a failed better-sqlite3 rebuild only lands in
 * <stateDir>/native-module-heals.jsonl and console.error. The agent then
 * silently runs with SemanticMemory / TopicMemory / MemoryIndex / TokenLedger
 * degraded and no Telegram alert ever fires. DegradationReporter is the
 * canonical path for "the primary failed, the user should know" — this
 * bridge connects the two.
 *
 * Scope: failure events only. Successful heals are silent on purpose —
 * the feature recovered, no user action is required. The listener still
 * fires on success so future health-info consumers can subscribe without
 * a parallel dispatch surface.
 *
 * Dedupe: one degradation event per component per process. Heals are
 * already once-per-process via NativeModuleHealer.healAttempted, but the
 * Set in here defends against future surface-area changes (e.g. per-module
 * heal retries) that would otherwise spam the alert path.
 */
import { DegradationReporter } from './DegradationReporter.js';
/**
 * Subscribe a DegradationReporter to NativeModuleHealer heal events.
 * Returns the unsubscribe function from NativeModuleHealer.onHealEvent
 * so tests (or future hot-reload code) can detach the bridge.
 *
 * The `reporter` parameter is exposed primarily for tests; production
 * callers should rely on the DegradationReporter singleton default.
 */
export declare function bridgeNativeHealToDegradation(reporter?: DegradationReporter): () => void;
//# sourceMappingURL=NativeHealDegradationBridge.d.ts.map