Monitoring worker setup

1. Domain ownership is verified once per domain. Use TXT or CNAME at _errornotifier-challenge.<domain>, or run the JavaScript SDK with a project key on the site.
2. Monitors wait in pending DNS verification until their domain proof succeeds.
3. Website tests support GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, custom safe headers, and request bodies for POST, PUT, PATCH, and DELETE.
4. Use WP-CLI for production checks: wp errornotifier run-checks --limit=50.
5. Use WP-CLI for due alert digests: wp errornotifier dispatch-alerts. Email digests send through the configured Mailgun HTTP API and are batched by each channel max email frequency.
6. Use WP-CLI for queued DNS proof checks: wp errornotifier verify-domains --limit=50.
7. Windows Task Scheduler can call studio wp or wp-cli every minute with the site --path.
8. Linux cron should call the monitor worker and alert worker every minute, for example wp errornotifier run-checks --limit=50 followed by wp errornotifier dispatch-alerts.
9. Cloudflare Worker probes are not shipped as a standalone package in this repository; use the current WP-CLI worker model unless an Enterprise private-probe deployment is explicitly arranged.
10. WP-Cron is registered as a fallback only; do not rely on page views for production monitoring.
11. Cleanup command: wp errornotifier cleanup.

Manual check: wp errornotifier check-site 123