Clear and Warm Up Your SpeedyCache Cache with AI

My WordPress site uses SpeedyCache. I changed [a widget, a Customizer setting, my theme styles or a plugin setting] and visitors still see the old version. Clear the whole SpeedyCache cache and warm it back up.

1. Run discover_abilities with category speedycache-cache. If speedycache-cache/delete-url is not there, run rest_api GET /wp/v2/plugins with search speedycache. If SpeedyCache is active, tell me its AI abilities are off until I turn on Enable AI Abilities on SpeedyCache's AI Abilities page in wp-admin (the MCP Adapter and Application Password steps on that page are not needed for WPVibe; if it is already on, the site needs SpeedyCache 1.4.3 or newer and WordPress 6.9 or newer), and stop. If it is installed but not active, tell me to activate it and then turn on that switch, and stop. If it is not installed, tell me this recipe is for the free SpeedyCache plugin, and stop. Never run speedycache-cdn/get or speedycache-import/export, and never read the speedycache_cdn or speedycache_object_cache options any other way: they hold my CDN API key and object cache login in full.
2. Run speedycache-settings/get. If cache_enabled is false, SpeedyCache is not storing or (on nginx) serving copies. On Apache hosts its .htaccess rules keep serving copies already stored, even with the cache off, so still check the folder in the next step. If copies exist, tell me they only matter on an Apache host, and offer to clear them with speedycache-cache/delete-all; tell me first that clearing everything also makes SpeedyCache ask Varnish to clear when purge_varnish is true, and Bunny or Cloudflare when its own CDN setting is on (for Cloudflare that is the whole zone). Wait for my yes. If there are none, tell me the old content comes from somewhere else (a host or CDN cache, or the browser) and stop.
3. SpeedyCache keeps each cached page as an index.html file at wp-content/cache/speedycache/HOST/all/PATH/index.html (the home page is all/index.html). First run list_files with scope wp-content and directory cache/speedycache to find the HOST folder, then list HOST/all. Count only index.html files as cached pages (ignore .gz copies; some folders, such as category or date paths, hold no page of their own). If the all folder does not exist, nothing is cached. Count the cached pages before you clear.
4. Tell me what you will clear, and that clearing everything also makes SpeedyCache ask Varnish to clear when purge_varnish is true, and Bunny or Cloudflare when its own CDN setting is on (for Cloudflare that is the whole zone). Wait for my yes. Then run speedycache-cache/delete-all once with no options. Do not clear the minified CSS and JavaScript files: SpeedyCache names them by their content, so a change already makes new ones, and deleting the old ones can break styling on copies a host cache or CDN still holds.
5. List cache/speedycache/HOST again and confirm the all folder is gone or holds far fewer index.html files. Visitors and a running preload can cache a page again within seconds, so for any copy still there, read its last line with read_file (files under 64 KB) and check its time is after the clear.
6. Skip this step if cache_enabled is false. Run speedycache-preload/build, then speedycache-preload/status, and tell me how many URLs are queued: the home page and up to about 90 of the newest posts, pages and products. WordPress cron caches about 10 a minute while the site gets visits. Run preload/status and list the folder again in a couple of minutes to show me it is moving.
7. Tell me to check the change in a private window. If it still shows the old version, a host cache or CDN that SpeedyCache does not manage is the next thing to clear.