Update signed manifest to 7.23.30

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.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",
     "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": "* 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=="
 }