workforest 0.2.2__tar.gz → 0.3.0__tar.gz

workforest-0.3.0/.claude/rules/architecture.md

@@ -0,0 +1,16 @@
+# Architecture invariants
+
+- `gitutil.py` is the only module that spawns git. Consumers get typed
+  results; worktree data comes from `--porcelain -z` output, never from
+  parsing the human-readable form.
+- `cli.py` is the sole stdout writer. Commands return
+  `ShellAction | str | None`; stdout carries the shell-wrapper cd protocol,
+  so nothing else may print there (hook/script stdout is diverted to stderr).
+- `tui.py`: everything except the fzf subprocess is pure and unit-tested;
+  fzf is the only sanctioned external tool there.
+- `completions.py` must never break the shell: any error yields an empty
+  candidate list, and output stays plain `NAME<TAB>ANNOTATION` lines.
+- `integrations/claude.py` is experimental: it reads Claude Code's private
+  on-disk state. Session lines are rewritten by JSON parsing, never by
+  string substitution.
+- README.md is the project reference; there is no separate design document.

workforest-0.3.0/.claude/rules/conventions.md

@@ -0,0 +1,12 @@
+# Code conventions
+
+- Python 3.14, uv-managed. Verify changes with `make check` (ruff lint +
+  format check, mypy, pytest with a 90% coverage floor). Run
+  `uv run ruff format .` rather than hand-formatting.
+- When a return value or constant bundles fields whose positions carry
+  meaning, use a small named dataclass — `@dataclass(slots=True,
+  frozen=True)` — not an anonymous tuple or nested dict. Plain dicts are for
+  genuine key→value lookups only (env maps, branch→remotes).
+- Pre-1.0 with zero users: on breaking changes keep the clean design and
+  state what to re-run (e.g. re-eval shell-init). Never add
+  backward-compatibility shims.

workforest-0.3.0/.claude/rules/tests.md

@@ -0,0 +1,17 @@
+---
+paths:
+  - "tests/**/*.py"
+---
+
+# Test conventions
+
+- Isolation contract (see `tests/conftest.py`): no test may read or write
+  the real environment. The autouse `isolated_env` fixture redirects HOME,
+  XDG_CONFIG_HOME, and git config, and pins SHELL=/bin/sh, EDITOR, and
+  NO_COLOR — rely on it instead of patching these per test.
+- Build repos through the `repo` / `make_repo` fixtures and the `Repo`
+  helper methods (`add_branch`, `add_remote`, `write_project_config`,
+  `make_dirty`) rather than raw git calls.
+- Coverage floor is 90% (`--cov-fail-under=90` in pyproject.toml); pure
+  helpers are expected to be unit-tested, subprocess/terminal glue may be
+  `# pragma: no cover`.

{workforest-0.2.2 → workforest-0.3.0}/.github/workflows/publish_aur.yml

@@ -12,7 +12,7 @@ jobs:
       name: aur
       url: https://aur.archlinux.org/packages/workforest
     permissions:
-      contents: write  # commit the generated PKGBUILD back to main
+      contents: read
     steps:
       - name: Install system dependencies
         run: >
@@ -21,15 +21,15 @@ jobs:
 
       - uses: actions/checkout@v4
 
-      - name: Update PKGBUILD to released version
+      - name: Render PKGBUILD from template
         run: |
           version="${GITHUB_REF_NAME#v}"
           cd packaging/AUR
-          sed -i "s/^pkgver=.*/pkgver=$version/" PKGBUILD
-          sed -i "s/^pkgrel=.*/pkgrel=1/" PKGBUILD
+          sed "s/@VERSION@/$version/g" PKGBUILD.template > PKGBUILD
           # makepkg refuses to run as root
           useradd -m builder
           chown -R builder .
+          # updpkgsums replaces the @SHA256@ placeholder with the real checksum
           runuser -u builder -- updpkgsums
           runuser -u builder -- sh -c 'makepkg --printsrcinfo > .SRCINFO'
 
@@ -70,24 +70,3 @@ jobs:
             git commit -m "Update to $version"
             git push origin HEAD:master
           fi
