Publish patch version 5.0.2 for npm release (#40)

This keeps release metadata aligned across package manifests while following the required protected-branch PR flow.

Constraint: Requested sub-branch PR flow into protected main
Rejected: Regenerate lockfile from install | unnecessary churn for a version-only bump
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep package.json and package-lock.json root versions in sync for every release bump
Tested: node -e "const p=require(\"./package.json\"); const l=require(\"./package-lock.json\"); console.log(p.version,l.version,l.packages[\"\"].version)"
Tested: node --test test/fuzzing.test.js (fails)
Not-tested: Full test suite currently blocked by existing fuzzing test failure

Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>

Author: NagyVikt

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@imdeadpool/guardex",
-  "version": "5.0.1",
+  "version": "5.0.2",
   "description": "GuardeX: the Guardian T-Rex for your repo, with hardened multi-agent git guardrails.",
   "license": "MIT",
   "preferGlobal": true,