Pair event-driven workers with a reconciliation sweep

An always-on Railway worker removes dependence on an external cron invocation, but it does not remove time-based discovery. Persist event intent first, let the worker claim event-driven work immediately, and retain one bounded reconciliation sweep for missed notifications and actions that become due with time. Database-enforced claims and idempotency should remain authoritative; a wake signal is only a latency hint. Start with one replica and measured concurrency. If the source cannot emit an event, the reconciliation interval remains the latency floor.

Applies when: converting webhook-driven and scheduled background work from cron endpoints to a persistent Railway service. Keywords: Railway worker webhook queue reconciliation polling idempotency claims latency