-
-      - name: Commit generated PKGBUILD back to main
-        run: |
-          version="${GITHUB_REF_NAME#v}"
-          cp packaging/AUR/PKGBUILD packaging/AUR/.SRCINFO /tmp/
-          # The workspace is created by the host runner under a different UID
-          # than the container's root, so git rejects it without this.
-          git config --global --add safe.directory "$GITHUB_WORKSPACE"
-          # The workflow runs detached at the release tag; move to main to commit.
-          # -f discards the in-place edits we just copied to /tmp; build
-          # artifacts in packaging/AUR are untracked and never git-added.
-          git fetch origin main
-          git checkout -f -B main origin/main
-          cp /tmp/PKGBUILD /tmp/.SRCINFO packaging/AUR/
-          git add packaging/AUR/PKGBUILD packaging/AUR/.SRCINFO
-          if git diff --cached --quiet; then
-            echo "Repo copy already up to date."
-          else
-            git commit -m "Update PKGBUILD to $version"
-            git push origin main
-          fi

{workforest-0.2.2 → workforest-0.3.0}/.github/workflows/publish_homebrew.yml

@@ -3,32 +3,43 @@ name: Publish to Homebrew tap
 on:
   release:
     types: [published]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Release version to publish (e.g. 0.2.1)"
+        required: true
 
 jobs:
   publish:
     runs-on: macos-latest
+    env:
+      RELEASE_VERSION: ${{ github.event_name == 'workflow_dispatch' && inputs.version || github.ref_name }}
     environment:
       name: homebrew-tap
       url: https://github.com/ArkadyBuryakov/homebrew-tap
     permissions:
-      contents: write  # commit the generated formula back to main
+      contents: read
     steps:
       - uses: actions/checkout@v4
 
-      - name: Update formula to released version
+      - name: Render formula from template
         run: |
-          version="${GITHUB_REF_NAME#v}"
+          version="${RELEASE_VERSION#v}"
           url="https://github.com/ArkadyBuryakov/workforest/archive/v$version.tar.gz"
           curl -fsSL "$url" -o /tmp/workforest.tar.gz
           sha256=$(shasum -a 256 /tmp/workforest.tar.gz | cut -d' ' -f1)
           cd packaging/homebrew
-          sed -i '' "s|^  url .*|  url \"$url\"|" workforest.rb
-          sed -i '' "s|^  sha256 .*|  sha256 \"$sha256\"|" workforest.rb
+          sed -e "s/@VERSION@/$version/g" -e "s/@SHA256@/$sha256/g" \
+            workforest.rb.template > workforest.rb
 
       - name: Build, test, and smoke test
         run: |
-          brew install --build-from-source --formula packaging/homebrew/workforest.rb
-          brew test --formula packaging/homebrew/workforest.rb
+          # Homebrew >= 4.6.4 refuses to install from a bare file path —
+          # formulas must live in a tap, so stage ours in a throwaway one.
+          brew tap-new --no-git arkadyburyakov/test
+          cp packaging/homebrew/workforest.rb "$(brew --repository arkadyburyakov/test)/Formula/"
+          brew install --build-from-source arkadyburyakov/test/workforest
+          brew test arkadyburyakov/test/workforest
           workforest --version
           wf --version
           workforest shell-init bash | bash -n
@@ -38,7 +49,7 @@ jobs:
         env:
           TAP_SSH_PRIVATE_KEY: ${{ secrets.TAP_SSH_PRIVATE_KEY }}
         run: |
-          version="${GITHUB_REF_NAME#v}"
+          version="${RELEASE_VERSION#v}"
           # Host keys are pinned rather than keyscanned (same policy as the
           # AUR workflow); these are GitHub's published SSH fingerprints.
           mkdir -p /tmp/ssh
@@ -63,29 +74,3 @@ jobs:
             git commit -m "workforest $version"
             git push origin main
           fi
-
-      - name: Commit generated formula back to main
-        run: |
-          version="${GITHUB_REF_NAME#v}"
-          cp packaging/homebrew/workforest.rb /tmp/workforest.rb
-          git config --global user.name "Arkady Buryakov"
-          git config --global user.email "arkady@buryakov.pro"
-          # The workflow runs detached at the release tag; move to main to
-          # commit. Retry because the AUR publisher pushes to main from the
-          # same release event and the two can race.
-          for attempt in 1 2 3; do
-            git fetch origin main
-            git checkout -f -B main origin/main
-            cp /tmp/workforest.rb packaging/homebrew/workforest.rb
-            git add packaging/homebrew/workforest.rb
-            if git diff --cached --quiet; then
-              echo "Repo copy already up to date."
-              break
-            fi
-            git commit -m "Update Homebrew formula to $version"
-            if git push origin main; then
-              break
-            fi
-            echo "Push raced with another workflow, retrying ($attempt)..."
-            sleep 10
-          done

