Advance Guardex to a fresh npm patch (#425)

The npm registry and repo were both at 7.0.35, so the latest merged branch-finish fix needs a new package version before it can publish without colliding with the existing package.

This bumps package metadata to 7.0.36 and records the matching README release-note entry.

Constraint: Version bumps in this repo must keep package.json, package-lock.json, and README release notes aligned.

Rejected: Reuse 7.0.35 | npm already serves that version.

Confidence: high

Scope-risk: narrow

Tested: npm view @imdeadpool/guardex version; node -p package/lock versions; node --test --test-name-pattern 'README release notes include current package version|package manifest pins runtime' test/metadata.test.js; npm pack --dry-run; git diff --check

Not-tested: npm publish

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

Author: NagyVikt

README.md

@@ -266,6 +266,11 @@ Being honest about where this still has issues:
 <details open>
 <summary><strong>v7.x</strong></summary>
 
+### v7.0.36
+- Bumped `@imdeadpool/guardex` from `7.0.35` to `7.0.36` so the latest
+  branch-finish cwd-prune fix can ship under a fresh npm version after PR #424.
+- No new CLI command surface is introduced in this release lane.
+
 ### v7.0.35
 - Bumped `@imdeadpool/guardex` from `7.0.34` to `7.0.35` so the current
   merged `main` payload can publish on a fresh npm version after PR #420.

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@imdeadpool/guardex",
-  "version": "7.0.35",
+  "version": "7.0.36",
   "description": "Guardian T-Rex for your multi-agent repo. Isolated worktrees, file locks, and PR-only merges stop parallel Codex & Claude agents from overwriting each other's work. Auto-wires Oh My Codex, Oh My Claude, OpenSpec, and Caveman.",
   "license": "MIT",
   "preferGlobal": true,