@outcomeeng/spx 0.6.15 → 0.6.17

package/README.md

@@ -99,9 +99,9 @@ spx session delete <session-id>
 
 Sessions are stored in `.spx/sessions/` with priority-based ordering (high > medium > low) and FIFO within the same priority. Commands output parseable `<PICKUP_ID>`, `<HANDOFF_ID>`, and `<SESSION_FILE>` tags for automation.
 
-### Spec Management (deprecated)
+### Spec Management
 
-The `spx spec` and `spx spx` CLI domains are **deprecated**. Spec tree management has moved to the **spec-tree** Claude Code plugin, available at [`outcomeeng/plugins`](https://github.com/outcomeeng/plugins). The plugin provides skills for understanding, authoring, decomposing, contextualizing, testing, refactoring, and aligning specification trees.
+The `spx spec` CLI provides deterministic inspection and evidence-projection commands such as `status`, `next`, and `context`. Spec authoring and tree-management workflows live in the **spec-tree** Claude Code plugin, available at [`outcomeeng/plugins`](https://github.com/outcomeeng/plugins). The plugin provides skills for understanding, authoring, decomposing, contextualizing, testing, refactoring, and aligning specification trees.
 
 ## Development
 
@@ -177,7 +177,12 @@ The project uses GitHub Actions for continuous integration and publishing:
 
 ### Publishing a Release
 
-1. Sync `main` with `origin/main`: `git pull --ff-only origin main`
+Run every step in the canonical main checkout. Keep `main` checked out there for
+the entire release so Git refuses attempts to check out `main` in a linked
+worktree.
+
+1. Confirm `git branch --show-current` reports `main`, then sync it with
+   `origin/main`: `git pull --ff-only origin main`
 2. Bump the version with `pnpm version patch --no-git-tag-version`, unless the
    release request specifies `minor`, `major`, or an exact version
 3. Run `pnpm run publish:check`
@@ -194,22 +199,25 @@ npm view @outcomeeng/spx version
 npm audit signatures
 ```
 
-8. Refresh the operator-visible CLI from the release tag in the main worktree
-   and confirm it reports the released version:
+8. Require current `main` to equal the release tag commit, then rebuild the
+   operator-visible CLI and confirm it reports the released version:
 
 ```bash
-git fetch --tags origin
-git switch --detach vX.Y.Z
-pnpm run build
-spx --version
-git switch main
-git pull --ff-only origin main
+git fetch --tags origin &&
+  test "$(git branch --show-current)" = main &&
+  test "$(git rev-parse HEAD)" = "$(git rev-parse 'vX.Y.Z^{commit}')" &&
+  test "$(git rev-parse origin/main)" = "$(git rev-parse 'vX.Y.Z^{commit}')" &&
+  pnpm run build &&
+  spx --version
 ```
 
 Do not refresh the CLI with `pnpm install`, global `pnpm add -g`, or package
 manager update commands during release close-out. The operator-visible binary
-comes from the release tag after the main worktree checks out that tag and
-rebuilds it; return the worktree to current main after the version check.
+comes from the canonical main checkout only while its HEAD and fetched
+`origin/main` both equal the release tag commit. Stop before the build if either
+ref advanced. On a mismatch, leave the CLI unchanged and complete the refresh
+through a later release that starts from newly synced `main`; never move `main`
+backward to retry the old release. The checkout remains on `main` throughout.
 
 ## Technical Stack
 
@@ -227,7 +235,7 @@ src/
 ├── commands/      # CLI command implementations
 │   ├── session/     # spx session subcommands
 │   ├── validation/  # spx validation subcommands
-│   └── spec/        # spx spec subcommands (deprecated)
+│   └── spec/        # spx spec subcommands
 ├── domains/       # Domain routers
 ├── validation/    # Lint, typecheck, circular dep logic
 ├── session/       # Session lifecycle and storage