Update signed manifest to 7.23.31

manifest.json

@@ -1,10 +1,11 @@
 {
-    "version": "7.23.2",
+    "version": "7.23.31",
-    "released_at": "2026-08-09T19:38:39+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.2/argus-wordpress-defence-7.23.2.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": "38edd77d2dbcd63597ef915cfa731377603c86e9d87cee92e8b966792900fdfb",
+    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "signature": "cSeceevolR+2D+Z/+6msRQfAkQU6yd8QMWZ32SrnEYCSbD5V3vX4+vCB/WVoSW3ZlB3PIsygr67Qq5L1pKn6DA=="
+    "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": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
 }