/**
 * agent-graph.ts, the four objects that make up a conversation loop's agent
 * graph, wired in the one order that works.
 *
 * The ordering is not cosmetic. `AgentOrchestrator` predates `AgentManager`, so
 * two of their links (the conversation-snapshot sink and the cooperative
 * cancellation source) cannot be constructor deps, they are set afterwards, on
 * the orchestrator, pointing back at the manager. Miss either and a spawned
 * agent's transcript never reaches a panel, or a cancel never reaches the run.
 * Both compositions that own a loop (the daemon-grade `createRuntimeServices`
 * and the pure-client `createClientRuntimeServices`) call this, so the order
 * exists in exactly one place.
 *
 * Nothing here is daemon-grade: a surface running its own loop owns this graph
 * outright, which is why it sits below the daemon furniture in the dependency
 * order and imports none of it.
 */
import type { ConfigManager } from '../config/manager.js';
import type { ProviderRegistry } from '../providers/registry.js';
import { AgentMessageBus } from '../agents/message-bus.js';
import { AgentOrchestrator } from '../agents/orchestrator.js';
import { ArchetypeLoader } from '../agents/archetypes.js';
import { AgentManager } from '../tools/agent/index.js';
import type { RuntimeEventBus } from './events/index.js';
export interface AgentGraphOptions {
    readonly runtimeBus: RuntimeEventBus;
    readonly configManager: ConfigManager;
    readonly providerRegistry: ProviderRegistry;
    /** Project root; the per-project archetype directory hangs off it. */
    readonly workingDirectory: string;
}
/** The agent graph a conversation loop runs on. */
export interface AgentGraph {
    readonly archetypeLoader: ArchetypeLoader;
    readonly agentMessageBus: AgentMessageBus;
    readonly agentOrchestrator: AgentOrchestrator;
    readonly agentManager: AgentManager;
}
export declare function createAgentGraph(options: AgentGraphOptions): AgentGraph;
//# sourceMappingURL=agent-graph.d.ts.map