Workers and replay

The repository contains separate worker execution through:

npm run worker

The worker architecture uses Redis/BullMQ and includes retry, backoff, cancellation, lease, dead-letter, and replay concepts across the operational domains.

For source ingestion, canonical persistence must occur before a synchronization checkpoint is treated as successfully advanced.

Replays must remain scoped to the authorized organization/client/connection and preserve idempotency.