Store events and create deliveries in the delivery engine (closes #544) #555

Merged
clawbot merged 1 commits from issue-544-engine-write-path into next 2026-10-16 00:51:27 +02:00
1 Commits
Author SHA1 Message Date
sneak cb5fbb4db7 Store events and create deliveries in the delivery engine (closes #544)
check / check (push) Waiting to run
The receiver, resubmit and replay handlers now read and check the
request and make one call. Engine.StoreEvent stores an event with a
pending delivery for each active target and the totals in one
transaction, then queues them; Engine.CreateReplay does the same for
one replay delivery. The handlers take *delivery.Engine, so the
Notifier interface and its bridge are gone, and the engine's notify is
no longer exported. Archives and CircuitBreakers stay because the
handler tests fake them. The tests that read a queued task moved to
the engine's tests; the handler tests use an engine that is never
started.

Model: opus-5-5
2026-10-15 22:32:49 +00:00