Update signed manifest to 7.23.31

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.24",
+    "version": "7.23.31",
-    "released_at": "2026-08-10T16:35:01+00:00",
+    "released_at": "2026-08-12T15:21:11+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.24/argus-wordpress-defence-7.23.24.zip",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.31/argus-wordpress-defence-7.23.31.zip",
-    "sha256": "214f60979904ab584960705d8713561fafa9ec6d1a61d0aa7cd8493375992644",
+    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Clarified what's included without an active trial or license: core protection (firewall, ban\n  engine, malware/integrity scanning, quarantine) always keeps running and WordPress is never\n  disabled. On this Base tier, the Findings page, the ANIS Global Threat Network connection, and\n  automatic scheduled backups require a trial or license; automatic scanning runs weekly instead\n  of hourly (manual scans and backups are always available regardless).\n* The License page has been redesigned: a countdown ring shows days remaining and your exact\n  expiration date, and a new \"What's Included\" table shows exactly what each tier includes, with\n  quick-jump links to every section.\n* Fixed: a file change made by a normal WordPress, plugin, theme, or ARGUS update could sometimes\n  be left flagged as an unresolved suspicious-file finding instead of being automatically resolved\n  like other update-related changes.\n* Scheduled backups now pace themselves to avoid competing with normal site traffic.",
+    "summary": "* Fixed: right after ARGUS checked for updates, its own health check could momentarily read that\n  timestamp before it was refreshed and report \"hasn't checked for updates\" -- the two checks now\n  run in the correct order.\n* The health-check findings for scanner/update/intelligence timing now explain the most common\n  real cause specifically -- WordPress's own scheduled-task system (WP-Cron) not firing reliably,\n  common on low-traffic sites or hosts without a real system cron configured -- instead of a\n  generic \"contact support.\"",
-    "signature": "xRiE+VPzHll2DTq5nhKY1WDu5YwENziSynwwYI5Jp/HitJ07lyF4sLfIIRgPOCDOCf/GO5L9bJ5vz5Ol96OOAQ=="
+    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
 }