WPPilot 1.18.5 — Safe updates that survive cache purges, and a site issues log

• New: wppilot/site-issues, a read-only log of what went wrong on the site. WordPress's fatal error handler now records the error behind "There has been a critical error on this website" - type, the message's first line, the file relative to the WordPress root and the line, the plugin or theme it belongs to, the request path without its query string, a count and first/last seen - in a capped, non-autoloaded log of 50 entries. Out-of-memory and timeout fatals are not blamed on the file PHP happened to stop in. The ability reads that log with the plugins and themes WordPress paused in recovery mode, failed backups and the updates WPPilot Pro's safe update rolled back. Query strings, cookies, stack traces and server paths are never stored.
• New: WPPilot Cloud hears about changes within seconds instead of at the next hourly check-in: a finished or failed backup (UpdraftPlus, BackWPup, Duplicator), a core, plugin or theme update (safe updates included), a plugin or theme installed, activated, deactivated, deleted or switched, and a Site Kit connection change each send the same signed check-in from WordPress cron, at most once every 30 seconds and never during a visitor's page load.
• Changed: cloud/status sends a compact issues summary - counts, when the newest fatal was, and the newest ten issues with relative file paths only - so WPPilot Cloud can show an Issues log per site.
• Fixed: wppilot/pagespeed-check offered Site Kit dashboard sharing to a module owner whose Google sign-in was gone, which Site Kit refuses. It now skips Site Kit with site_kit_owner_signed_out and returns a sign-in fix that links to Site Kit > Dashboard.