@imdeadpool/guardex 7.0.18 → 7.0.20

package/README.md

@@ -49,7 +49,7 @@ npm i -g @imdeadpool/guardex
 
 <p align="center">
   <sub>
-    Then <code>cd</code> into your repo and run <code>gx setup</code> — hook shims, workflow shims, repo state,
+    Then <code>cd</code> into your repo and run <code>gx setup</code> — hook shims, repo state,
     and OMX&nbsp;/&nbsp;OpenSpec&nbsp;/&nbsp;caveman wiring all scaffold in one go.
   </sub>
 </p>
@@ -88,7 +88,7 @@ cd /path/to/your/repo
 gx setup
 ```
 
-That's it. Install and update via `@imdeadpool/guardex`. Setup installs the minimal repo footprint: managed hook/workflow shims, lock state, AGENTS wiring, and OpenSpec/caveman/OMX scaffolding. Aliases: `gx` (preferred), `gitguardex` (full), `guardex` (legacy compatibility).
+That's it. Install and update via `@imdeadpool/guardex`. Setup installs the minimal repo footprint: managed hook shims, repo-local state, AGENTS wiring, OpenSpec/caveman/OMX scaffolding, and a small set of repo-local helper assets. Aliases: `gx` (preferred), `gitguardex` (full), `guardex` (legacy compatibility).
 
 ---
 
@@ -178,7 +178,7 @@ Before you branch, repair, or start agents, run plain `gx`. It gives you a one-s
 
 ![GitGuardex terminal status output](https://raw.githubusercontent.com/recodeee/gitguardex/main/docs/images/workflow-gx-terminal-status.svg)
 
-Use `gx setup` the first time you wire GitGuardex into a repo. It bootstraps the managed hook/workflow shims, repo state, and optional workspace/OpenSpec wiring. If the repo drifts later, use `gx doctor` as the repair path: it reapplies the managed safety files, verifies the setup, and on protected `main` it auto-sandboxes the repair so your visible base branch stays clean.
+Use `gx setup` the first time you wire GitGuardex into a repo. It bootstraps the managed hook shims, repo-local state, and optional workspace/OpenSpec wiring. If the repo drifts later, use `gx doctor` as the repair path: it reapplies the managed safety files, verifies the setup, and on protected `main` it auto-sandboxes the repair so your visible base branch stays clean.
 
 ---
 
@@ -203,7 +203,7 @@ gx branch finish \
   --base main --via-pr --wait-for-merge --cleanup
 ```
 
-If you use the managed Codex launcher shim, the finish flow runs automatically when the Codex session exits — it auto-commits, retries once after syncing if the base moved during the run, then pushes and opens the PR.
+If you launch Codex through Guardex, the finish flow runs automatically when the Codex session exits — it auto-commits, retries once after syncing if the base moved during the run, then pushes and opens the PR.
 
 GitGuardex normally prunes merged sandboxes for you as part of the finish flow. If you simply do not want a local sandbox/worktree anymore, remove that worktree directly; delete the branch too only if you are intentionally abandoning that lane:
 
