Update signed manifest to 7.43.0

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.31",
+    "version": "7.43.0",
-    "released_at": "2026-08-12T15:21:11+00:00",
+    "released_at": "2026-09-17T12:33:02+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.31/argus-wordpress-defence-7.23.31.zip",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.43.0/argus-wordpress-defence-7.43.0.zip",
-    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
+    "sha256": "cdc118a3fc386a38b376c089bcbb4276a6f6a9cbaa847eb2586320553d4c621d",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Fixed: right after ARGUS checked for updates, its own health check could momentarily read that\n  timestamp before it was refreshed and report \"hasn't checked for updates\" -- the two checks now\n  run in the correct order.\n* The health-check findings for scanner/update/intelligence timing now explain the most common\n  real cause specifically -- WordPress's own scheduled-task system (WP-Cron) not firing reliably,\n  common on low-traffic sites or hosts without a real system cron configured -- instead of a\n  generic \"contact support.\"",
+    "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": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
+    "signature": "aS+aCokuI9o+k8CkM9NbifEWrOq+iz1wcRFkiWDIR2T9rGF+Xd47TIJDjKoyS3Ll2nx65uBobTCyr3mlK18KAQ=="
 }