Update signed manifest to 7.23.31

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.16",
+    "version": "7.23.31",
-    "released_at": "2026-08-10T11:08:03+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.16/argus-wordpress-defence-7.23.16.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": "08e3f53858885dc34bea9ca62396b3a343e146ae9310994f0eb84ec2b70107b5",
+    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Vulnerability checking now also runs immediately whenever a plugin or theme is installed or\n  updated (when connected to ARGUS Cloud), instead of only on the regular hourly schedule -- so you\n  find out right away if something you just installed has a known issue. The regular hourly check\n  continues to run as before for everything else.",
+    "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": "cGe/Vc4NAWalUjkDueEw73IDsSWmEtdBsW7ppx8h+V8tStLgfxJ/KH1Kp2lIqqYF5A9EKDV8uUOXXYv4wIHDBQ=="
+    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
 }