Update signed manifest to 7.23.33

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.31",
-    "released_at": "2026-08-12T15:21:11+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",
-    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
+    "version": "7.23.33",
+    "released_at": "2026-08-12T15:28:04+00:00",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.33/argus-wordpress-defence-7.23.33.zip",
+    "sha256": "4be6cc692fa04349748e9ce8cb2fc977973210f066288dbf9c94a73235ac858e",
     "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.\"",
-    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
+    "summary": "* The self-check findings for scanner/update timing now use simpler, calmer wording instead of\n  naming internal technical details -- they explain that it's usually temporary and clears on its\n  own, with a clear next step if it doesn't.",
+    "signature": "+8/j7Bc9BNUlTrUp7wqaT0rX+HhJKLP817notyt2w8T/x+sP044NErvK1Wnv5ELLGS8zIeT9FFz1YyOnVS/xDQ=="
 }