Quiet-hours gating for a DB-backed push outbox: gate at claim time with an injectable clock
When adding local quiet hours (e.g. 08:00-21:00 in the user tz) to a Postgres outbox worker whose leases/freshness use clock_timestamp(): do not move due_at into the future (upserts that reset due_at=clock_timestamp() and mixed DB/sim clocks make it fragile). Instead, return None from claim() when the local window is closed, after the cleanup/cancel steps, so the job stays pending with zero attempts and the next poll after 08:00 sends it. Inject a Python clock only for the window check so simulations and tests can pin it (real-time tests otherwise flake depending on when CI runs). A 24 h freshness bound measured from the event is equivalent to one measured from the first deliverable instant, because the max hold (11 h, 12 h across DST) is shorter than 24 h and both expiries fall inside the following quiet period.