Get a SpeedyCache Health Check with AI

My WordPress site uses SpeedyCache. Give me a health check of my cache setup without changing anything.

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. Do not use speedycache-cache/get-stats either: on the free plugin it returns 0 or a stale count.
2. Run speedycache-settings/get, speedycache-file/get, speedycache-excludes/list and speedycache-preload/status, and run_wp_cli plugin list --status=active.
3. Check, and explain each in a sentence without jargon:
- cache_enabled false means no new pages are cached: fix now, on the Cache tab. Also run run_wp_cli config get WP_CACHE: if it is not true, WordPress never loads SpeedyCache's serving code, so pages are stored but (on nginx and most hosts) never served. Fix now: wp-config.php was probably not writable when SpeedyCache was activated; turning the cache off and on again on the Cache tab retries, or my host can add define WP_CACHE true.
- mobile true is Mobile Override, which stops phone and tablet visitors from getting the desktop cached copy. Without Mobile Cache (mobile_theme, a SpeedyCache Pro feature) they get no cached pages at all. If my theme is responsive (most current themes are), turning Mobile Override off on the Cache tab lets them use the same cached pages: worth doing, and I should check the site on a phone after.
- logged_in_user true means logged-in visitors get the logged-out cached copy. On a shop, membership, course or community site (check the active plugins) that is fix now, because members would see logged-out pages; on a plain blog it is fine.
- purge_interval and purge_interval_unit are the Cache Lifespan; 0 means cached pages never expire on a schedule. Say what it is set to.
- preload false means pages are cached only when someone visits: worth turning on for most sites, on the Cache tab.
- File optimization: list what file/get shows on. Options marked Premium in SpeedyCache's settings do nothing without SpeedyCache Pro, even if file/get shows them true. Say combine_js is the one most likely to break menus, sliders or forms, so if any part of the site misbehaves it is the first to switch off on the File Optimization tab. Do not call it a problem on its own.
4. Pages that should not be cached: list published pages with rest_api GET /wp/v2/pages, status publish, per_page 100, paging until there are no more. Pick out login, account, registration, profile, dashboard and checkout-style pages that are not WooCommerce's (SpeedyCache already skips WooCommerce cart, checkout and My Account pages). 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. Any of these pages with a cached copy is fix now, whatever the exclude rules say: a cached form or login page can stop working, and a member area can show the wrong page. Exclude rules only stop SpeedyCache from storing a page; a copy stored before the rule keeps being served. Tell me to add a page rule for it with Add New Rule on SpeedyCache's Excludes tab, choosing the Post ID or starts-with kind (an exact-URL rule misses links with tracking tags such as utm_source, and that copy is then served to everyone), and then clear that page, which you can do with speedycache-cache/delete-url when I ask.
5. Exclude rules: explain each page, cookie and user agent rule from speedycache-excludes/list in plain words (css and js rules are for file optimization and do not affect page caching). Tell me cookie and user agent rules only stop a visitor's view being stored; they do not stop those visitors getting a page someone else's visit stored. A cookie rule with empty text (such as SpeedyCache's has Woocommerce Items in Cart rule) matches every visitor who has any cookie, so most real visits are never stored and the cache fills mainly from preload: worth knowing, not a fault. Flag a page rule with the post prefix: it does nothing in SpeedyCache. Flag a startwith rule whose text starts with a slash: it never matches. For startwith, contain and exact rules, check the text against my published posts', pages' and products' paths and flag any that match nothing.
6. Tell me how many pages are cached now.
7. Group the findings into fix now, worth doing, and fine to ignore. For each, say what to change and on which SpeedyCache tab. Change nothing.