v7.0.16

GitGuardex v7.0.16

Changes since v7.0.15.

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

GitGuardex v7.0.15

Changes since v7.0.12.

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.
• Bumped @imdeadpool/guardex from 7.0.14 → 7.0.15 after npm rejected a republish over the already-published 7.0.14.

v7.0.14

• Bumped @imdeadpool/guardex from 7.0.13 → 7.0.14 after npm rejected a republish over the already-published 7.0.13.
• No package payload changes beyond the release metadata bump; this release exists so npm publish can proceed with a fresh semver.

v7.0.13

• gx status and gx setup now present the Claude companion as oh-my-claudecode while still installing the published npm package oh-my-claude-sisyphus.
• When that dependency is inactive or the user declines the optional install, Guardex now prints the upstream repo URL so the missing dependency is explicit instead of hidden behind the npm package name.
• Bumped @imdeadpool/guardex from 7.0.12 → 7.0.13 after npm rejected a republish over the already-published 7.0.12.

v7.0.12

GitGuardex v7.0.12

• restart into the installed CLI after a successful self-update so the same gx invocation no longer prints a stale pre-update version
• keep the existing pinned retry guard when npm reports success but leaves old bytes on disk
• bump @imdeadpool/guardex from 7.0.11 to 7.0.12

v7.0.11

GitGuardex v7.0.11

• fix the npm publish workflow trigger so releases run from the published release event or manual dispatch only
• remove the duplicate tag-push publish path that was leaving extra cancelled deployment cards in the npm environment
• bump @imdeadpool/guardex from 7.0.10 to 7.0.11 so the replacement release can publish cleanly after 7.0.10 already landed on npm

v7.0.10

GitGuardex v7.0.10

• promote gitguardex to the primary long-form CLI, skill, and command surface while keeping gx and guardex compatibility aliases
• bump the npm package metadata to 7.0.10 and add the new gitguardex bin alias
• slim the always-loaded templates to 1930 bytes total to reduce fixed context
• align release workflow and repository metadata with the canonical recodeee/gitguardex repository
• include the frontend smoke-test fix required for release verification to pass under npm test

guardex v7.0.3

Changed\n- Refactored agent branch/worktree naming to role + timestamp format.\n- Normalized agent role detection and added deterministic --print-name-only output mode.\n- Updated tests for the new branch naming shape.\n\nNotes\n- See README Release notes for full historical details (v7.0.0-v7.0.3).

guardex v7.0.2

• Fix: __source-probe-* worktree leak on conflict exit. agent-branch-finish.sh was registering its cleanup() trap after the sync-guard rebase block, so when that rebase hit conflicts and the script exited, the throwaway probe worktree was never removed. gx doctor sweeps against stalled branches accumulated one new probe per run.
• The cleanup trap is now installed immediately after probe creation, and aborts any in-progress rebase/merge before worktree remove --force so conflict-stuck probes are cleaned up reliably.

guardex v7.0.1

• Maintenance release.

guardex v7.0.0

• Breaking (soft). Consolidated 17 commands into 12 visible commands with flag-based subcommands. Five removed names (init, install, fix, scan, copy-prompt, copy-commands, print-agents-snippet, review) still work but print a one-line deprecation notice on stderr and will be removed in v8. See the migration table in "Copy-paste: common commands" above.

• Token-usage improvements. Trimmed the auto-installed agent templates that live inside every consumer repo and get loaded into every Claude/Codex session:

  • templates/AGENTS.multiagent-safety.md: 6990 B → 1615 B (−77%)
  • templates/codex/skills/guardex/SKILL.md: 2732 B → 1086 B (−60%)
  • templates/claude/commands/guardex.md: 472 B → 357 B (−24%)
  • Total: 10194 B → 3058 B per consumer repo (−70%, ~1.5k fewer tokens per agent session).

  The AI_SETUP_PROMPT and AI_SETUP_COMMANDS constants used by gx prompt are now compact checklists, so piping gx prompt into a model context is cheaper too.

• New gx prompt command replaces three prompt-emitting commands: gx prompt (full checklist), gx prompt --exec (commands only), gx prompt --snippet (AGENTS.md managed-block template).

• New flag surface on gx setup: --install-only (templates/hooks/locks only), --repair (fix drift), plus the existing --target, --parent-workspace-view, --dry-run, etc.

• New gx status --strict mirrors the old gx scan behavior (exit non-zero on findings).

• Updated internal REQUIRED_PACKAGE_SCRIPTS for consumer package.json so agent:safety:scan and agent:safety:fix helper scripts now invoke the new v7 surface (gx status --strict, gx setup --repair).

musafety v5.0.0

musafety 5.0.0 release marker.\n\n- Includes latest guardrail updates merged on April 11, 2026.\n- npm publish currently fails with registry/package permission (E404) and needs npm package ownership/token fix.