Update signed manifest to 7.23.36

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.31",
+    "version": "7.23.36",
-    "released_at": "2026-08-12T15:21:11+00:00",
+    "released_at": "2026-08-12T15:43:51+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.23.36/argus-wordpress-defence-7.23.36.zip",
-    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
+    "sha256": "574fc990930b0f7c1d24c861dce0e7a50bfe66980bcb972b5e1dc8b62168a3f9",
     "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": "* Fixed a real gap found via a direct customer report: \"Automatic Security Updates\" kept your\n  plugins and themes current, but not WordPress core itself -- a core security/point release could\n  sit unapplied. It's now included too (major version upgrades are never forced automatically --\n  you stay in control of those).",
-    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
+    "signature": "lXhdvdDgG6WFs7jaf48yiIPTSfDILuUdFaabL0Jykye4zTlH35eliTeAEZKTmdmXulonjnKwhP4dKLfaZppsDw=="
 }