Unblock the next Guardex npm publish after 7.0.15 was already taken

README.md

@@ -529,6 +529,12 @@ npm pack --dry-run
 <details>
 <summary><strong>v7.x</strong></summary>
 
+### v7.0.16
+- `gx doctor` now keeps nested repo repair runs visibly progressing, and overlapping integration work stays off the protected base branch instead of trying to merge back on `main`.
+- Cleanup and finish flows are less brittle: `codex-agent` no longer waits on PRs that can never exist, and prune cleanup now walks both managed worktree roots so stale sandboxes get removed consistently.
+- Mirror-sync diagnostics are quieter: when the mirror PAT is unset, Guardex now skips the sync path instead of marking the run red, and shared `ralplan` lanes stay easier to identify during handoff/debugging.
+- Bumped `@imdeadpool/guardex` from `7.0.15` → `7.0.16` after npm rejected a republish over the already-published `7.0.15`.
+
 ### v7.0.15
 - `gx doctor` no longer blocks recursive nested protected-repo repairs on child PR merge waits; nested sandboxes now force `--no-wait-for-merge` so the parent repair loop can continue.
 - `gx setup` can now refresh managed files from protected `main` through a temporary sandbox branch/worktree, sync the managed outputs back to the visible base checkout, and prune the sandbox afterward.

openspec/changes/agent-codex-release-guardex-7-0-16-2026-04-21-15-22/.openspec.yaml

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

openspec/changes/agent-codex-release-guardex-7-0-16-2026-04-21-15-22/proposal.md

@@ -0,0 +1,15 @@
+## Why
+
+- `npm publish` rejected `@imdeadpool/guardex@7.0.15` because that version is already published, so the package needs the next publishable patch version before release can proceed.
+- The shipped behavior since `7.0.15` is not captured in the README release notes yet, and `package-lock.json` is also still lagging behind the manifest version.
+
+## What Changes
+
+- Bump the package release metadata from `7.0.15` to `7.0.16` in `package.json` and `package-lock.json`.
+- Add a `README.md` release-notes entry for `v7.0.16` that summarizes the post-`7.0.15` Guardex behavior now shipping in the package.
+- Update the `gx release` integration expectation in `test/install.test.js` so the release workflow tracks the current package version.
+
+## Impact
+
+- Unblocks the next npm publish without changing runtime behavior beyond what is already merged on `main`.
+- Keeps the packaged version, lockfile metadata, and documented release notes aligned so release state is easier to trust.

openspec/changes/agent-codex-release-guardex-7-0-16-2026-04-21-15-22/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 npm rejects the current version as already published.
+
+#### Scenario: Recover from an already-published npm version
+- **GIVEN** `npm publish` rejects the current Guardex version as already published
+- **WHEN** maintainers prepare the recovery release
+- **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-16-2026-04-21-15-22/tasks.md

@@ -0,0 +1,21 @@
+## 1. Specification
+
+- [x] 1.1 Finalize proposal scope and acceptance criteria for `agent-codex-release-guardex-7-0-16-2026-04-21-15-22`.
+- [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 Update the `gx release` integration expectation in `test/install.test.js` so the release workflow follows the current package version.
+
+## 3. Verification
+
+- [x] 3.1 Run `npm test`, `node --check bin/multiagent-safety.js`, and `npm pack --dry-run` for the release-only change. `npm test` passed `150/150`; `node --check bin/multiagent-safety.js` passed; `npm pack --dry-run` produced `imdeadpool-guardex-7.0.16.tgz`.
+- [x] 3.2 Run `openspec validate agent-codex-release-guardex-7-0-16-2026-04-21-15-22 --type change --strict`. Result: `Change 'agent-codex-release-guardex-7-0-16-2026-04-21-15-22' is valid`.
+- [x] 3.3 Run `openspec validate --specs`. Result: `No items found to validate.`
+
+## 4. Completion
+
+- [ ] 4.1 Finish the agent branch via PR merge + cleanup (`gx finish --via-pr --wait-for-merge --cleanup` or `bash scripts/agent-branch-finish.sh --branch <agent-branch> --base <base-branch> --via-pr --wait-for-merge --cleanup`).
+- [ ] 4.2 Record PR URL + final `MERGED` state in the completion handoff.
+- [ ] 4.3 Confirm sandbox cleanup (`git worktree list`, `git branch -a`) or capture a `BLOCKED:` handoff if merge/cleanup is pending.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imdeadpool/guardex",
-  "version": "7.0.15",
+  "version": "7.0.16",
   "description": "GitGuardex: hardened multi-agent git guardrails for parallel agent work.",
   "license": "MIT",
   "preferGlobal": true,

test/install.test.js

@@ -5015,9 +5015,9 @@ exit 1
   assert.match(args, new RegExp(`^create$`, 'm'));
   assert.match(args, new RegExp(`^v${escapeRegexLiteral(cliVersion)}$`, 'm'));
   assert.match(args, /^--repo$\nrecodeee\/gitguardex$/m);
-  assert.match(args, /^--title$\nv7\.0\.15$/m);
+  assert.match(args, new RegExp(`^--title$\\nv${escapeRegexLiteral(cliVersion)}$`, 'm'));
   assert.match(args, /Changes since v7\.0\.12\./);
-  assert.match(args, /### v7\.0\.15/);
+  assert.match(args, new RegExp(`### v${escapeRegexLiteral(cliVersion)}`));
   assert.match(args, /### v7\.0\.14/);
   assert.match(args, /### v7\.0\.13/);
 });