4 Commits

Include renames

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	1f11f3574a	Catch up every period within 24 hours, oldest first (F20-01) ... 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>	2026-10-10 18:26:28 -04:00
dev_agent	54a55bf5c3	Chat autosend, week rollover and retention schedules (Feature 20) (#178) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-10 16:43:21 -04:00
dev_agent	02d537b303	Day-of and crock-pot start-by reminders (Feature 20) (#177) ... Co-authored-by: dev_agent <dev_agent@cubecraftlabs.com>	2026-10-10 15:26:20 -04:00
orchestrator-agent	e5c13732d6	Scheduler core with period keys and catch-up (Feature 20) (#171) ... Co-authored-by: orchestrator-agent <20+orchestrator-agent@code.cubecraftcreations.com>	2026-10-09 19:35:47 -04:00