v7.0.20
GitGuardex v7.0.20
Changes since v7.0.16.
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
mainis easier to maintain without changing the shipped CLI surface. - Bumped the release from
7.0.19→7.0.20so the shipped Active Agents visibility and cleanup-evidence refinements land on a fresh publishable npm version.
v7.0.19
gx setupandgx doctornow accept targeted managed-file recovery after--force, sogx doctor --force scripts/review-bot-watch.shrepairs 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--forcefor 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.19so 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
gxitself: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-managedagent:*package scripts into consumer repos. gx migratecan move older repos onto the smaller CLI-owned install surface while preserving the managed AGENTS block, lock registry state, hook shims, required gitignore entries, and the repo-local helper assets that still carry local state.- Bumped the release from
7.0.17→7.0.18so the shipped CLI-owned install-surface changes land on a fresh publishable npm version.
v7.0.17
- Restored the published npm package name to
@imdeadpool/guardexafter the@imdeadpool/gitguardexrename only changed the package identity locally and could not rename the existing npm registry entry. - README/install/tutorial/self-update surfaces now point back at
@imdeadpool/guardexwhile keeping GitGuardex as the product/repo brand andgitguardexas the long-form command. - Bumped the release from
7.0.16→7.0.17because@imdeadpool/guardex@7.0.16is already published on npm.