arashi 1.37.0 → 1.38.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +1 -10
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -36,7 +36,7 @@ Verify the installation:
36
36
  aw --version
37
37
  ```
38
38
 
39
- `aw` is the preferred command name. `arashi` remains available for existing scripts and workflows. See the [installation guide](./docs/INSTALLATION.md) for version pinning, manual installation, and troubleshooting, or the [`update` command guide](https://arashi.haphazard.dev/commands/update/) for upgrades.
39
+ `aw` is the preferred command name. `arashi` remains available for existing scripts and workflows. See the [installation guide](https://arashi.haphazard.dev/getting-started/) for version pinning, manual installation, and troubleshooting, or the [`update` command guide](https://arashi.haphazard.dev/commands/update/) for upgrades.
40
40
 
41
41
  ## Quick start
42
42
 
@@ -84,14 +84,6 @@ For a single repository without persisted Arashi configuration, use `aw init --z
84
84
 
85
85
  Run `aw --help`, `aw <command> --help`, or use the [complete command reference](https://arashi.haphazard.dev/commands/) for options and examples.
86
86
 
87
- ### Finishing a coordinated workspace
88
-
89
- `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.
90
-
91
- 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.
92
-
93
- 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.
94
-
95
87
  ## Shell integration
96
88
 
97
89
  Install shell integration for parent-shell directory switching and completion in Bash, Zsh, or Fish:
@@ -133,7 +125,6 @@ files, and the containing install directory.
133
125
  - [Hooks](https://arashi.haphazard.dev/workflows/hooks/)
134
126
  - [Editor and terminal integrations](https://arashi.haphazard.dev/workflows/)
135
127
  - [Agents and automation](https://arashi.haphazard.dev/workflows/agents-and-specs/#automation-and-json)
136
- - [Local configuration reference](./docs/configuration.md)
137
128
 
138
129
  ## Contributing
139
130
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "arashi",
3
- "version": "1.37.0",
3
+ "version": "1.38.0",
4
4
  "description": "Git worktree manager for meta-repositories - The eye of the storm for your development workflow",
5
5
  "keywords": [
6
6
  "cli",