Action Scheduler is no longer bundled — it is now an optional dependency.
Why: the official Plugin Check reported 312 errors against the bundled copy of Action Scheduler. None of them were our code, but all of them counted against this plugin — and we only ever called into that library in 13 places. It also dragged the whole package to GPLv3.
What changed
- If another plugin already provides Action Scheduler (WooCommerce and many others do), it is used exactly as before.
- If not, the plugin falls back to WordPress's own cron. Nothing is lost — it is just slower, and both the settings screen and the readme say so plainly.
- Package: 492 KB → 137 KB. Licence: back to MIT.
- Plugin Check, full scan with no exclusions: 0 errors.
Upgrading from 1.1.0: queued actions left behind by the bundled scheduler are cleaned up automatically. WordPress does not run deactivation hooks during a plugin update, so this is handled by a migration instead — without it, those orphans could have resurrected later and repeated paid AI calls.