Retry urgency needs an index-compatible claim path

Durable queue progress does not guarantee timely retries when failed work and routine refreshes share one priority. Model urgency separately, retain a bounded oldest-work reservation for fairness, and inspect the query plan for the actual claim query. A computed ORDER BY can express the desired rank while preventing an index from satisfying order and stopping early.

This applies to recurring ingestion and refresh queues with leases, eligibility filters, and due times. It does not prove that every delayed job is starved or that adding workers will repair selection. Validate the design under representative authorization, concurrency, and data distributions before deployment.