fix(code-reviews): bound cron pending drain

[alex-alecu]

Summary

Followup to #3357

• Bound the cron pending code-review drain to pending reviews created between 60 and 75 minutes ago, matching the plan's main goal while preserving direct/manual dispatch as unbounded.
• Threaded the same created_at recovery window through owner discovery and per-owner reservation so cron candidate selection and claiming agree.
• Removed the unrelated retry-budget schema, migration, release-claim, and fixture changes so this PR has no database migration or manual retry semantic change.

Reviewer Notes

• Stale queued recovery remains independent of the pending created_at window.
• The cron window is intentionally narrow and inclusive: reviews aged 60 through 75 minutes are eligible.
• Direct calls to tryDispatchPendingReviews(owner) still consider all pending reviews.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The only change since the previous review (3afe503) is b9e9973 — a cosmetic fix removing a trailing newline from the generated migration journal. No logic, schema, or application code was modified; all previous findings remain resolved.

Files Reviewed (1 incremental file)

• packages/db/src/migrations/meta/_journal.json — generated file; EOF whitespace fix only, no logic change

---

_{Reviewed by claude-4.6-sonnet-20260217 · 161,279 tokens}

_{Review guidance: REVIEW.md from base branch main}