feat(a2a): implement A2A event queue publish/subscribe system #8545

Open
opened 2026-04-13 20:37:54 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Commit message type: feat
  • Scope: a2a
  • Branch name prefix: feat/v3.5.0-a2a-event-queue

Background and Context

As part of Epic #8423 (A2A Protocol Integration), the A2A event queue enables publish/subscribe communication between agents and the orchestration layer. This is essential for the autonomy hardening flow where multiple subplans need to communicate status updates.

This issue blocks Epic #8423.

Expected Behavior

  • An event queue supports publish and subscribe operations
  • Publishers can emit events with a topic, payload, and metadata
  • Subscribers can register handlers for specific topics
  • Events are delivered reliably (at-least-once delivery)
  • The event queue is backed by the database for persistence

Acceptance Criteria

  • EventQueue class is implemented with publish and subscribe methods
  • Events include: id, topic, payload (JSON), metadata, created_at, delivered_at
  • Subscribers can register handlers for specific topics
  • Events are persisted to the database
  • At-least-once delivery is guaranteed
  • Integration tests verify publish/subscribe for multiple topics
  • Unit tests achieve >= 97% coverage

Subtasks

  • Design Event data model and database schema
  • Implement EventQueue class with publish/subscribe
  • Implement topic-based routing for subscribers
  • Add database persistence for events
  • Implement at-least-once delivery guarantee
  • Write integration tests for publish/subscribe
  • Write unit tests for EventQueue

Definition of Done

  1. EventQueue is implemented with publish/subscribe
  2. Integration tests verify event delivery for multiple topics
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Metadata - **Commit message type**: `feat` - **Scope**: `a2a` - **Branch name prefix**: `feat/v3.5.0-a2a-event-queue` ## Background and Context As part of Epic #8423 (A2A Protocol Integration), the A2A event queue enables publish/subscribe communication between agents and the orchestration layer. This is essential for the autonomy hardening flow where multiple subplans need to communicate status updates. This issue blocks Epic #8423. ## Expected Behavior - An event queue supports publish and subscribe operations - Publishers can emit events with a topic, payload, and metadata - Subscribers can register handlers for specific topics - Events are delivered reliably (at-least-once delivery) - The event queue is backed by the database for persistence ## Acceptance Criteria - [ ] `EventQueue` class is implemented with publish and subscribe methods - [ ] Events include: id, topic, payload (JSON), metadata, created_at, delivered_at - [ ] Subscribers can register handlers for specific topics - [ ] Events are persisted to the database - [ ] At-least-once delivery is guaranteed - [ ] Integration tests verify publish/subscribe for multiple topics - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Design `Event` data model and database schema - [ ] Implement `EventQueue` class with publish/subscribe - [ ] Implement topic-based routing for subscribers - [ ] Add database persistence for events - [ ] Implement at-least-once delivery guarantee - [ ] Write integration tests for publish/subscribe - [ ] Write unit tests for EventQueue ## Definition of Done 1. `EventQueue` is implemented with publish/subscribe 2. Integration tests verify event delivery for multiple topics 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.5.0 milestone 2026-04-13 20:56:32 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#8545
No description provided.