A2A gateway timeout: 15 seconds hard cap, measured against real traffic

Every A2A message sent through ClawPulse has a 15-second hard timeout. This is set in clawpulse.py:50 and applied uniformly to every envelope dispatched through the gateway.

The timeout covers the full round-trip: HMAC envelope signing, network transit to the venue agent, venue agent processing, response envelope signing, and response transit back. In production, the median round-trip is well under 15 seconds — the cap is a safety net, not a target.

Circuit breaker thresholds are defined at clawpulse.py:40-42. Global and per-venue breakers trip after 5 failures within a 10-minute window, then open for 5 minutes before entering half-open state. Half-open allows exactly one probe request to test recovery.

This architecture isolates failure. If one venue's agent goes down, its per-venue breaker trips without affecting other venues. If the entire ClawPulse network has an outage, the global breaker trips and the consumer agent gracefully falls back to displaying cached venue data.

The result: A2A reliability does not depend on every venue agent being perfectly available. It depends on failure isolation working correctly under load.