arashi 1.32.1 → 1.34.0

package/README.md

@@ -4,424 +4,105 @@
 [![CI](https://github.com/corwinm/arashi/actions/workflows/ci.yml/badge.svg)](https://github.com/corwinm/arashi/actions/workflows/ci.yml)
 [![License](https://img.shields.io/github/license/corwinm/arashi.svg)](https://github.com/corwinm/arashi/blob/main/LICENSE)
 
-Arashi is a Git worktree manager for meta-repositories.
+Arashi is a Git worktree manager for meta-repositories. It coordinates related repositories in one feature workspace while each repository keeps its own history, CI, and pull requests.
 
-It keeps related repositories aligned while you work on a feature branch across a shared workspace.
-
-Arashi makes a polyrepo work like a monorepo during development, while every repository keeps its own history, CI, and pull requests.
-
-[Documentation](https://arashi.haphazard.dev)
+[Documentation](https://arashi.haphazard.dev) · [Command reference](https://arashi.haphazard.dev/commands/) · [Workflow guides](https://arashi.haphazard.dev/workflows/)
 
 ## Installation
 
-### Option 1: Install with curl (official direct install)
-
-Prerequisites:
-
-- `curl`
-- `bash`
-- A SHA-256 tool (`shasum`, `sha256sum`, or `openssl`)
+macOS and Linux:
 
 ```bash
 curl -fsSL https://arashi.haphazard.dev/install | bash
 ```
 
-Install a specific release:
-
-```bash
-curl -fsSL https://arashi.haphazard.dev/install | ARASHI_VERSION=1.4.0 bash
-```
-
-Verify install:
-
-```bash
-aw --version
-```
-
-By default, the installer places `arashi` in `~/.arashi/bin`, adds that path to your shell config, and in interactive installs offers to enable shell integration for `aw switch --cd`.
-Use `aw` for documented workflows. The `arashi` executable remains supported for existing scripts and workflows, and both names run the same implementation. Product names, configuration, environment variables, packages, and native binaries retain their established Arashi names.
-
-The installer transaction verifies that both executable entrypoints report the same non-empty version before declaring success.
-
-If curl installation fails, or if the smoke test reports a bad release artifact, use npm installation below or the manual release instructions in [`docs/INSTALLATION.md`](./docs/INSTALLATION.md).
-
-### Option 2: Install on Windows with PowerShell
-
-PowerShell is the canonical Windows installer:
+Windows PowerShell:
 
 ```powershell
 powershell -c "irm https://arashi.haphazard.dev/install.ps1 | iex"
 ```
 
-It verifies and installs one `arashi.bin.exe` plus `arashi`/`aw` wrappers for Git Bash, `arashi.ps1`/`aw.ps1`, and `arashi.bat`/`aw.bat` from the same release. The default directory is `%USERPROFILE%\.arashi\bin`; the installer adds it to the persistent user PATH. It does not create or modify `.bashrc` or another shell profile. Open a new Git Bash window before verifying the installed version so it inherits the PATH change.
+Open a new terminal after the Windows installer so it inherits the updated user `PATH`.
 
-### Option 3: Install with npm
+With npm:
 
 ```bash
 npm install -g arashi
 ```
 
-The npm package is script-free: it does not require package-manager lifecycle scripts or `postinstall` approval. It maps both npm bins to the same lightweight JavaScript entrypoint, then downloads the matching platform binary on first use through either name.
-
-To preinstall the binary explicitly, run:
-
-```bash
-aw install
-```
-
-To check for package updates or refresh the matching platform binary, run:
-
-```bash
-aw update --check
-aw update --dry-run
-aw update --yes
-```
-
-`aw update` can update npm-managed installs when it can confidently detect the package manager, including npm, pnpm, Yarn, Bun, and Vite+ (`vp update -g arashi`). For official direct-installer installs, `aw update --yes` reruns the platform installer against the current binary directory: the POSIX curl installer on macOS/Linux and a deferred PowerShell installer on Windows after the current Arashi process exits.
-
-Verify install:
+Verify the installation:
 
 ```bash
 aw --version
 ```
 
-If npm is unavailable or binary installation fails, use the curl installer command above or the manual release instructions in [`docs/INSTALLATION.md`](./docs/INSTALLATION.md).
-
-### Manual install from GitHub Releases
+`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.
 
-If you prefer not to use npm, download a platform binary from [GitHub Releases](https://github.com/corwinm/arashi/releases) and place it on your `PATH`.
+## Quick start
 
-macOS (Apple Silicon):
+From the repository that will coordinate your projects:
 
 ```bash
-curl -L https://github.com/corwinm/arashi/releases/latest/download/arashi-macos-arm64 -o arashi.bin
-curl -L https://github.com/corwinm/arashi/releases/latest/download/arashi -o arashi
-curl -L https://github.com/corwinm/arashi/releases/latest/download/aw -o aw
-chmod +x arashi.bin arashi aw
-sudo install -m 0755 arashi.bin arashi aw /usr/local/bin/
-```
-
-Linux (x64):
-
-```bash
-curl -L https://github.com/corwinm/arashi/releases/latest/download/arashi-linux-x64 -o arashi.bin
-curl -L https://github.com/corwinm/arashi/releases/latest/download/arashi -o arashi
-curl -L https://github.com/corwinm/arashi/releases/latest/download/aw -o aw
-chmod +x arashi.bin arashi aw
-sudo install -m 0755 arashi.bin arashi aw /usr/local/bin/
-```
-
-Windows (PowerShell and Git Bash):
-
-```powershell
-# Download arashi-windows-x64.exe, arashi, arashi.ps1, arashi.bat,
-# aw, aw.ps1, aw.bat,
-# and arashi-checksums.txt from the same release.
-# Verify all seven payload files against arashi-checksums.txt.
-# Rename arashi-windows-x64.exe to arashi.bin.exe and keep the seven files together on PATH.
-```
-
-Windows manual installation requires `arashi-windows-x64.exe`, `arashi`, `arashi.ps1`, `arashi.bat`, `aw`, `aw.ps1`, `aw.bat`, and `arashi-checksums.txt` from the same release. Verify all seven payload files, rename the executable to `arashi.bin.exe`, and keep the payload together on PATH. Manual release installations do not create the direct installer's ownership ledger; deliberately move or remove the manual payload before later using the direct installer.
-
-You can also build from source for local development. Development is pinned to Node.js 24.18.0, which satisfies pnpm 11's Node.js 22.13 minimum, and pnpm 11.20.0; nvm users can select the repository's development runtime with `nvm use`.
-
-```bash
-nvm use # Optional; reads .nvmrc
-pnpm install
-pnpm run build
-```
-
-## Command Surface
-
-Arashi currently provides these commands:
-
-- `aw init`
-- [`aw init --zero-config`](docs/standalone.md) for a single repository with `.worktrees/<branch>` paths and no persisted Arashi configuration
-- `aw install`
-- `aw update [--check] [--dry-run] [--yes]`
-- `aw add <git-url>`
-- `aw clone [--all] [--base <branch>] [--repo-base <repository=branch>]`
-- `aw create <branch> [--base <branch>] [--repo-base <repository=branch>] [--tab] [--tmux|--sesh|--herdr]`
-- `aw list`
-- `aw status`
-- `aw remove <branch|path>`
-- `aw prune [--dry-run]` - clean stale Git worktree metadata
-- `aw switch [filter] [--repos|--all] [--tab] [--cd|--launch] [--tmux|--sesh|--herdr] [--ignore-configured-launcher]`
-- `aw completion <bash|zsh|fish>`
-- `aw shell init <bash|zsh|fish>`
-- `aw shell install`
-- `aw pull`
-- `aw push [--set-upstream] [--dry-run] [--only <repo>] [--json]`
-- `aw sync`
-- `aw setup [--only <repo>] [--verbose]`
-
-## Quick Example
-
-```bash
-aw init                         # repository-local ignore rules (default)
-aw init --ignore-scope tracked  # opt in to a shared .gitignore block
+aw init
 aw add git@github.com:your-org/frontend.git
 aw add git@github.com:your-org/backend.git
 aw create feature-auth-refresh
-aw create feature-auth-refresh --base feature/auth
-aw create feature-auth-refresh --repo-base @meta=develop --repo-base frontend=release/2.x
-aw clone --all --base main --repo-base frontend=release/2.x
-aw create feature-auth-refresh --launch
-aw create feature-auth-refresh --tmux
-aw create feature-auth-refresh --herdr
-aw create feature-auth-refresh --tab
-aw create feature-auth-refresh --no-launch
-aw shell install
-aw status
-aw switch feature-auth-refresh          # parent repo worktrees
-aw switch --repos feature-auth-refresh  # child repo worktrees in current workspace
-aw switch --all feature-auth-refresh    # all repos
-aw switch --repos docs                  # repo-name matching in child repos
-aw switch --cd feature-auth-refresh     # parent-shell cd when shell integration is active
-aw switch --launch feature-auth-refresh # force launch while preserving a configured launcher
-aw switch --tmux feature-auth-refresh   # force a new plain tmux window
-aw switch --herdr feature-auth-refresh  # open or focus a persistent Herdr workspace
-aw switch --tab feature-auth-refresh    # request a true tab or managed equivalent
-aw switch --ignore-configured-launcher  # bypass configured sesh/Herdr mode once
-aw switch --launch --ignore-configured-launcher # force generic automatic launch
-```
-
-### Add from a linked parent worktree
-
-When `aw add` runs from an active linked parent worktree, Arashi creates one canonical clone in the parent main checkout and leaves it on the child default branch. It then creates the active child as a linked worktree on the coordinated branch and updates only the active parent configuration. Direct-main and configured-bare adds keep their existing single-placement behavior. See the [add command guide](https://arashi.haphazard.dev/commands/add/) for branch, managed-ignore, JSON, and rollback details.
-
-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. 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
-
-Configured workspaces keep `reposDir` and `worktreesDir` effectively ignored. Arashi asks Git
-first, so an existing tracked `.gitignore`, repository-local `.git/info/exclude`, or configured
-global excludes rule is honored without duplication. Missing safe repository-relative rules use
-the common repository's local exclude file by default, including when a command runs in a linked
-worktree.
-
-Use `aw init --ignore-scope tracked` when the team wants Arashi-owned rules committed in the
-workspace `.gitignore`. Use `aw init --ignore-scope none` for a fully manual workflow; Arashi
-will warn about unignored managed paths but will not edit ignore files. Running
-`aw init --ignore-scope local` resets that clone-local preference without recreating an
-existing workspace. The explicit `tracked` or `none` preference is stored only in local Git config
-as `arashi.ignoreScope`; Arashi never creates or modifies global Git ignore configuration.
-
-`init`, `pull`, `clone`, `add`, and `create` reconcile the same owned rules before materializing
-configured repositories or worktrees. `doctor` reports missing, unsafe, invalid, or stale managed
-ignore state without changing it.
-
-## Workflow Guides
-
-Use the docs site workflow guides when you want setup guidance by outcome instead of by individual command.
-
-For contributors working on Arashi itself, the project planning workflow in the `arashi-arashi` meta-repo now uses OpenSpec. Older SpecKit-oriented references in legacy planning artifacts are historical context only.
-
-- Hooks and configuration defaults: [arashi.haphazard.dev/workflows/hooks-and-config](https://arashi.haphazard.dev/workflows/hooks-and-config/)
-- Integrations for Herdr, VSCode, tmux, and `tmux` plus `sesh`: [arashi.haphazard.dev/workflows](https://arashi.haphazard.dev/workflows/)
-- Agent-assisted and spec-driven change flow: [arashi.haphazard.dev/workflows/agents-and-specs](https://arashi.haphazard.dev/workflows/agents-and-specs/)
-
-## Shell Integration
-
-Use shell integration for parent-shell directory switching and native tab completion. Bash, Zsh, and Fish are supported through both `arashi` and `aw`.
-
-The official curl installer can offer this automatically. If you skip it or use npm, install it for the active shell with:
-
-```bash
-aw shell install
 ```
 
-`aw shell install` adds a managed pair to the active shell startup file: the parent-shell wrapper first and completion activation second. Repeating the command is idempotent and upgrades older wrapper-only blocks.
-
-For manual setup, activate the wrapper and completion independently:
+Arashi creates matching worktrees for the configured repositories. From there, use:
 
 ```bash
-# Bash
-eval "$(command aw shell init bash)"
-source <(command aw completion bash)
-
-# Zsh
-eval "$(command aw shell init zsh)"
-source <(command aw completion zsh)
-
-# Fish
-command aw shell init fish | source
-command aw completion fish | source
+aw status                         # inspect the coordinated workspace
+aw switch feature-auth-refresh    # return to a worktree
+aw pull                           # update repositories
+aw push --set-upstream            # publish branches
+aw remove feature-auth-refresh    # remove the coordinated worktrees
 ```
 
-`aw shell init <shell>` remains wrapper-only and defines both parent-shell functions, unless an unrelated `aw` alias or function already owns that shell name. `aw completion <shell>` registers the same completion model for both executable names and emits only deterministic sourceable shell code, including on npm first use when the platform binary must be installed.
-
-Completion covers commands, aliases, options, finite choices, conflicts, and positional boundaries. In an Arashi workspace it also resolves configured repository and group selector segments, switch/remove worktrees and paths, and move source/target references. Dynamic lookup is local and read-only, silent on unavailable or broken metadata, and limited to a 200 ms whole-query budget; it performs no network requests, hooks, prompts, workspace mutations, or child operations. Static completion remains available outside a workspace.
-
-Once installed, you can use `aw switch --cd <filter>` for one-off parent-shell switching or set `.arashi/config.json` `defaults.switch.mode` to `"cd"` or contextual `"auto"`. The canonical modes are `auto` | `cd` | `launch` | `sesh` | `herdr`.
-
-If shell integration is inactive, `aw switch --cd` warns and skips launch fallback for that invocation.
-
-For automated installs, set `ARASHI_SHELL_INTEGRATION=yes` to enable it without prompting or `ARASHI_SHELL_INTEGRATION=no` to skip it.
+For a single repository without persisted Arashi configuration, use `aw init --zero-config`. See the [standalone workflow](https://arashi.haphazard.dev/workflows/standalone/).
 
-## Hooks
+## Core commands
 
-Arashi can run file-backed or configured inline lifecycle hooks during `aw create` and
-`aw remove`. Inline workspace values live only at root `hooks.scripts.<lifecycle>`; repository
-values live only at `repos.<name>.hooks.<lifecycle>`. Use inline config for short reviewable commands
-and native files for substantial scripts. One inline/file source may own a logical location; a
-same-location collision fails preflight instead of running both.
+| Command                           | Purpose                          |
+| --------------------------------- | -------------------------------- |
+| `aw init`                         | Initialize a workspace           |
+| `aw add`                          | Add a repository                 |
+| `aw clone`                        | Clone configured repositories    |
+| `aw configure`                    | Edit existing workspace settings |
+| `aw create`                       | Create coordinated worktrees     |
+| `aw list`                         | List worktrees                   |
+| `aw status`                       | Show repository status           |
+| `aw switch`                       | Select and open a worktree       |
+| `aw pull` / `aw push` / `aw sync` | Synchronize repositories         |
+| `aw setup`                        | Run repository setup steps       |
+| `aw remove` / `aw prune`          | Clean up worktrees and metadata  |
+| `aw doctor`                       | Diagnose workspace problems      |
+| `aw update`                       | Update Arashi                    |
 
-Configured create uses workspace `pre-create`/`post-create` plus repository-specific create locations.
-Configured remove evaluates repository, workspace, user-global targeted, and user-global shared scopes
-once per target repository. `--no-hooks` is create-only; `--no-hook-input` applies to both commands.
-Standalone mode remains file-only and activates only targeted and shared user-global hooks.
+Run `aw --help`, `aw <command> --help`, or use the [complete command reference](https://arashi.haphazard.dev/commands/) for options and examples.
 
-Hook failures participate in create rollback or remove finalization. Inline and file sources share the
-configured timeout, input, JSON isolation, dry-run, and ordered outcome policies. Public records expose
-source kind/owner metadata but never disclose configured snippet text.
+## Shell integration
 
-See [`docs/configuration.md`](./docs/configuration.md#inline-lifecycle-hook-configuration) for values and
-[`docs/hooks.md`](./docs/hooks.md) for exact lookup, lifecycle, environment, and automation behavior.
-
-## Workflow Shortcuts
-
-Use `aw list` with `fzf` and optional keybinds to speed up daily navigation.
-
-### Jump to a worktree (`cd`)
-
-```bash
-# One-off jump
-cd "$(aw list | fzf)"
-```
-
-```bash
-# Bash keybind (Ctrl+G)
-bind '"\C-g":"cd \$(aw list | fzf)\n"'
-```
-
-```zsh
-# Zsh keybind (Ctrl+G)
-bindkey -s '^g' 'cd $(aw list | fzf)\n'
-```
-
-### Open or switch tmux sessions with `sesh`
+Install shell integration for parent-shell directory switching and completion in Bash, Zsh, or Fish:
 
 ```bash
-# One-off session connect
-sesh connect "$(aw list | fzf)"
-```
-
-```bash
-# Bash keybind (Ctrl+S)
-bind '"\C-s":"sesh connect \$(aw list | fzf)\n"'
-```
-
-```zsh
-# Zsh keybind (Ctrl+S)
-bindkey -s '^s' 'sesh connect $(aw list | fzf)\n'
-```
-
-You can also use `aw switch --sesh` directly inside tmux to open the selected worktree in a new tmux window.
-
-`aw switch` checks managed contexts in this order: tmux → Herdr → cmux → integrated IDE → Kitty. Managed Kitty selection applies when any one of `KITTY_PID`, `KITTY_WINDOW_ID`, or `TERM=xterm-kitty` is present after normalization.
-
-Managed Kitty requires Kitty 0.43 or newer plus working `kitten @` remote control. Arashi reuses only its exact worktree marker and focuses that tab before launching a new session-backed tab. Once managed Kitty is selected, missing or unsupported tooling, denied remote control, duplicate markers, and validation failures are reported directly instead of falling back to another launcher.
-
-`aw create --launch` and `defaults.create.launch: "auto"` use the same managed Kitty behavior. If that post-create launch fails, Arashi exits nonzero but preserves the successfully created worktree and reports the launch as partial success. Fix the launcher problem and use `aw switch`; do not retry creation for the same branch.
-
-### Fast remove selection
-
-```bash
-# Select and remove a worktree quickly
-aw remove -f "$(aw list | fzf)"
-```
-
-If you prefer the term `delete`, create a shell alias:
-
-```bash
-alias arashi-delete='aw remove -f'
-```
-
-## Configuration Schema
-
-### Configured worktree files
-
-Configured repositories can copy isolated files or create native symlinks for intentionally shared state when coordinated worktrees are created. See [Worktree file materialization](docs/configuration.md#worktree-file-materialization) for direct `copy`/`symlink` arrays, Git-primary sourcing, lifecycle order, safety rules, dry-run previews, and doctor diagnostics.
-
-## Configuration Schema
-
-Arashi publishes a JSON Schema for `.arashi/config.json` so editors can validate and autocomplete your config.
-
-- Stable URL: `https://unpkg.com/arashi/schema/config.schema.json`
-- Version-pinned URL: `https://unpkg.com/arashi@1.7.0/schema/config.schema.json`
-
-Example config header:
-
-```json
-{
-  "$schema": "https://unpkg.com/arashi/schema/config.schema.json",
-  "version": "1.0.0",
-  "reposDir": "./repos",
-  "defaults": {
-    "create": {
-      "switch": true,
-      "launch": "none"
-    },
-    "editors": {
-      "vscode": {
-        "create": {
-          "launch": "sesh"
-        }
-      }
-    },
-    "switch": {
-      "mode": "sesh"
-    }
-  },
-  "repos": {}
-}
+aw shell install
 ```
 
-`defaults.switch.mode` accepts `auto` | `cd` | `launch` | `sesh` | `herdr`. Contextual `auto` checks strict managed contexts in the order tmux → Herdr → cmux → integrated IDE → managed Kitty, then uses parent-shell `cd` when shell integration is active, and otherwise follows terminal/platform launch fallback. An absent mode preserves the built-in automatic `launch` behavior rather than newly preferring `cd`.
-
-Explicit launcher flags take precedence over `--cd` / `--launch`, which take precedence over the configured mode and automatic context detection. `--launch` forces launch while preserving a configured launcher. `--ignore-configured-launcher` bypasses only configured `sesh` or `herdr`; combine both canonical flags to force generic automatic launch. `--herdr` remains available on both `create` and `switch`; Herdr launch uses `herdr worktree open` with the Git-resolved non-bare main checkout and selected worktree.
-
-Legacy switch-only `launchMode` and `launch_mode` fields remain readable for a bounded compatibility window. Arashi warns with the exact replacement `defaults.switch.mode` on stderr; migrate promptly. Ambiguous `cd` plus an explicit legacy launcher and conflicting legacy aliases are rejected.
-
-Use `defaults.create` for terminal `aw 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.
+You can then use `aw switch --cd <filter>` to change the current shell's directory. See the [shell command guide](https://arashi.haphazard.dev/commands/shell/) for manual setup.
 
-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.
+## More documentation
 
-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.
-
-Defaults precedence for unrelated switch behavior remains unchanged.
-
-## skills.sh Integration
-
-Arashi also ships a dedicated `skills.sh` integration package for guided installation, workflow examples, and troubleshooting.
-
-- Skill repository: [`repos/arashi-skills`](../arashi-skills/README.md)
-- Canonical skill manifest: [`repos/arashi-skills/skills/arashi/SKILL.md`](../arashi-skills/skills/arashi/SKILL.md)
-- Workflow catalog: [`repos/arashi-skills/skills/arashi/references/workflows.md`](../arashi-skills/skills/arashi/references/workflows.md)
-- Session shortcuts: [`repos/arashi-skills/skills/arashi/references/session-shortcuts.md`](../arashi-skills/skills/arashi/references/session-shortcuts.md)
-
-## Documentation
-
-- Installation details: [`docs/INSTALLATION.md`](./docs/INSTALLATION.md)
-- Configuration details: [`docs/configuration.md`](./docs/configuration.md)
-- Clone command details: [`docs/commands/clone.md`](./docs/commands/clone.md)
-- Hook behavior: [`docs/hooks.md`](./docs/hooks.md)
-- Workflow guides: [https://arashi.haphazard.dev/workflows/](https://arashi.haphazard.dev/workflows/)
-- Shell integration details: [`docs/commands/shell.md`](./docs/commands/shell.md)
-- Setup command details: [`docs/commands/setup.md`](./docs/commands/setup.md)
-- Switch command details: [`docs/commands/switch.md`](./docs/commands/switch.md)
-- Remove command details: [`docs/commands/remove.md`](./docs/commands/remove.md)
-- Push command details: [`docs/commands/push.md`](./docs/commands/push.md)
-- FZF integration: [`docs/FZF_COMPATIBILITY.md`](./docs/FZF_COMPATIBILITY.md)
+- [Getting started](https://arashi.haphazard.dev/getting-started/)
+- [Configuration](https://arashi.haphazard.dev/workflows/config/)
+- [Hooks](https://arashi.haphazard.dev/workflows/hooks/)
+- [Editor and terminal integrations](https://arashi.haphazard.dev/workflows/)
+- [JSON automation](https://arashi.haphazard.dev/workflows/json-automation/)
+- [Local configuration reference](./docs/configuration.md)
 
 ## Contributing
 
-Use the canonical guide: [`CONTRIBUTING.md`](./CONTRIBUTING.md).
-
-For specs and planning workflow, see the specs repository: [github.com/corwinm/arashi-arashi](https://github.com/corwinm/arashi-arashi).
+See [`CONTRIBUTING.md`](./CONTRIBUTING.md). Planning and specifications live in [corwinm/arashi-arashi](https://github.com/corwinm/arashi-arashi).
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arashi",
-  "version": "1.32.1",
+  "version": "1.34.0",
   "description": "Git worktree manager for meta-repositories - The eye of the storm for your development workflow",
   "keywords": [
     "cli",
@@ -110,5 +110,5 @@
   "engines": {
     "node": ">=18.0.0"
   },
-  "packageManager": "pnpm@11.20.0"
+  "packageManager": "pnpm@11.22.0"
 }

package/schema/config.schema.json

@@ -26,7 +26,7 @@
           "type": "string"
         },
         "baseBranch": {
-          "description": "Workspace base branch shared by configured create and clone",
+          "description": "Workspace base branch shared by configured base-aware commands",
           "minLength": 1,
           "pattern": "^(?!HEAD$)(?!origin/(?:HEAD$|-))(?![-/.])(?!.*(?:/\\.|//|\\.\\.|@\\{))(?!.*\\.lock(?:/|$))(?!.*[/.]$)[^\\u0000-\\u0020\\u007F~^:?*\\[\\\\]+$",
           "type": "string"
@@ -98,12 +98,6 @@
     "CreateCommandDefaults": {
       "additionalProperties": false,
       "properties": {
-        "baseBranch": {
-          "description": "Default base branch for configured create invocations",
-          "minLength": 1,
-          "pattern": "^(?!HEAD$)(?!origin/(?:HEAD$|-))(?![-/.])(?!.*(?:/\\.|//|\\.\\.|@\\{))(?!.*\\.lock(?:/|$))(?!.*[/.]$)[^\\u0000-\\u0020\\u007F~^:?*\\[\\\\]+$",
-          "type": "string"
-        },
         "launch": {
           "$ref": "#/definitions/CreateLaunchMode",
           "description": "Post-create launch choice; omitted preserves built-in no-launch behavior"
@@ -223,7 +217,7 @@
       "description": "Meta-repository-specific configuration.",
       "properties": {
         "baseBranch": {
-          "description": "Meta-repository-specific base branch for configured create",
+          "description": "Meta-repository-specific base branch for configured base-aware commands",
           "minLength": 1,
           "pattern": "^(?!HEAD$)(?!origin/(?:HEAD$|-))(?![-/.])(?!.*(?:/\\.|//|\\.\\.|@\\{))(?!.*\\.lock(?:/|$))(?!.*[/.]$)[^\\u0000-\\u0020\\u007F~^:?*\\[\\\\]+$",
           "type": "string"
@@ -236,7 +230,7 @@
       "description": "Configuration for a single repository",
       "properties": {
         "baseBranch": {
-          "description": "Repository-specific base branch for configured create and clone",
+          "description": "Repository-specific base branch for configured base-aware commands",
           "minLength": 1,
           "pattern": "^(?!HEAD$)(?!origin/(?:HEAD$|-))(?![-/.])(?!.*(?:/\\.|//|\\.\\.|@\\{))(?!.*\\.lock(?:/|$))(?!.*[/.]$)[^\\u0000-\\u0020\\u007F~^:?*\\[\\\\]+$",
           "type": "string"