Unblock the next Guardex npm release

README.md

@@ -645,6 +645,12 @@ npm pack --dry-run
 <details>
 <summary><strong>v7.x</strong></summary>
 
+### v7.0.20
+- The VS Code Active Agents tree now exposes worktree-owned SCM changes and lock ownership directly, so operators can see which sandbox owns a dirty file before they act.
+- Guardex now keeps merged cleanup evidence truthful by recording final cleanup proof only after the merge and cleanup state is actually available.
+- Install-surface verification cleanup on `main` is easier to maintain without changing the shipped CLI surface.
+- Bumped the release from `7.0.19` → `7.0.20` so the shipped Active Agents visibility and cleanup-evidence refinements land on a fresh publishable npm version.
+
 ### v7.0.19
 - `gx setup` and `gx doctor` now accept targeted managed-file recovery after `--force`, so `gx doctor --force scripts/review-bot-watch.sh` repairs the named managed file instead of failing on an unknown argument.
 - Managed-file conflict output now teaches both recovery forms directly: `--force <managed-path>` for one file and plain `--force` for whole-surface rewrites.

openspec/changes/agent-codex-release-guardex-7-0-20-2026-04-22-12-12/proposal.md

@@ -0,0 +1,14 @@
+## Why
+
+- The npm registry already serves `@imdeadpool/guardex@7.0.19`, so the package metadata needs the next publishable patch version before another release can be cut.
+- `main` now contains post-`7.0.19` operator-facing improvements that are not recorded in the README release history yet, so the release notes would drift again without a matching version bump.
+
+## What Changes
+
+- Bump the package release metadata from `7.0.19` to `7.0.20` in `package.json` and `package-lock.json`.
+- Add a `README.md` release-notes entry for `v7.0.20` that captures the shipped Active Agents ownership visibility and merged-cleanup evidence fixes already merged on `main`.
+
+## Impact
+
+- Unblocks the next npm publish without changing runtime behavior beyond what is already merged on `main`.
+- Keeps the packaged version, lockfile metadata, and README release history aligned so the release state stays trustworthy.

openspec/changes/agent-codex-release-guardex-7-0-20-2026-04-22-12-12/specs/release-version-bump/spec.md

@@ -0,0 +1,10 @@
+## ADDED Requirements
+
+### Requirement: Release recovery version alignment
+The release metadata SHALL move to the next publishable package version when maintainers intentionally request the next npm release after the current published Guardex version.
+
+#### Scenario: Prepare the next publishable npm patch release
+- **GIVEN** the current Guardex package version is already the latest published release metadata in the repo and npm registry
+- **WHEN** maintainers request the next npm version bump
+- **THEN** `package.json` and `package-lock.json` SHALL be bumped to the next publishable semver
+- **AND** `README.md` SHALL record the new release version with the newly shipped behavior that the package now contains.

openspec/changes/agent-codex-release-guardex-7-0-20-2026-04-22-12-12/tasks.md

@@ -0,0 +1,22 @@
+## 1. Specification
+
+- [x] 1.1 Finalize proposal scope and acceptance criteria for `agent-codex-release-guardex-7-0-20-2026-04-22-12-12`.
+- [x] 1.2 Define normative requirements in `specs/release-version-bump/spec.md`.
+
+## 2. Implementation
+
+- [x] 2.1 Bump `package.json`, `package-lock.json`, and `README.md` to the next publishable Guardex release version.
+- [x] 2.2 No new runtime regression coverage is required because this change only updates release metadata for already-merged behavior.
+
+## 3. Verification
+
+- [x] 3.1 Run `npm test`, `node --check bin/multiagent-safety.js`, and `npm pack --dry-run` for the release-only change. All three passed in `/tmp/gitguardex-release-7-0-20`; `npm test` finished with 187 tests, 185 passes, 0 failures, and 2 skips.
+- [x] 3.2 Run `openspec validate agent-codex-release-guardex-7-0-20-2026-04-22-12-12 --type change --strict`.
+- [x] 3.3 Run `openspec validate --specs`. Current repo baseline reports `No items found to validate.` and exits clean.
+
+## 4. Completion
+
+- [ ] 4.1 Finish the agent branch via PR merge + cleanup (`gx branch finish --branch "agent/codex/release-guardex-7-0-20-2026-04-22-12-12" --base main --via-pr --wait-for-merge --cleanup`).
+- [ ] 4.2 Run `gx release` from the maintainer repo after merge and record the GitHub release URL plus npm workflow result.
+- [ ] 4.3 Record PR URL + final `MERGED` state in the completion handoff.
+- [ ] 4.4 Confirm sandbox cleanup (`git worktree list`, `git branch -a`) or capture a `BLOCKED:` handoff if merge, release, or cleanup is still pending.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imdeadpool/guardex",
-  "version": "7.0.19",
+  "version": "7.0.20",
   "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,