Closes feature integration finding F20-01. Catch-up now processes every unclaimed fire time inside 24 hours, oldest first, including both America/Chicago 01:30 periods across the 2026 spring-forward. Does not merge pull request #182.
Maestro task e20ecd4b-696c-43c5-8b46-31208edf0568.
Closes feature integration finding F20-01. Catch-up now processes every unclaimed fire time inside 24 hours, oldest first, including both America/Chicago 01:30 periods across the 2026 spring-forward. Does not merge pull request #182.
Head: 1f11f3574a7beb0d748198cbde1ea222e404bc63.
Catch-up handled only each schedule's most recent fire time, so an
earlier unclaimed period still within CatchUpWindow was skipped for
good. Across the Chicago spring-forward change, 01:30 on 8 March and
01:30 on 9 March 2026 are 23 hours apart; booting at 9 March 01:35 ran
only 9 March.
The scheduler now handles, in time order, every fire time after done
that passed within CatchUpWindow, plus the most recent one even when it
is older (recorded as missed, as before). Each period keeps its own
claim; a failed claim stops that schedule's queue and is retried in
order. Older fire times are still never looked at.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Maestro task e20ecd4b-696c-43c5-8b46-31208edf0568.
Closes feature integration finding F20-01. Catch-up now processes every unclaimed fire time inside 24 hours, oldest first, including both America/Chicago 01:30 periods across the 2026 spring-forward. Does not merge pull request #182.
Head:
1f11f3574a.Independent Codex gpt-6-sol review: APPROVED for this exact commit.