arashi 1.24.1 → 1.25.0

package/README.md

@@ -172,7 +172,7 @@ arashi switch --no-default-launch           # bypass configured sesh/Herdr mode
 
 Explicit `--tmux` is a per-invocation launcher override for `create` and `switch`; it is not a persisted configuration mode. It requires an active tmux context whose `TMUX` value is non-empty after trimming, uses the selected worktree path as one argv-safe `tmux new-window -c` argument, and does not fall back to another launcher when the prerequisite or launch fails. On `create`, it implies both launch and switch, while validation failures occur before worktree mutation.
 
-`--tab` is a CLI-only launch disposition for `create` and `switch`; it is never persisted. It requests a true terminal tab or documented managed-context equivalent, implies launch (and selection for `create`), overrides automatic parent-shell `cd`, and never degrades to a window or another launcher. Unsupported adapters fail with `TAB_DISPOSITION_UNSUPPORTED`; launch/preflight failures use `LAUNCH_FAILED`. Human-only tab launch is incompatible with `--json`.
+`--tab` is a CLI-only launch disposition for `create` and `switch`; it is never persisted. It requests a true terminal tab or documented managed-context equivalent, implies launch (and selection for `create`), overrides automatic parent-shell `cd`, and never degrades to a window or another launcher. For switch, it bypasses configured `sesh` or `herdr` launch defaults; for create, it bypasses configured generic or editor-scoped launch defaults. An explicit launcher selector remains authoritative. Unsupported adapters fail with `TAB_DISPOSITION_UNSUPPORTED`; launch/preflight failures use `LAUNCH_FAILED`. Human-only tab launch is incompatible with `--json`.
 
 ### Managed Git ignore rules
 
@@ -229,24 +229,16 @@ For automated installs, set `ARASHI_SHELL_INTEGRATION=yes` to enable it without
 
 ## Hooks
 
-Arashi can run lifecycle hooks during `arashi create` and `arashi remove`.
+Arashi can run lifecycle hooks during `arashi create` and `arashi remove`. Configured create uses
+workspace `pre-create`/`post-create` plus repository-specific `pre-create.<repo>` and
+`post-create.<repo>` files. Configured remove evaluates repository, workspace, user-global targeted,
+and user-global shared scopes once per target repository. Standalone mode activates only targeted
+and shared user-global hooks.
 
-- Global hooks in `.arashi/hooks/`:
-  - `pre-create.sh`
-  - `post-create.sh`
-  - `pre-remove.sh`
-  - `post-remove.sh`
-- Repository-specific hooks:
-  - `pre-create.<repo>.sh`
-  - `post-create.<repo>.sh`
-- Scoped remove hooks:
-  - repository scope: `repos/<repo>/.arashi/hooks/pre-remove.sh` and `post-remove.sh`
-  - global shared: `~/.arashi/hooks/pre-remove.sh` and `post-remove.sh`
-  - global targeted: `~/.arashi/hooks/<repo>/pre-remove.sh` and `post-remove.sh`
-
-For `arashi remove`, hook execution order is: repository scope -> workspace-root scope -> global targeted scope -> global shared scope.
-
-`pre-remove.sh` is useful for teardown before deletion (for example, stopping tmux sessions), and `post-remove.sh` can run final cleanup after remove operations complete.
+POSIX uses executable `.sh` files. Windows uses one case-insensitive `.ps1`, `.cmd`, or `.bat`
+candidate per location and never runs `.sh` implicitly. Hook failures participate in create rollback
+or remove finalization, all hooks default to a 300000 ms timeout, and JSON results expose the ordered
+ledger at `data.hookOutcomes` on success or `error.details.hookOutcomes` on failure.
 
 See [`docs/hooks.md`](./docs/hooks.md) for hook behavior, environment variables, and examples.
 
@@ -351,7 +343,7 @@ Legacy switch-only `launchMode` and `launch_mode` fields remain readable for a b
 
 Use `defaults.create` for terminal `arashi create` behavior. Use `defaults.editors.<host>.create` for editor-specific overrides such as VS Code extension create flows. Supported hosts are `vscode`, `cursor`, and `kiro`. Each scope has one canonical `launch` choice: `none` | `auto` | `sesh` | `herdr`. `switch` stays independent, while any enabled launch implies switch handling for the newly created primary worktree.
 
-Create precedence is: reject `--sesh` plus `--herdr`; then explicit `--sesh` / `--herdr`; `--launch`; `--no-launch`; the matching configured scope; and built-in `none`. An editor-hosted invocation does not fall back to terminal or another editor scope.
+Create precedence is: reject `--sesh` plus `--herdr`; then explicit `--sesh` / `--herdr`; `--tab` or `--launch`; `--no-launch`; the matching configured scope; and built-in `none`. `--tab` bypasses the matching configured scope unless an explicit launcher selector is present. An editor-hosted invocation does not fall back to terminal or another editor scope.
 
 Legacy create booleans plus `launchMode` / `launch_mode` remain readable for a bounded compatibility window. Accepted combinations warn on stderr with the exact canonical replacement and do not rewrite the file. Disabled launch plus a launcher, conflicting aliases, and conflicting canonical/legacy choices are rejected before workspace mutation.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arashi",
-  "version": "1.24.1",
+  "version": "1.25.0",
   "description": "Git worktree manager for meta-repositories - The eye of the storm for your development workflow",
   "keywords": [
     "cli",

package/schema/config.schema.json

@@ -34,7 +34,10 @@
           "description": "Optional workspace-level hooks settings",
           "properties": {
             "timeout": {
-              "description": "Timeout in milliseconds for long-running operations",
+              "description": "Lifecycle-hook timeout in milliseconds (default: 300000)",
+              "maximum": 2147483647,
+              "minimum": 1,
+              "multipleOf": 1,
               "type": "number"
             }
           },