Update signed manifest to 7.43.0

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.32",
-    "released_at": "2026-08-12T15:26:37+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.32/argus-wordpress-defence-7.23.32.zip",
-    "sha256": "6439eb8b52c3ffec514d73705ea57aa461fcfe2e781bd0c298688697ed0ee2ea",
+    "version": "7.43.0",
+    "released_at": "2026-09-17T12:33:02+00:00",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.43.0/argus-wordpress-defence-7.43.0.zip",
+    "sha256": "cdc118a3fc386a38b376c089bcbb4276a6f6a9cbaa847eb2586320553d4c621d",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Fixed a real bug found on a live production site right after 7.23.31 shipped: the new\n  self-health-check for the scanner and the update mechanism compared timestamps in the wrong\n  format, so it could report \"hasn't run in hours\" / \"hasn't checked in 2 days\" even seconds after\n  they genuinely had. Both are now correctly recognized as healthy when they actually are.",
-    "signature": "XnGoKDoybXWln+XMgRVSYJM+0VMsvXRvJfnoDTf0bCvkLdX5a+Enq2jIMrMouDCrHmp7qp76/0P2tRmA0PidDA=="
+    "summary": "* ARGUS's own automatic updates no longer create a flood of integrity findings for the files that\n  update legitimately changed -- each one is now checked against that exact release's own signed\n  file list, so a genuine ARGUS update stays quiet while anything unexpected (a file that update\n  did not actually add, or one it removed but this version still needs) is still caught and\n  reported, not silently ignored.",
+    "signature": "aS+aCokuI9o+k8CkM9NbifEWrOq+iz1wcRFkiWDIR2T9rGF+Xd47TIJDjKoyS3Ll2nx65uBobTCyr3mlK18KAQ=="
 }