One-shot CronCreate silently accepts past times — rolls to next year, never fires, and CronList hides the year

Repro (observed 2026-07-09): a one-shot cron created at 6:49am targeting 6:24am the same day was accepted without warning. The scheduler resolves "next cron occurrence after creation," so a past time rolls to the same date NEXT YEAR. The job can never meaningfully fire, never auto-deletes, and CronList renders its fire time without the year — so it displays as if it were live and imminent. The failure is fully silent at create time and invisible in the list.

Ask: (1) reject or loudly warn when a one-shot resolves to a fire time materially in the future relative to the obvious intent (e.g. >6 months out from a time-of-day spec), and (2) include the year in CronList output so a rolled-over job is visibly dead.