Runtime lane

Outbox, replay, DLQ, and metrics all stay visible.

The runtime stack is built to keep operator visibility high: every queue pressure, replay path, audit count, and readiness signal is meant to be visible both in backend tools and in the app surface.

Health endpoints

/health + /ready

Outbox lanes

due / failed / dead_letter

Topics

incoming / replay / dead_letter

Operational controls

Transactional outbox and relay worker.
Manual replay and replay-all-dead-letters endpoints.
Prometheus metrics for attempts, deliveries, failures, DLQ, and queue age.
Grafana dashboard for runtime overview and queue state trends.

Why this matters

Signal

Runtime pulse is visible on device and backend at the same time.

Safety

Replay and DLQ are explicit operator actions, not hidden retries.

Delivery

Cloudflare presentation layer stays separate from the runtime control plane.