WebUI: operator-friendly schedule editor (replaces raw cron)

[lonix]

Problem

Three config keys today store raw cron strings:

• voicetracking.announcements.schedule (default "0 16 * * 5")
• voicetracking.cleanup.schedule (default "0 0 * * *")
• leaderboard_roles.update_cron (default "0 0 * * 1")

Raw cron is power-user-only. The vast majority of real operator intents — "Friday at 4pm", "every night at midnight", "Mondays at midnight" — can be expressed as (frequency, time-of-day, day). Exposing cron syntax in the admin panel is a discoverability and accuracy hazard for the same audience #436 / #439 is targeting with human labels and dropdowns.

Proposed change

• Add a cron type discriminator to SettingMetadata (lands naturally next to the type field proposed in WebUI: dropdown selectors for channel/category/role config keys (replace freetext) #439).
• Renderer for cron type shows three controls:
  • Frequency dropdown: daily | weekly | monthly | custom.
  • Time of day picker: HH:MM.
  • Day picker: weekday for weekly, day-of-month for monthly, hidden for daily.
• Saving converts the picker values to a cron string and stores the existing format unchanged — no schema migration, the backend still receives 0 16 * * 5.
• Picking custom reveals a raw cron text input as an escape hatch for power users.
• When loading an existing value, parse the stored cron and reverse-engineer the picker state; unknown patterns fall back to custom.

Acceptance

• All three schedule keys render as the friendly picker by default.
• A round-trip (save → reload page) reproduces the same picker state.
• Picking custom and entering a raw cron string still works.
• Existing cron values in the DB read correctly into the picker.

Notes

• Depends on WebUI: human-readable labels and section titles/descriptors in Settings #436 / WebUI: dropdown selectors for channel/category/role config keys (replace freetext) #439 for the per-key type mechanism.

[lonix]

👍 Upvote — this is the highest-value/lowest-effort feature improvement in the current backlog.

Raw cron strings ("0 16 * * 5") are completely opaque to the non-developer operators this bot targets. They are the single most error-prone setting in the WebUI today: a mistyped cron silently breaks scheduled announcements or cleanup jobs with no feedback until the window passes.

A simple dropdown-based editor (e.g. "Every Friday at 4 PM" → day-of-week + time pickers) would:

1. Eliminate the most common misconfiguration class with zero additional documentation.
2. Reuse the existing validCron / normalizeCron helpers already in write-routes.ts — the server-side validation path needs no changes, just a nicer front-end input.
3. Scope is well-contained: only three keys are affected (voicetracking.announcements.schedule, voicetracking.cleanup.schedule, polls.cleanup_schedule), and only their renderSettingInput slots in the Settings page need a widget swap.

Compared to other open features this is a small client-side widget change with outsized UX impact.

---

Generated by Claude Code