forktreev0.1.0

A CI pipeline creates ephemeral worktrees per test shard so parallel jobs never collide on the same checkout. Each job captures `forktree create` stdout into a variable, cds into the path, runs its shard, then relies on `gc` to reap stale worktrees by age. Strict exit codes let the pipeline distinguish preflight refusals from git failures without parsing logs.

An autonomous coding agent spins up a fresh worktree before each task so experimental edits never touch the user's main checkout. Because stdout is pure data, the agent captures the worktree path directly and routes diagnostics to a log file. If `create` exits non-zero, the agent reads stderr and abandons the task rather than retrying blindly.

A review bot materializes a worktree per pull request so multiple diffs can be built and tested concurrently on one machine. It uses `list --json` to enumerate active worktrees and `remove --force-if-lossless` to clean up after merges. The TOML config pins base paths and setup scripts for reproducibility.

Developers run `forktree init` once to generate `.forktree.toml`, then `create` a worktree per branch under test without disturbing the primary clone. `list --porcelain` feeds shell completions and status prompts, while `gc --dry-run` previews what would be cleaned before committing. This keeps laptops tidy across many concurrent branches.

A regulated build system uses forktree to carve out short-lived worktrees that are destroyed automatically by the setup hook's teardown-on-failure behavior. Every `create` refusal is logged with the exact `forktree: <subcommand>: <reason>` stderr line for audit trails. Garbage collection ensures no stale source trees persist past their policy window.

The forktree CLI remains free and stdlib-only while a paid control plane manages worktree lifecycles across fleets of agents and CI runners. The hosted layer adds dashboards, audit logs, and policy enforcement for `gc` and setup hooks. Teams adopt the OSS CLI bottom-up, then upgrade when coordination becomes painful.

forktree is packaged inside an agent runtime sold to AI coding startups that need safe, isolated git checkouts out of the box. Licensing is per-organization, with the CLI acting as the wedge into broader sandboxing and environment-management products. The strict stdout/stderr contract makes it trivially embeddable in any pipeline.

Enterprises with sprawling monorepos pay for engagements that wire forktree into Jenkins, GitHub Actions, or internal build systems with custom TOML configs and setup scripts. Deliverables include hardened gc policies, strict-mode configs, and runbooks for exit-code handling. Recurring retainers cover ongoing tuning as repos grow.