v3.5.0

Network maintenance purges now use a durable, paced queue instead of immediately clearing every enabled zone. Plugin, theme and core updates share one coalesced maintenance session.

• Defaults: 120 seconds between origin dispatches and between Cloudflare maintenance requests, plus a renewable 180-second quiet period after update activity.
• Update-start hooks pause further stages. New updates revoke older edge readiness and refresh already-processed sites after the session settles.
• Dashboard → Updates offers Hold for updates / Updates finished. Settings show progress, timing, failures and pause/resume/cancel/retry controls.
• Ordinary content edits remain independent. Maintenance uses separate hostname-scoped Cloudflare purges for distinct hosts sharing a zone. Shared-host/subdirectory scopes stop for review; no zone-wide fallback is used.
• WP Engine dispatch remains asynchronous. Passive failure backoff and durable worker recovery do not guarantee origin capacity or completed propagation.
• No object-cache flushing or warm-up crawler. Native WP Engine and Smart Plugin Manager purges remain outside this plugin's control.

Upgrade precaution: disable v3.4.4 automatic-update and external-cache-clear triggers before installation, and review pending broad jobs. The installation request may still run old loaded callbacks. Existing settings are retained; enable the desired triggers after installation with maintenance held, then choose Updates finished when ready.

Validation: PHP lint, regression suites (84 and 63 assertions with a shared baseline), and 226 real local WordPress/MariaDB integration assertions across standalone/multisite with and without Redis. Provider transports were simulated. Release ZIP excludes test harnesses.

Install the attached ZIP or use the GitHub updater. Back up the installed plugin first; a network-activated update affects every site using that installation.