Update signed manifest to 7.41.0

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.17",
-    "released_at": "2026-08-10T11:36: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",
-    "sha256": "2a5c55fca141a65574818ba553657f26486d3153d159c17a8a9a0182d2ac2621",
+    "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": "* 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.",
-    "signature": "gbC2tegHF/ACYCy+w3apuZxJIcpNyxl2YmNsJUqI95iZD7PYzXC4X+uApNElf9+wzgStXFdEtEBnmIYvrXGxCQ=="
+    "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=="
 }