diff --git a/README.md b/README.md index 1b14fff..7276114 100644 --- a/README.md +++ b/README.md @@ -645,6 +645,12 @@ npm pack --dry-run
v7.x +### 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 ` for one file and plain `--force` for whole-surface rewrites. +- GitGuardex now keeps small-task routing caveman-only by default and makes working VS Code agent lanes easier to spot at a glance while keeping the CLI-owned install-surface rollout intact. +- Bumped the release from `7.0.18` → `7.0.19` so the shipped setup/doctor recovery and UX refinements land on a fresh publishable npm version. + ### v7.0.18 - GitGuardex now keeps the install workflow in `gx` itself: `gx branch ...`, `gx locks ...`, `gx worktree prune`, `gx migrate`, and user-level agent-skill install now own the agent lifecycle instead of teaching pasted repo scripts as the primary surface. - Fresh installs switch repo hooks to tiny `gx hook run ...` shims, stop copying repo-local workflow implementations and repo-local skills, and stop injecting Guardex-managed `agent:*` package scripts into consumer repos. diff --git a/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/.openspec.yaml b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/.openspec.yaml new file mode 100644 index 0000000..25345f4 --- /dev/null +++ b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/.openspec.yaml @@ -0,0 +1,2 @@ +schema: spec-driven +created: 2026-04-22 diff --git a/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/proposal.md b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/proposal.md new file mode 100644 index 0000000..06c4db8 --- /dev/null +++ b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/proposal.md @@ -0,0 +1,14 @@ +## Why + +- The user asked for the next npm version in `gitguardex`, so the package metadata needs the next publishable patch release after `7.0.18`. +- The shipped behavior since `7.0.18` is not recorded in the README release history yet, so the package version and release notes would drift again without a matching docs update. + +## What Changes + +- Bump the package release metadata from `7.0.18` to `7.0.19` in `package.json` and `package-lock.json`. +- Add a `README.md` release-notes entry for `v7.0.19` that captures the shipped targeted `--force ` recovery flow plus the post-`7.0.18` UX refinements 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 is easier to trust. diff --git a/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/specs/release-version-bump/spec.md b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/specs/release-version-bump/spec.md new file mode 100644 index 0000000..0ce736c --- /dev/null +++ b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/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 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 +- **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. diff --git a/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/tasks.md b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/tasks.md new file mode 100644 index 0000000..45d72a8 --- /dev/null +++ b/openspec/changes/agent-codex-release-guardex-7-0-19-2026-04-22-10-27/tasks.md @@ -0,0 +1,21 @@ +## 1. Specification + +- [x] 1.1 Finalize proposal scope and acceptance criteria for `agent-codex-release-guardex-7-0-19-2026-04-22-10-27`. +- [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 `node --check bin/multiagent-safety.js`, `node --test test/metadata.test.js`, and `npm pack --dry-run` for the release-only change. `node --check` and `npm pack --dry-run` passed; `node --test test/metadata.test.js` still fails on the pre-existing `critical runtime helper scripts stay in sync with templates` parity mismatch, and the same failure reproduces on current `main`. +- [x] 3.2 Run `openspec validate agent-codex-release-guardex-7-0-19-2026-04-22-10-27 --type change --strict`. +- [x] 3.3 Run `openspec validate --specs`. + +## 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 --base --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. diff --git a/package-lock.json b/package-lock.json index 0bc6729..17229c7 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@imdeadpool/guardex", - "version": "7.0.18", + "version": "7.0.19", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@imdeadpool/guardex", - "version": "7.0.18", + "version": "7.0.19", "license": "MIT", "bin": { "gitguardex": "bin/multiagent-safety.js", diff --git a/package.json b/package.json index 61ce278..617d2ee 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@imdeadpool/guardex", - "version": "7.0.18", + "version": "7.0.19", "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,