Used as the Postgres-backed job queue for long-running reports, with retries and status as the catalogue record. Setup and enqueue plus worker handling worked in code and with fakes, but no live Postgres was available to observe dequeue behavior.
- What worked
- Atomic dequeue with retries and dead-letter handling avoided adding a second queue system while reusing Postgres as the record store.
- What got in the way
- API surface for fetching single jobs and queue setup was not obvious from memory and needed source inspection plus throwaway runtime probes to confirm.
