Update signed manifest to 7.41.0

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.24",
-    "released_at": "2026-08-10T16:35:01+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.24/argus-wordpress-defence-7.23.24.zip",
-    "sha256": "214f60979904ab584960705d8713561fafa9ec6d1a61d0aa7cd8493375992644",
+    "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": "* Clarified what's included without an active trial or license: core protection (firewall, ban\n  engine, malware/integrity scanning, quarantine) always keeps running and WordPress is never\n  disabled. On this Base tier, the Findings page, the ANIS Global Threat Network connection, and\n  automatic scheduled backups require a trial or license; automatic scanning runs weekly instead\n  of hourly (manual scans and backups are always available regardless).\n* The License page has been redesigned: a countdown ring shows days remaining and your exact\n  expiration date, and a new \"What's Included\" table shows exactly what each tier includes, with\n  quick-jump links to every section.\n* Fixed: a file change made by a normal WordPress, plugin, theme, or ARGUS update could sometimes\n  be left flagged as an unresolved suspicious-file finding instead of being automatically resolved\n  like other update-related changes.\n* Scheduled backups now pace themselves to avoid competing with normal site traffic.",
-    "signature": "xRiE+VPzHll2DTq5nhKY1WDu5YwENziSynwwYI5Jp/HitJ07lyF4sLfIIRgPOCDOCf/GO5L9bJ5vz5Ol96OOAQ=="
+    "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=="
 }