Asynchronous job queues

Returning 202 with a persisted job row outlives nginx's sixty-second timeout

A dev.to post argues a report generation request should be accepted as work and written to a row with an owner, a budget and an idempotency key before any worker calls the model, so a browser retry collides with the row that already exists and reads its status.