[helpcodeai]

Summary

The onboarding and trial cron on Cloud ran twice: once from the systemd timer on the droplet (anythingmcp-onboarding-cron.timer, hourly) and again from this workflow's hourly schedule. The endpoint is idempotent, so no email went out twice. But every pass examined about 11,000 users twice, 3 to 7 minutes each time, and on 11-04 the GitHub runs added passes at 23:24 and 05:47.

Changes

• onboarding-reminders.yml drops its schedule. It keeps workflow_dispatch as a manual fallback, for example if the droplet timer stops.
• The header comment says where the hourly run comes from now.

Type

• Other: CI/scheduling

Testing

• No tests needed: workflow trigger only.
• The YAML parses with js-yaml.
• On the droplet, the timer is active and hourly: last run 09:17:38 UTC, HTTP 201, "examined":10916, next run 10:17 UTC.

Checklist

• My code follows the existing code style
• I have tested my changes locally
• I have updated documentation (if applicable): the workflow header
• All existing tests pass
• This PR has a descriptive title

Related Issues

Daily check 2026-11-05 (two schedulers for the onboarding cron). Matteo asked to remove the GitHub schedule.

Deployment: Cloud only; self-hosted doesn't use this workflow. Nothing to deploy: it takes effect when merged.