/**
 * channel-composition, route bindings, surface registry, and channel plugin
 * registry for a host composition root (held apart from the composition root for the
 * line cap).
 *
 * RECORDED DIVERGENCE from the SDK composition root: SurfaceRegistry and
 * ChannelPluginRegistry are constructed WITHOUT the gate manager. The SDK's
 * surface gate map only names six surfaces (web/slack/discord/ntfy/webhook/
 * homeassistant) and reads every other adapter (telegram, whatsapp, signal,
 * imessage, msteams, ...) as OFF whenever a manager is present, no settings
 * key could re-enable them. Until the gate map covers every adapter, the
 * honest governing switch here stays the surfaces.<id>.enabled config each
 * adapter already reads, exactly as the feature surface's own
 * constant-binding rule states. RouteBindingManager keeps its manager, its
 * route-binding gate is a real registry feature.
 */
import { ChannelPluginRegistry, RouteBindingManager, SurfaceRegistry } from '../channels/index.js';
import type { ConfigManager } from '../config/index.js';
import type { FeatureFlagManager } from './feature-flags/manager.js';
import type { RuntimeEventBus } from './events/index.js';
import type { RuntimeStore } from './store/index.js';
export interface ChannelComposition {
    readonly routeBindings: RouteBindingManager;
    readonly surfaceRegistry: SurfaceRegistry;
    readonly channelPlugins: ChannelPluginRegistry;
}
export declare function createChannelComposition(options: {
    readonly configManager: ConfigManager;
    readonly runtimeStore: RuntimeStore;
    readonly runtimeBus: RuntimeEventBus;
    readonly featureFlags: FeatureFlagManager;
}): ChannelComposition;
//# sourceMappingURL=channel-composition.d.ts.map