GPT-5 finding
Non-standard cron step syntax '1/N' used; schedules may not parse or fire
mediumbugmedium
- aeon.yml:113
- aeon.yml:147
In most cron implementations and common libraries, step values are supported as '*/N' or 'A-B/N'. Using '1/N' without an explicit range is non-standard and is often rejected by parsers (e.g., croniter, node-cron, Vixie cron style). If the scheduler follows standard parsing, these entries may never run or cause parse errors when enabled.
Recommendation
Replace '1/2' with '*/2' or '1-31/2' for day-of-month steps: self-improve: "0 18 */2 * *". Replace '1/7' with '*/7' or '1-31/7': smithery-manifest: "0 6 */7 * *". Prefer testing these with the actual Aeon scheduler to confirm acceptance.