Cache runs listing now accepts a field-scoped date range filter on the ran_at field, so reporting clients (including the generated Swift command-line client) can request runs from a specific execution window without paginating the full history.
Use ran_at[gt], ran_at[gte], ran_at[lt], and ran_at[lte] query parameters with Unix timestamps (seconds) to bound the response. Invalid or out-of-range timestamp filters return a 400 response with a concrete error message instead of silently returning everything.
Cache run responses now also report ran_at from the stored execution timestamp rather than deriving it from created_at, so the filter and the response field line up. Existing filters (git reference, branch, commit, pagination) keep working alongside the new range filter.