Publish a fresh npm version for the current verified release payload

README.md

@@ -647,6 +647,11 @@ npm pack --dry-run
 <details>
 <summary><strong>v7.x</strong></summary>
 
+### v7.0.21
+- Bumped `@imdeadpool/guardex` from `7.0.20` to `7.0.21` so npm can publish the next release from the current merged mainline.
+- Keep the release scoped to version and release metadata only; the package payload stays the same as the verified `main` branch contents.
+- Published-release automation will pick up this new package version once the matching GitHub release is created.
+
 ### 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.

openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-04-22

openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/notes.md

@@ -0,0 +1,5 @@
+# T1 Notes
+
+- Bump `@imdeadpool/guardex` from `7.0.20` to `7.0.21` so npm can accept the next publish from the already-verified `main` payload.
+- Update the README release notes in the same change so the release history stays aligned with the package metadata.
+- Keep the release narrowly scoped to metadata only; no package payload changes are intended in this bump.

package.json

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