Update signed manifest to 7.23.31

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.17",
+    "version": "7.23.31",
-    "released_at": "2026-08-10T11:36:11+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.17/argus-wordpress-defence-7.23.17.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": "2a5c55fca141a65574818ba553657f26486d3153d159c17a8a9a0182d2ac2621",
+    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Reduced false-positive security findings for recognized WordPress and WooCommerce functionality\n  -- normal, expected WooCommerce cart/storefront activity no longer shows up as a security issue\n  requiring your attention.\n* Findings you resolve or accept no longer reappear on their own within the hour.\n* Added a new \"Automatically Handled\" section on the Findings page, showing what ARGUS verified\n  and handled on its own -- separate from anything you decided yourself.\n* Replaced \"Delete\" with \"Archive\" for findings -- your security history is kept, not destroyed,\n  when you clear something from your queue.\n* Findings actions (Acknowledge, Resolve, Accept Risk, Archive) now show a short explanation of\n  what each one actually means.\n* The Security Score and Findings counts on the dashboard no longer count routine technical\n  inventory as active security issues.\n* An ARGUS Defence update verified through its own signed update process is no longer shown as a\n  file-integrity warning.",
+    "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": "gbC2tegHF/ACYCy+w3apuZxJIcpNyxl2YmNsJUqI95iZD7PYzXC4X+uApNElf9+wzgStXFdEtEBnmIYvrXGxCQ=="
+    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
 }