@@ -245,7 +245,7 @@ To install the real companion into local VS Code from a GitGuardex-wired repo:
 node scripts/install-vscode-active-agents-extension.js
 ```
 
-It adds an `Active Agents` view to the Source Control container, groups each live repo into `ACTIVE AGENTS` and `CHANGES` sections, reads `.omx/state/active-sessions/*.json`, derives `thinking` versus `working` from each live sandbox worktree, and uses VS Code's native `loading~spin` codicon for the running-state affordance. Reload the VS Code window after install.
+It adds an `Active Agents` view to the Source Control container, groups each live repo into `ACTIVE AGENTS` and `CHANGES` sections, splits `ACTIVE AGENTS` into `BLOCKED`, `WORKING NOW`, `IDLE`, `STALLED`, and `DEAD` when those states are present, reads `.omx/state/active-sessions/*.json`, derives session state from git conflict markers, dirty worktree status, PID liveness, and recent file mtimes, and surfaces working/dead counts in the repo/header affordances. Reload the VS Code window after install.
 
 ---
 
@@ -542,7 +542,7 @@ Expanded flow:
 
 ### OpenSpec in agent sub-branches
 
-- The managed Codex launcher shim enforces OpenSpec workspaces before launching Codex.
+- The Guardex Codex launcher enforces OpenSpec workspaces before launching Codex.
 - `gx branch start` can scaffold both `openspec/changes/<slug>/` and `openspec/plan/<slug>/` when `GUARDEX_OPENSPEC_AUTO_INIT=true`.
 - The collaboration section in `tasks.md` is there for real cleanup handoffs too. If the first Codex/Claude session finishes the implementation work but hits a usage limit before `agent-branch-finish --cleanup`, hand the same sandbox to another agent, let that agent finish cleanup, and record the join/handoff in the change task.
 
@@ -560,26 +560,29 @@ Environment variables:
 ## Files installed by setup
 
 ```text
+AGENTS.md                   # managed multi-agent block appended/refreshed in place
 .githooks/pre-commit        # shim -> gx hook run pre-commit
 .githooks/pre-push          # shim -> gx hook run pre-push
 .githooks/post-merge        # shim -> gx hook run post-merge
 .githooks/post-checkout     # shim -> gx hook run post-checkout
-scripts/agent-branch-start.sh          # shim -> gx branch start
-scripts/agent-branch-finish.sh         # shim -> gx branch finish
-scripts/agent-branch-merge.sh          # shim -> gx branch merge
-scripts/agent-worktree-prune.sh        # shim -> gx worktree prune
-scripts/agent-file-locks.py            # shim -> gx locks ...
-scripts/codex-agent.sh                 # shim -> CLI-owned Codex launcher
-scripts/review-bot-watch.sh            # shim -> CLI-owned review bot
-scripts/openspec/init-plan-workspace.sh    # shim -> CLI-owned OpenSpec init
-scripts/openspec/init-change-workspace.sh  # shim -> CLI-owned OpenSpec init
-.omc/agent-worktrees
-.omx/state/agent-file-locks.json
+scripts/guardex-env.sh      # repo toggle + hook/helper env bridge
+scripts/guardex-docker-loader.sh       # compose env/loader helper
+scripts/agent-session-state.js         # active-session state helper
+scripts/install-vscode-active-agents-extension.js
+.omc/agent-worktrees        # Claude sandbox root
+.omx/agent-worktrees        # Codex sandbox root
+.omx/state/agent-file-locks.json       # file-lock registry
 .github/pull.yml.example
 .github/workflows/cr.yml
+vscode/guardex-active-agents/package.json
+vscode/guardex-active-agents/extension.js
+vscode/guardex-active-agents/session-schema.js
+vscode/guardex-active-agents/README.md
 ```
 
-Repo-local Codex/Claude helper files are no longer copied into the repo. Install the optional user-level companions with `gx install-agent-skills`.
+Legacy compatibility note: older repos may still contain repo-local workflow scripts under `scripts/`. Direct `gx branch ...`, `gx locks ...`, `gx finish`, `gx cleanup`, `gx merge`, and `gx migrate` do not require them. `gx migrate` removes those leftover workflow shims by default. The CLI still honors repo-local `scripts/review-bot-watch.sh` and `scripts/codex-agent.sh` when they are already present so older repos can keep working during migration.
+
+Optional Codex/Claude user-level companions still install with `gx install-agent-skills`; they are not copied into each repo.
 
 ---
 
@@ -642,10 +645,22 @@ npm pack --dry-run
 <details>
 <summary><strong>v7.x</strong></summary>
 
+### 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 `main` is easier to maintain without changing the shipped CLI surface.
+- Bumped the release from `7.0.19` → `7.0.20` so the shipped Active Agents visibility and cleanup-evidence refinements land on a fresh publishable npm version.
+
+### 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 <managed-path>` 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.
-- `gx migrate` can move older repos onto the smaller CLI-owned install surface while preserving the managed AGENTS block, lock registry state, repo-local dispatch shims, and required gitignore entries.
+- `gx migrate` can 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.18` so the shipped CLI-owned install-surface changes land on a fresh publishable npm version.
 
 ### v7.0.17