Struct AgentDispatcher 

pub struct AgentDispatcher {
    peers: Arc<dyn WorkspaceFacade>,
    workers: Arc<dyn WorkerFacade>,
}

The two engines, both held: a target inside the caller’s project is served by the workers engine and one outside it by the peers engine. Keeping both is what makes this a dispatcher rather than a third implementation.

Fields

peers: Arc<dyn WorkspaceFacade>

workers: Arc<dyn WorkerFacade>

Implementations

impl AgentDispatcher

pub fn new( peers: Arc<dyn WorkspaceFacade>, workers: Arc<dyn WorkerFacade>, ) -> Self

pub fn peers(&self) -> &Arc<dyn WorkspaceFacade>

The cross-project engine, for listing configured projects and reading the caller’s own identity.

pub fn workers(&self) -> &Arc<dyn WorkerFacade>

The in-project engine, for the caller’s own workers and every worker lifecycle verb.

pub async fn deliver( &self, caller: &SessionSlot, target: &AgentTarget, wrapped: WrappedPrompt, ) -> Result<(), String>

Hand wrapped to target’s seat. The engine’s own answer is whether the message was accepted, not whether it was read, so a success says nothing more than that.

Three of the four paths are the ones the two families already had, unchanged. The fourth is the reach the merge adds: a worker address in another project, which the peers engine cannot serve because it resolves a project to that project’s own agent.

async fn deliver_within_own_project( &self, caller: &SessionSlot, target: &AgentTarget, wrapped: WrappedPrompt, ) -> Result<(), String>