arashi 1.36.0 → 1.37.0

package/README.md

@@ -53,6 +53,7 @@ Arashi creates matching worktrees for the configured repositories. From there, u
 
 ```bash
 aw status                         # inspect the coordinated workspace
+aw status --local                 # inspect cached remote-tracking refs without fetching
 aw switch feature-auth-refresh    # return to a worktree
 aw pull                           # update repositories
 aw push --set-upstream            # publish branches
@@ -77,11 +78,20 @@ For a single repository without persisted Arashi configuration, use `aw init --z
 | `aw pull` / `aw push` / `aw sync` | Synchronize repositories                  |
 | `aw setup`                        | Run repository setup steps                |
 | `aw remove` / `aw prune`          | Clean up branch worktrees and metadata    |
+| `aw finish`                       | Assess and retire a coordinated workspace |
 | `aw doctor`                       | Diagnose workspace problems               |
 | `aw update`                       | Update Arashi                             |
 
 Run `aw --help`, `aw <command> --help`, or use the [complete command reference](https://arashi.haphazard.dev/commands/) for options and examples.
 
+### Finishing a coordinated workspace
+
+`aw finish <branch-or-parent-path> --dry-run` inventories the registered parent and configured children, refreshes named base/upstream refs into disposable private Git storage, and previews the exact cleanup scope and remove hooks. It does not run hooks, ask for completion/discard/removal consent, or write managed worktrees, refs, config, or index; network metadata refresh is permitted. A blocked or unknown preview still exits successfully **as a preview**, not as cleanup authorization. In main, a human TTY can omit the target to select one parent; selection is not consent. JSON/non-TTY requires an explicit target.
+
+Current `repos.<key>.baseBranch` overrides workspace `baseBranch` (`meta.baseBranch` overrides it for the parent). This is **current policy**, not a record of the create-time base or invocation-only overrides. With no configured base, preview leaves integration unknown; interactive execution can supply a repository-specific remote and full `refs/heads/...` target without saving it. Exact inspected HEAD ancestry of a freshly fetched named base can prove integration, but a negative ancestry result cannot prove non-integration after squash, rebase, or cherry-pick. GitHub PR correlation is attempted when ancestry is unproven and head/base remotes identify the same GitHub repository, including during dry-run: finish runs `gh auth status` and up to three paginated `gh api` requests. A match is only a correlation, not immutable historical merge-time HEAD proof; squash/rebase and other unproven completion still require explicit per-repository manual judgment in a human TTY. `--force` never supplies that judgment.
+
+Run `aw finish <target>` to review unknown completion, then separately consent to discarding dirty, untracked, or ignored local data and absent/ahead-upstream state and to removal. `--force` covers the latter two consents only; `--keep-branches` retains local branches. `--json` / `-j` emits one schema-versioned report and never prompts. Finish rechecks identity, policy, fresh evidence, and exact remove actions after consent and after successful pre-remove hooks before mutation. Hooks may already have side effects if that gate aborts; once removal starts, partial failures retain the existing remove ledger and require manual inspection/retry. External Git/filesystem actors can still race after the final gate: finish does **not** make deletion atomic or serialize other Arashi commands. It does not merge, push, delete remote branches, or detect later reverts.
+
 ## Shell integration
 
 Install shell integration for parent-shell directory switching and completion in Bash, Zsh, or Fish:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arashi",
-  "version": "1.36.0",
+  "version": "1.37.0",
   "description": "Git worktree manager for meta-repositories - The eye of the storm for your development workflow",
   "keywords": [
     "cli",
@@ -56,7 +56,7 @@
   ],
   "type": "module",
   "scripts": {
-    "dev": "node src/index.ts",
+    "dev": "bun src/index.ts",
     "build": "pnpm run completion:check && bun build src/index.ts --compile --minify --outfile bin/arashi.bin",
     "build:debug": "pnpm run completion:check && bun build src/index.ts --compile --sourcemap --outfile bin/arashi.bin",
     "build:all": "pnpm run completion:check && pnpm run build:mac && pnpm run build:linux && pnpm run build:windows",
@@ -65,6 +65,10 @@
     "build:linux": "pnpm run completion:check && bun build src/index.ts --compile --target=bun-linux-x64 --outfile bin/arashi-linux-x64",
     "build:windows": "pnpm run completion:check && bun build src/index.ts --compile --target=bun-windows-x64 --outfile bin/arashi-windows-x64.exe",
     "test": "node scripts/test/run-tests.ts",
+    "benchmark": "node --experimental-strip-types scripts/benchmark/orchestrate.ts",
+    "benchmark:run": "node --experimental-strip-types scripts/benchmark/run.ts",
+    "benchmark:pull:run": "node --experimental-strip-types scripts/benchmark/pull-run.ts",
+    "benchmark:test": "vitest run tests/benchmarks",
     "typecheck": "tsc --noEmit",
     "lint": "oxlint -D no-explicit-any .",
     "lint:fix": "oxlint --fix -D no-explicit-any .",
@@ -96,7 +100,7 @@
     "commander": "12.1.0",
     "conventional-changelog-conventionalcommits": "8.0.0",
     "husky": "9.1.7",
-    "js-yaml": "4.3.1",
+    "js-yaml": "4.3.2",
     "lint-staged": "16.2.7",
     "node-pty": "1.1.0",
     "ora": "8.2.0",
@@ -105,7 +109,7 @@
     "semantic-release": "25.0.6",
     "ts-json-schema-generator": "2.4.0",
     "typescript": "5.9.3",
-    "vitest": "4.1.10"
+    "vitest": "4.1.11"
   },
   "lint-staged": {
     "*.{ts,tsx,js,mjs,cjs,json,md,yml,yaml}": "oxfmt --config .oxfmtrc.json --write"