claude
2dbf476c45
RescheduleReminder walked the cron schedule on a UTC instant, and robfig's Next walks the calendar in the location it is handed. So '0 9 * * *' created for 09:00 Moscow rescheduled to the next 09:00 UTC, which is noon the same day: the reminder fired again that afternoon and every day at noon after. The same offset walk moved it an hour across a DST changeover. The walk runs in the owner's location now. Worse and quieter: any outage longer than one period killed the recurrence for good. next is the occurrence after the last fire, so next.Before(now) marked a daily reminder fired when the daemon was down overnight. Past occurrences roll forward to the first one after now, with no backlog replay, matching routine.DueAccepted. internal/routine is clean. Its IntervalDays*24h is an elapsed measure rather than a wall clock, so the hour arithmetic is right there. (V-616)