v7.0.42

GitGuardex v7.0.42

Changes since v7.0.41.

v7.0.42

• Bumped @imdeadpool/guardex from 7.0.41 to 7.0.42 so the current
  main payload can publish under a fresh npm version after 7.0.41 reached
  the registry.
• Improves the agent-session and cockpit workflow: gx agents start/status
  now share canonical session storage, agent lanes can be previewed, claimed,
  finished by session, and launched through safer supported-agent metadata,
  and cockpit can render live session state through tmux-backed panes.
• Hardens setup and status hygiene by ignoring local .codex/ state during
  setup/doctor, avoiding generic OpenSpec dirty-worktree reuse, and pruning
  stale agent sessions from user-facing status surfaces.

v7.0.41

v7.0.41

• Bumped @imdeadpool/guardex from 7.0.40 to 7.0.41 so the current main payload can publish under a fresh npm version after the v7.0.40 GitHub release landed without a matching npm registry package.
• Ships the Colony companion setup as the default global companion surface: colony maps to @imdeadpool/colony-cli, README setup documents colony install --ide ..., and status tests/images expect Colony instead of cavemem.

Publish from the merged commit with:
npm publish --access public

v7.0.40

GitGuardex v7.0.40

Changes since v7.0.39.

v7.0.40

• Bumped @imdeadpool/guardex from 7.0.39 to 7.0.40 so the current
  main payload can publish under a fresh npm version after 7.0.39 reached
  the registry.
• No new CLI command behavior is introduced in this release lane.

v7.0.39

• Bumped @imdeadpool/guardex from 7.0.38 to 7.0.39 so the current main payload can publish under a fresh npm version after 7.0.38 reached the registry.
• No new CLI command behavior is introduced in this release lane.

v7.0.38

• Bumped @imdeadpool/guardex from 7.0.37 to 7.0.38 so the current main payload can publish under a fresh npm version after 7.0.37 reached the registry.
• No new CLI command behavior is introduced in this release lane.

v7.0.37

GitGuardex v7.0.37

Changes since v7.0.35.

v7.0.37

• Bumped @imdeadpool/guardex from 7.0.36 to 7.0.37 so the current
  package can publish under a fresh npm version after 7.0.36 reached the
  registry.
• Synced the shipped Active Agents template with the canonical VS Code
  extension source so Colony task counts and details install with the package.
• No new CLI command behavior is introduced in this release lane.

v7.0.36

• Bumped @imdeadpool/guardex from 7.0.35 to 7.0.36 so the latest
  branch-finish cwd-prune fix can ship under a fresh npm version after PR #424.
• No new CLI command surface is introduced in this release lane.

v7.0.35

GitGuardex v7.0.35

Changes since v7.0.34.

v7.0.35

• Bumped @imdeadpool/guardex from 7.0.34 to 7.0.35 so the current
  merged main payload can publish on a fresh npm version after PR #420.
• Refreshed README release/skills metadata and shipped Active Agents template
  parity so the current main payload passes release verification.
• No new CLI command behavior is introduced in this release lane.

v7.0.34

Highlights

• Fix: primary-checkout branch-flip guard now survives a dirty tree. The templates/githooks/post-checkout hook auto-stashes dirty edits as guardex-auto-revert <ts> <prev>-><new> (including untracked files) before reverting primary to the protected branch. Previously a dirty tree caused the guard to print auto-revert skipped and silently leave primary flipped onto an agent/* branch — the exact symptom where local main appeared to become the agent worktree branch. (#417)
• Contract tightening in AGENTS.md / CLAUDE.md: new explicit Primary-tree lock (blocking) rule enumerating every disallowed command on the primary checkout (git checkout <ref>, git switch <ref>, git switch -c ..., git checkout -b ..., git worktree add <path> <existing-agent-branch>), plus a Dirty-tree rule pointing at the new auto-stash safety net. (#417)

Changes

• chore(release): bump to 7.0.34 (#418)
• fix(guardex): auto-stash dirty primary on branch-switch (#417)

Full Changelog: v7.0.33...v7.0.34

v7.0.33

What's Changed

• Reduce launch tax when bare gx finds drift by @NagyVikt in #400
• feat(vscode-active-agents): distinct icons per tree section by @NagyVikt in #402
• feat(vscode-active-agents): refine file-icon SVGs by @NagyVikt in #403
• docs(AGENTS): make Claude finish always include via-pr + wait-for-merge + cleanup by @NagyVikt in #404
• Default Active Agents tree toward raw details view by @NagyVikt in #401
• Let gx doctor auto-finish agent branches without a GitHub remote by @NagyVikt in #405
• feat(worktree): prefix worktree leaves with repo basename instead of literal 'agent' by @NagyVikt in #406
• Group gx help commands + quickstart and bump to 7.0.28 by @NagyVikt in #408
• Show green check when agent finished editing worktree by @NagyVikt in #407
• Compact gx status banner with context-aware next-step hint by @NagyVikt in #409
• Default auto-doctor to --current so bare gx stays in this repo by @NagyVikt in #410
• Prompt on bare gx to install missing companion tools by @NagyVikt in #411
• Rewrite README against Claude Design handoff (929 -> 248 lines) by @NagyVikt in #412
• README: add back hero/problem/workflow images + companion tools table by @NagyVikt in #413

Full Changelog: v7.0.27...v7.0.33

v7.0.27

GitGuardex v7.0.27

Changes since v7.0.26.

v7.0.27

• Bumped @imdeadpool/guardex from 7.0.26 to 7.0.27 so npm can publish a fresh version after 7.0.26 was already taken on the registry.
• The shipped agent-branch-start.sh copies now keep the startup auto-transfer path alive under set -o pipefail, so Guardex can still restore moved changes back to the protected checkout when branch startup hits a later failure.
• The shipped agent-branch-finish.sh copies now keep PR-only finish runs from opening temporary integration repos, so maintainers can finish directly through the existing PR lane without extra temp-repo churn.
• Keep the release scoped to version metadata for the already-merged main payload; no additional runtime behavior changes are introduced in this release lane.