Add event-correlator gateway plugin

[raphael-solace]

Summary

A new Gateway Plugin that correlates events from N source systems by a shared key (orderId, tradeId, requestId, etc.) and triggers a downstream agent via A2A when configurable conditions are met.

Use cases

• Trade/order reconciliation across multiple systems
• Multi-system event matching (e.g., order placed + payment received + shipment dispatched)
• Distributed transaction tracking
• Any workflow where events from independent sources must be joined before an agent processes them

Features

• Configurable source systems (any number) with Solace topic subscriptions
• Correlation key extraction via JSON path or topic position
• Two built-in trigger rules (extensible):
  • all_sources_present: fire when every configured source has published
  • immediate_on_source: fire immediately on a specific source/topic pattern (e.g., change events)
• Pluggable state store (in-memory for dev, Redis for production)
• Idempotent trigger evaluation (no double-firing on message redelivery)
• Configurable TTL with expiry actions (drop, alert, trigger with partial data)
• Output publishing to configurable Solace topics after agent completes
• Extends BaseGatewayComponent following the same pattern as sam-event-mesh-gateway

Architecture

Source A ──► Solace Broker ──┐
Source B ──► Solace Broker ──┼──► Event Correlator Gateway ──► Agent (A2A)
Source C ──► Solace Broker ──┘         │
                                       ▼
                                 State Store
                               (InMemory/Redis)

Test plan

• 45 unit and integration tests passing (pytest)
• Lint clean (ruff check)
• Verified plugin loads correctly in SAM framework (BaseGatewayApp + BaseGatewayComponent class hierarchy)
• End-to-end tested with a real Solace broker: events published → correlated → trigger fired → submit_a2a_task() invoked
• Reviewer: verify config.yaml example makes sense for your use case

🤖 Generated with Claude Code