Repair ambiguous weekday routine cron handling

[LoganYe]

Summary

• repair ambiguous weekday cron handling for scheduled run_task routines
• normalize clear Monday-Friday requests to use unambiguous MON-FRI cron fields during scheduler action create/reschedule
• conservatively repair legacy stored cron routines when the original thread_request.md clearly asked for weekday execution
• document the scheduler weekday parser caveat so future generated routines avoid ambiguous numeric weekday ranges

Root Cause

The scheduler cron parser does not behave like common Unix cron numeric weekday conventions. Legacy weekday schedules encoded with numeric weekday ranges such as 1-5 could execute as Sunday-Thursday, which is why Work could show 4/5 while the confirmation email said the routine should start on 4/3.

Testing

• cargo fmt --all --manifest-path DoWhiz_service/Cargo.toml
• cargo test --manifest-path DoWhiz_service/Cargo.toml -p scheduler_module --lib resolve_schedule_request_with_context_
• cargo test --manifest-path DoWhiz_service/Cargo.toml -p scheduler_module --lib maybe_repair_legacy_weekday_cron_task_uses_thread_request_context

Notes

• No frontend screenshots: this change is scheduler/backend logic plus scheduler skill documentation.
• Existing legacy routines are only auto-repaired when their workspace still has request context that clearly indicates a weekday cadence.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dowhiz	Ready	Preview, Comment	Apr 3, 2026 2:45am