Update signed manifest to 7.23.31

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.30",
-    "released_at": "2026-08-12T13:24:00+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.30/argus-wordpress-defence-7.23.30.zip",
-    "sha256": "81751849589995c4830915bb28a1b7983063571cfd3d728cac98457294e74703",
+    "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": "* Findings quality: routine, expected activity from legitimate plugins (like WooCommerce's cart/\n  checkout endpoints and Jetpack's public API) no longer shows up as a security issue just because\n  it doesn't require login -- ARGUS now recognizes it as normal.\n* Fixed a real false-positive: a legitimate WordPress core update could previously be flagged as a\n  suspicious file appearing or disappearing inside WordPress core. It's now correctly recognized as\n  an expected part of the update.\n* Fixed: repeated attacks matching the same firewall rule from different sources no longer create a\n  growing pile of near-identical findings -- they're now tracked as one finding with an occurrence\n  count, so your Findings list stays readable.\n* Fixed: a vulnerability finding (including \"WordPress core is out of date\") now automatically\n  clears itself once you actually update the affected plugin, theme, or WordPress core -- it no\n  longer stays open forever, or gets duplicated every time a newer version comes out.\n* Each finding now shows how confident ARGUS actually is (Confirmed, High confidence, Likely,\n  Suspicious, or Informational), so it's clear what's been verified versus what's an inference.\n* \"Resolve All Open\" is now \"Archive All Open\" -- same one-click way to clear your queue, but it no\n  longer implies everything was fixed; archived findings stay fully available in your history.\n* ARGUS now periodically checks its own health in the background (its files, database, scanner,\n  firewall, quarantine storage, and update mechanism) and can fix common problems automatically;\n  if something stays broken, you'll see it as a finding until it's verified resolved.\n* Two-factor authentication data is now fully removed when you uninstall the plugin.\n* Backups page: new charts showing your backup success/failure history and size trend over time.\n* License page: \"What's Included\" is now a simple, readable list instead of a dense table.",
-    "signature": "6p5dKzyfdivTHNN9qeMBQVVM9V3kb/fMWdTDvSj81Bp5wLuxOc/nVHerdoU2NMIleLjlhKGzQwpvt75shnabDw=="
+    "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=="
 }