Update signed manifest to 7.41.0

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.41.0",
+    "released_at": "2026-09-17T11:36:03+00:00",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.41.0/argus-wordpress-defence-7.41.0.zip",
+    "sha256": "311dacbd64a9604dba16de4329203899dd5a85aac0f0e78ea5670e2123069958",
     "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": "* Findings now have a complete lifecycle: Resolve, Reopen, Accept Risk, False Positive/Suppress,\n  Archive and Restore are all real, tracked actions (who did it, when, and why), available here in\n  wp-admin and, if this site is connected to a WAD account, from there too -- WAD is never a\n  separate copy of this data, every action there is carried out on this site the same way.\n* Contact Form 7's public feedback submission endpoint is now correctly recognised as an\n  intentional, documented part of that plugin's own public API, the same way WooCommerce's Store\n  API and Jetpack's public endpoints already were -- it no longer creates an unnecessary finding.",
+    "signature": "ebCSGFVp8NzohM7F8+os2MaNT67iyaYxNaxeKSrj+utKUL3qF30VF7qy69wvyBicttrKvtlqcbzhl53QBlMRCQ=="
 }