Update signed manifest to 7.23.31

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.27",
+    "version": "7.23.31",
-    "released_at": "2026-08-10T20:18:36+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.27/argus-wordpress-defence-7.23.27.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": "6a0a76fe0d3a366b1df62fc351841f91f8e52f19aacbe032a911ca4f0eaeffcb",
+    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Reverted the dashboard's visual redesign (sidebar navigation, larger ring cards) back to the\n  familiar layout while keeping the real fixes that came with it:\n  - The dashboard no longer scrolls the whole WordPress admin page -- the ARGUS header and\n    navigation stay in place while only the dashboard content scrolls.\n  - An active Premium license no longer shows \"0 days left\" next to a correct future renewal\n    date.\n  - The Blocked Requests chart's hover tooltip no longer fails on the most recent data point and\n    no longer renders off-screen near the chart's edge.\n  - IPs Tracked, ANIS Protections, and Global Network cards explain what a \"0\" means (not\n    connected, still connecting, or genuinely clean) instead of showing a bare number, and the\n    Global Network panel now shows correct instance/indicator/feed numbers instead of always\n    showing 0.",
+    "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": "ZSRLTPI5fTv0f81GbB58HCxRYt2QhQSWUZUFVfdeK96zLJ0cGKmbDLC/94sz7HePQqAP1cTKiQFIdghYPhS6Aw=="
+    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
 }