Update signed manifest to 7.23.31

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.28",
-    "released_at": "2026-08-10T22:09:39+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.28/argus-wordpress-defence-7.23.28.zip",
-    "sha256": "4c2b238947032bb65f7373ef712bb13f44a6f5c2d46528aefa219b2f22054eda",
+    "version": "7.23.31",
+    "released_at": "2026-08-12T15:21:11+00:00",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.31/argus-wordpress-defence-7.23.31.zip",
+    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Redesigned the Overview page to be understandable at a glance, whether or not you know anything\n  about website security: a single \"Your website is protected\" summary explains what's happening\n  and whether you need to do anything, your protection score now explains itself (\"Why is my score\n  X?\"), findings are shown in plain language instead of technical rule names, and ARGUS can turn\n  your firewall back on for you with one click if it's ever off.\n* The Firewall page's Rule Activity and Blocked IPs tables now lead with plain language (what was\n  detected, how it was handled) instead of raw internal rule/ban codes -- the technical detail is\n  still there behind a \"Technical details\" toggle for anyone who wants it.\n* Settings is now organized into Protection, Automatic Protection, Account, and Advanced sections\n  instead of one long list of unrelated panels.\n* Calmed down the visual style throughout -- removed constant pulsing/glowing effects on routine,\n  everything-is-fine status indicators; motion is now reserved for things that actually need your\n  attention.",
-    "signature": "xfwlvA9lrR3LqV8H3ETm8HyCWXOUGSaDyfDarvfZ+6z7MblYO9pWzoYFnPcubrHeC4bKn5n1nWbF47/QE/PlCA=="
+    "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=="
 }