{workforest-0.2.2 → workforest-0.3.0}/.gitignore

@@ -13,9 +13,12 @@ build/
 .coverage
 htmlcov/
 
-# Packaging artifacts
+# Packaging artifacts (rendered from *.template at release time)
 *.pkg.tar.zst
 pkg/
+packaging/AUR/PKGBUILD
+packaging/AUR/.SRCINFO
+packaging/homebrew/workforest.rb
 
 # Tooling config
 .workforest.yaml

{workforest-0.2.2 → workforest-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: workforest
-Version: 0.2.2
+Version: 0.3.0
 Summary: Git worktree forest management: create, open, and clean up per-branch worktrees with project-defined setup hooks
 Project-URL: Homepage, https://github.com/ArkadyBuryakov/workforest
 Author-email: Arkady Buryakov <arkady@buryakov.pro>
@@ -20,6 +20,14 @@ Description-Content-Type: text/markdown
 
 # Workforest
 
+## Elevator pitch
+
+Your repo has one working directory; your AI agents want five. Workforest
+gives every feature — and every agent — its own disposable git worktree, so
+parallel work on the same repo never collides.
+
+## About
+
 Git worktree forest management: one main checkout plus any number of
 disposable, per-branch worktrees in a predictable location — created, set up,
 opened, and cleaned up with one command.
@@ -108,17 +116,17 @@ All keys, with defaults:
 ```yaml
 worktrees_dir: "$WF_MAIN/../worktrees/$WF_NAME"  # where the forest lives
 opener: ""              # default opener; "" → $VISUAL → $EDITOR
-openers: {}             # name -> command template, e.g. edit: "$EDITOR {target}"
-window_command: ""      # "" → current shell; or e.g.
-                        # "kitty --title {title} --directory {worktree} $WF_COMMAND"
+openers: {}             # name -> shell command, e.g. edit: '$EDITOR "$WF_TARGET"'
+window_command: ""      # "" → current shell; or e.g. kitty --title "$WF_TITLE"
+                        #   --directory "$WF_WORKTREE" $SHELL -c "$WF_COMMAND"
 symlinks: []            # untracked assets linked from main into new worktrees
 setup_scripts: []       # shell snippets run in a fresh worktree
 scripts: {}             # name -> snippet for `wf run NAME`
 ```
 
-Openers and `window_command` are command templates sharing one variable
-family, which the launched process (and every script) also receives as
-environment variables:
+Openers and `window_command` are plain shell commands, run via `$SHELL -c`
+with one variable family in the environment — the same family the launched
+process and every script receive:
 
 | Variable | Value |
 |---|---|
@@ -130,13 +138,17 @@ environment variables:
 | `WF_TARGET` | the `-p` argument, default `.` (launch-only) |
 | `WF_TITLE` | window label, `project_name: feat-x` (launch-only) |
 
-In templates, `$WF_X` (like any `$ENV` variable) inserts raw text that
-word-splits into multiple arguments, while `{x}` — `{worktree}`, `{target}`,
-`{title}`, … — inserts the shell-quoted value as exactly one argument.
-Openers run with the worktree root as working directory; in
-`window_command` the resolved opener command is additionally available as
-`$WF_COMMAND` (spliced into argv words) or `{command}` (one argument, for
-`$SHELL -c` wrappers).
+Standard shell rules apply — there is no workforest template syntax:
+`"$WF_X"` is exactly one argument, bare `$WF_X` word-splits, and `$$`,
+braces, pipes, and `&&` mean whatever your shell says they mean (a
+misspelled `$WF_VAR` expands to empty, as in any shell). Openers run with
+the worktree root as working directory. In `window_command` the resolved
+opener command is additionally available as `$WF_COMMAND` — still
+unexpanded, so run it through a shell of its own for its `$WF_*` references
+to resolve: `$SHELL -c "$WF_COMMAND"`. Spawned windows shed activation
+state inherited from the invoking shell (Python venv, conda, nvm, rvm) so
+the new session starts clean instead of carrying an environment it cannot
+deactivate.
 
 Fully commented reference configs:
 [`config.yaml`](src/workforest/examples/config.yaml) (user/system) and
@@ -185,8 +197,23 @@ workforest tui    [MODE]
 workforest init   [--local]
 workforest config [--json]
 workforest shell-init [bash|zsh]
+workforest claude copy-session SESSION_ID   # experimental
 ```
 
+`open` (and the opener shortcut, e.g. `wf edit`) without NAME opens the
+worktree you are standing in.
+
+`create` resolves BRANCH in order: existing local branch, then a branch on
+exactly one remote (checked out tracking it), then a brand-new branch.
+`REMOTE/BRANCH` picks the remote explicitly — needed when several remotes
+carry the same branch name; if that local name is already taken, `create`
+prompts for a different one.
+
+`workforest claude` (shown only when `~/.claude` exists) copies a Claude
+Code session from the main worktree into the current one. It is
+**experimental**: it manipulates Claude Code's private on-disk state,
+which is not a stable interface, so any Claude Code update may break it.
+
 Exit codes: `0` ok · `1` error · `2` usage · `3` cancelled · `4` config error.
 Human messages go to stderr; stdout carries only machine output (`cd`
 directives for the `wf` wrapper, `--porcelain` listings, dumps).
@@ -200,12 +227,13 @@ make install      # install this checkout as a uv tool (~/.local/bin/workforest)
 make uninstall    # remove it again
 ```
 
-Packaging recipes live under `packaging/` (one directory per package
-manager: `packaging/AUR/`, `packaging/homebrew/`).
-Release: bump `__version__` and push to main — CI tags the release and
-publishes to PyPI, the AUR, and the
-[Homebrew tap](https://github.com/ArkadyBuryakov/homebrew-tap), committing
-the regenerated recipes back to the repo.
+Packaging templates live under `packaging/` (one directory per package
+manager: `packaging/AUR/`, `packaging/homebrew/`); the `@VERSION@` and
+`@SHA256@` placeholders are filled in at release time.
+Release: bump `__version__` and push to main — CI tags the release,
+renders the templates, and publishes to PyPI, the AUR, and the
+[Homebrew tap](https://github.com/ArkadyBuryakov/homebrew-tap). The
+published AUR package and tap are the only places rendered recipes exist.
 
 ## License
 

{workforest-0.2.2 → workforest-0.3.0}/README.md

@@ -1,5 +1,13 @@
 # Workforest
 
+## Elevator pitch
+
+Your repo has one working directory; your AI agents want five. Workforest
+gives every feature — and every agent — its own disposable git worktree, so
+parallel work on the same repo never collides.
+
+## About
+
 Git worktree forest management: one main checkout plus any number of
 disposable, per-branch worktrees in a predictable location — created, set up,
 opened, and cleaned up with one command.
@@ -88,17 +96,17 @@ All keys, with defaults:
 ```yaml
 worktrees_dir: "$WF_MAIN/../worktrees/$WF_NAME"  # where the forest lives
 opener: ""              # default opener; "" → $VISUAL → $EDITOR
-openers: {}             # name -> command template, e.g. edit: "$EDITOR {target}"
-window_command: ""      # "" → current shell; or e.g.
-                        # "kitty --title {title} --directory {worktree} $WF_COMMAND"
+openers: {}             # name -> shell command, e.g. edit: '$EDITOR "$WF_TARGET"'
+window_command: ""      # "" → current shell; or e.g. kitty --title "$WF_TITLE"
+                        #   --directory "$WF_WORKTREE" $SHELL -c "$WF_COMMAND"
 symlinks: []            # untracked assets linked from main into new worktrees
 setup_scripts: []       # shell snippets run in a fresh worktree
 scripts: {}             # name -> snippet for `wf run NAME`
 ```
 
-Openers and `window_command` are command templates sharing one variable
-family, which the launched process (and every script) also receives as
-environment variables:
+Openers and `window_command` are plain shell commands, run via `$SHELL -c`
+with one variable family in the environment — the same family the launched
+process and every script receive:
 
 | Variable | Value |
 |---|---|
@@ -110,13 +118,17 @@ environment variables:
 | `WF_TARGET` | the `-p` argument, default `.` (launch-only) |
 | `WF_TITLE` | window label, `project_name: feat-x` (launch-only) |
 
-In templates, `$WF_X` (like any `$ENV` variable) inserts raw text that
-word-splits into multiple arguments, while `{x}` — `{worktree}`, `{target}`,
-`{title}`, … — inserts the shell-quoted value as exactly one argument.
-Openers run with the worktree root as working directory; in
-`window_command` the resolved opener command is additionally available as
-`$WF_COMMAND` (spliced into argv words) or `{command}` (one argument, for
-`$SHELL -c` wrappers).
+Standard shell rules apply — there is no workforest template syntax:
+`"$WF_X"` is exactly one argument, bare `$WF_X` word-splits, and `$$`,
+braces, pipes, and `&&` mean whatever your shell says they mean (a
+misspelled `$WF_VAR` expands to empty, as in any shell). Openers run with
+the worktree root as working directory. In `window_command` the resolved
+opener command is additionally available as `$WF_COMMAND` — still
+unexpanded, so run it through a shell of its own for its `$WF_*` references
+to resolve: `$SHELL -c "$WF_COMMAND"`. Spawned windows shed activation
+state inherited from the invoking shell (Python venv, conda, nvm, rvm) so
+the new session starts clean instead of carrying an environment it cannot
+deactivate.
 
 Fully commented reference configs:
 [`config.yaml`](src/workforest/examples/config.yaml) (user/system) and
@@ -165,8 +177,23 @@ workforest tui    [MODE]
 workforest init   [--local]
 workforest config [--json]
 workforest shell-init [bash|zsh]
+workforest claude copy-session SESSION_ID   # experimental
 ```
 
+`open` (and the opener shortcut, e.g. `wf edit`) without NAME opens the
+worktree you are standing in.
+
+`create` resolves BRANCH in order: existing local branch, then a branch on
+exactly one remote (checked out tracking it), then a brand-new branch.
+`REMOTE/BRANCH` picks the remote explicitly — needed when several remotes
+carry the same branch name; if that local name is already taken, `create`
+prompts for a different one.
+
+`workforest claude` (shown only when `~/.claude` exists) copies a Claude
+Code session from the main worktree into the current one. It is
+**experimental**: it manipulates Claude Code's private on-disk state,
+which is not a stable interface, so any Claude Code update may break it.
+
 Exit codes: `0` ok · `1` error · `2` usage · `3` cancelled · `4` config error.
 Human messages go to stderr; stdout carries only machine output (`cd`
 directives for the `wf` wrapper, `--porcelain` listings, dumps).
@@ -180,12 +207,13 @@ make install      # install this checkout as a uv tool (~/.local/bin/workforest)
 make uninstall    # remove it again
 ```
 
-Packaging recipes live under `packaging/` (one directory per package
-manager: `packaging/AUR/`, `packaging/homebrew/`).
-Release: bump `__version__` and push to main — CI tags the release and
-publishes to PyPI, the AUR, and the
-[Homebrew tap](https://github.com/ArkadyBuryakov/homebrew-tap), committing
-the regenerated recipes back to the repo.
+Packaging templates live under `packaging/` (one directory per package
+manager: `packaging/AUR/`, `packaging/homebrew/`); the `@VERSION@` and
+`@SHA256@` placeholders are filled in at release time.
+Release: bump `__version__` and push to main — CI tags the release,
+renders the templates, and publishes to PyPI, the AUR, and the
+[Homebrew tap](https://github.com/ArkadyBuryakov/homebrew-tap). The
+published AUR package and tap are the only places rendered recipes exist.
 
 ## License
 

workforest-0.3.0/completions/_workforest

@@ -0,0 +1,44 @@
+#compdef workforest wf
+# zsh completion for workforest / wf — installed to zsh site-functions.
+# Dynamic candidates are delegated to `workforest --complete TOPIC`.
+
+local topic cmd line name rest kind desc
+local -a items cmds
+cmd="${words[2]:-}"
+if (( CURRENT == 2 )); then
+    topic=commands
+else
+    case "$cmd" in
+        create) topic=branches ;;
+        open|delete|checkout) topic=worktrees ;;
+        run) topic=scripts ;;
+        claude) topic=claude-sessions ;;
+        tui|list|init|config|shell-init) topic=none ;;
+        *) topic=worktrees ;;
+    esac
+fi
+if [[ "$topic" != none ]]; then
+    items=(${(f)"$(workforest --complete "$topic" 2>/dev/null)"})
+    if [[ "$topic" == commands ]]; then
+        # NAME<TAB>KIND<TAB>DESCRIPTION → described candidates; one group
+        # (kind spelled out in the description) so list order, alignment,
+        # and the command/opener distinction survive fzf-tab's merging.
+        # Cyan for openers, but only under fzf-tab (fzf renders ANSI with
+        # --ansi; plain complist would print the escapes literally).
+        local pre="" post=""
+        if (( ${+functions[fzf-tab-complete]} )); then
+            pre=$'\e[36m' post=$'\e[0m'
+        fi
+        for line in "${items[@]}"; do
+            name="${line%%$'\t'*}"
+            rest="${line#*$'\t'}"
+            kind="${rest%%$'\t'*}"
+            desc="${rest#*$'\t'}"
+            [[ "$kind" == opener ]] && desc="${pre}opener: ${desc}${post}"
+            cmds+=("${name//:/\\:}:${desc}")
+        done
+        (( ${#cmds} )) && _describe -t commands 'workforest command' cmds
+    else
+        (( ${#items} )) && compadd -a items
+    fi
+fi

workforest-0.2.2/packaging/AUR/PKGBUILD → workforest-0.3.0/packaging/AUR/PKGBUILD.template

@@ -1,6 +1,10 @@
 # Maintainer: Arkady Buryakov <arkady@buryakov.pro>
+#
+# Template — not a buildable PKGBUILD. On release the publish_aur workflow
+# substitutes @VERSION@, fills sha256sums via updpkgsums, generates .SRCINFO,
+# and pushes the rendered files to the AUR; nothing is committed back here.
 pkgname=workforest
-pkgver=0.2.1
+pkgver=@VERSION@
 pkgrel=1
 pkgdesc="Git worktree forest management: per-branch worktrees with project-defined setup hooks"
 arch=(any)
@@ -10,7 +14,7 @@ depends=(python python-yaml git)
 makedepends=(python-build python-installer python-wheel python-hatchling)
 optdepends=('fzf: interactive TUI (workforest tui)')
 source=("$pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz")
-sha256sums=('47062e51ae374a9afce50ee0be6c39b08da6c96064450b3c2c58566d05fb7078')
+sha256sums=('@SHA256@')
 
 build() {
   cd "$pkgname-$pkgver"

workforest-0.2.2/packaging/homebrew/workforest.rb → workforest-0.3.0/packaging/homebrew/workforest.rb.template

@@ -1,13 +1,15 @@
-# The publish_homebrew workflow rewrites url/sha256 on release and pushes
-# this file to the ArkadyBuryakov/homebrew-tap repo; this copy is the source
-# of truth for everything else (deps, completions, caveats, test).
+# Template — not an installable formula. On release the publish_homebrew
+# workflow substitutes @VERSION@ and @SHA256@ and pushes the rendered
+# Formula/workforest.rb to the ArkadyBuryakov/homebrew-tap repo; nothing is
+# committed back here. This copy is the source of truth for everything else
+# (deps, completions, caveats, test).
 class Workforest < Formula
   include Language::Python::Virtualenv
 
   desc "Git worktree forest management with per-branch setup hooks"
   homepage "https://github.com/ArkadyBuryakov/workforest"
-  url "https://github.com/ArkadyBuryakov/workforest/archive/v0.2.1.tar.gz"
-  sha256 "47062e51ae374a9afce50ee0be6c39b08da6c96064450b3c2c58566d05fb7078"
+  url "https://github.com/ArkadyBuryakov/workforest/archive/v@VERSION@.tar.gz"
+  sha256 "@SHA256@"
   license "MIT"
   head "https://github.com/ArkadyBuryakov/workforest.git", branch: "main"
 

{workforest-0.2.2 → workforest-0.3.0}/src/workforest/__init__.py

@@ -1,3 +1,3 @@
 """Workforest — git worktree forest management."""
 
-__version__ = "0.2.2"
+__version__ = "0.3.0"