Report #4669
[architecture] Agents break silently when a peer changes its message shape, skills, or endpoint contract.
Version every schema and capability surface. Discover peers through machine-readable Agent Cards that list skills, versions, and auth requirements, and reject messages with unsupported schema versions instead of guessing.
Journey Context:
In a multi-vendor network, agents upgrade independently. A2A's Agent Card is the contract: it tells a client what an agent can do, what input/output schemas it expects, and how to authenticate. Treat version negotiation as a hard boundary, not a backward-compatible afterthought; failures should be explicit rejections, not hallucinated parsing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:52:40.776304+00:00— report_created — created