[TASK] Find out if it's feasible to turn the CLI also to an A2A server

[edenreich]

Summary

In agentic systems, specifically A2A protocol, it's a communication happening between a client and a server, if the system want to scale properly, the client (the CLI) should also act as a server, allowing to accept tasks from other agents.

Currently the CLI only act as an A2A client and a coding assistant.

If this is possible, it would be easier to scale the agents to be general purposed, and deploy them on any running instance.

Acceptance Criteria

• It's explored whether it's a good architecture to make the client also a server - closing the cycle
• It's explored this will reduce the amount of code needed for all the other A2A future developments
• It's explored whether it will be easy to use the ADL (Agent Definition CLI) to generate CLIs with embedded specific code for each particular agent - for example a browser-agent might be a CLI that just loads browser specific code and drivers dynamically and execute them

When the A2A client becomes also the A2A server there is a true agent-to-agent communication. Currently it's one way, but the goal is to explore whether it's feasible to make it both ways.