Clear SpeedyCache for a Page Showing Old Content with AI

My WordPress site uses SpeedyCache. Visitors still see old content on [page URL, or several]. Clear SpeedyCache for just those pages.

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. For each URL I gave, say whether it has a cached copy. Where read_file (scope wp-content) can open it (files under 64 KB), read its last line, which says Cache by SpeedyCache at a Unix time, and tell me when it was cached in my site's timezone.
4. Run speedycache-cache/delete-url with urls set to my URLs, all in one call. It answers deleted true even when nothing was cached, so do not take that as proof.
5. List the folder again and confirm those copies are gone. Visitors and the preload can cache a page again within seconds, so for any copy still there, read its last line and check its time is after the clear. If settings/get showed preload true, SpeedyCache queues them to be cached again within a few minutes; otherwise the next visitor's view is stored.
6. Tell me to check in a private window. If the old content is still there and step 3 found no SpeedyCache copy, it comes from a host or CDN cache, or the browser. If what changed is a widget, the Customizer or theme styles, tell me those affect every page and SpeedyCache needs a full clear.