Update signed manifest to 7.23.31

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.25",
+    "version": "7.23.31",
-    "released_at": "2026-08-10T19:23:48+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.25/argus-wordpress-defence-7.23.25.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": "3c9d7710933628296894f5c84d91ecf4d7cbc33d8cf5dd8aaec54e99342d390a",
+    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Redesigned the entire admin dashboard to match the rest of the ARGUS product family: a\n  persistent navigation sidebar with a status bar (protection state, version, notifications,\n  account) above it, replacing the old horizontal tab bar. Your normal WordPress admin menu is\n  untouched -- this lives alongside it, not instead of it.\n* The Overview page has been rebuilt around ring-style stat cards with trend sparklines, an\n  hoverable blocked-requests chart with an exact-value tooltip, a Global Network card summarizing\n  your ARGUS Cloud connection, and Top Threat Types / Top Blocked IPs / Recent Activity at a\n  glance -- all real data, nothing decorative implies a number that isn't actually tracked.\n* Every other page (Firewall, Threats, Findings, Scanner, Quarantine, Cache & Performance,\n  Backups, Vulnerabilities, Intelligence, ANIS, Audit Log, MFA, License, Settings) now shares the\n  same navigation and visual language.",
+    "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": "khoqK1dJ+YAZ4D/IC3OgqTqcpI1GPTtKvuAvEHB3S0SjpRLcXUb+mPh3cvEQSAswOI4iu3mpocsb81cSkUnRDA=="
+    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
 }