@imdeadpool/guardex 7.0.13 → 7.0.15

package/README.md

@@ -116,6 +116,8 @@ Running Codex across several existing worktrees (e.g. from VS Code Source Contro
 gx finish --all
 ```
 
+Codex sessions default to `.omx/agent-worktrees/`. Claude Code sessions default to `.omc/agent-worktrees/`, so Claude sandboxes stay under the Claude runtime folder instead of sharing the Codex root.
+
 ---
 
 ## Visual reference
@@ -161,13 +163,25 @@ gx setup --target /path/to/repo --parent-workspace-view
 
 ### Monorepo support
 
-Setup auto-installs into every nested git repo (e.g. `apps/*/.git`). Submodules and worktrees under `.omx/agent-worktrees/` are skipped.
+Setup auto-installs into every nested git repo (e.g. `apps/*/.git`). Submodules and worktrees under `.omx/agent-worktrees/` or `.omc/agent-worktrees/` are skipped.
 
 ```sh
 gx setup --target /mainfolder
 gx setup --target /mainfolder --no-recursive
 ```
 
+### Fresh repos + Docker Compose
+
+On a brand-new repo, `gx setup` now prints the next real steps too: commit the scaffold, start the first agent branch, and add `origin` if you want finish/merge flows to leave the machine.
+
+If the repo already has `docker-compose.yml`, `docker-compose.yaml`, `compose.yml`, or `compose.yaml`, setup also points you at the bundled Docker loader:
+
+```sh
+GUARDEX_DOCKER_SERVICE=app bash scripts/guardex-docker-loader.sh -- npm test
+```
+
+When the service is already running, the loader uses `docker compose exec`; otherwise it falls back to `docker compose run --rm`.
+
 ### Protected branches
 
 ```sh
@@ -206,8 +220,15 @@ gx cleanup                # prune merged/stale branches and worktrees
 gx cleanup --watch --interval 60
 gx cleanup --idle-minutes 10
 gx cleanup --watch --once --interval 60
+gx release                # create/update the current GitHub release from README notes
 ```
 
+### Release publishing
+
+`gx release` is the maintainer path for package releases. It reads the versioned sections under `README.md -> Release notes`, finds the last published GitHub release, and writes one grouped GitHub release body covering everything newer than that release and up to the current package version.
+
+That GitHub release then triggers `.github/workflows/release.yml`, which performs the actual `npm publish --provenance --access public` step.
+
 ### Prompts for your agents
 
 ```sh
@@ -441,6 +462,7 @@ scripts/openspec/init-plan-workspace.sh
 .claude/commands/gitguardex.md
 .github/pull.yml.example
 .github/workflows/cr.yml
+.omc/agent-worktrees
 .omx/state/agent-file-locks.json
 ```
 
@@ -450,17 +472,17 @@ If `package.json` exists, setup also adds `agent:*` helper scripts.
 
 ## Frontend mirror
 
-- Standalone frontend repo: <https://github.com/Webu-PRO/guardex-frontend>
+- Standalone frontend repo: <https://github.com/recodeee/gitguardex-frontend>
 - This repo tracks the frontend under `frontend/` and auto-mirrors it via `.github/workflows/sync-frontend-mirror.yml` on changes to `main`.
 
 Setup (in this repo):
 
 1. `Settings → Secrets and variables → Actions`
-2. Add secret `GUARDEX_FRONTEND_MIRROR_PAT` with `contents:write` on `Webu-PRO/guardex-frontend`
+2. Add secret `GUARDEX_FRONTEND_MIRROR_PAT` with `contents:write` on `recodeee/gitguardex-frontend`
 
 Optional overrides (Actions Variables):
 
-- `GUARDEX_FRONTEND_MIRROR_REPO` (default `Webu-PRO/guardex-frontend`)
+- `GUARDEX_FRONTEND_MIRROR_REPO` (default `recodeee/gitguardex-frontend`)
 - `GUARDEX_FRONTEND_MIRROR_BRANCH` (default `main`)
 
 Manual run:
@@ -507,6 +529,15 @@ npm pack --dry-run
 <details>
 <summary><strong>v7.x</strong></summary>
 
+### 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.