using-git-worktrees

1# Using Git Worktrees
2 
3## Overview
4 
5A worktree is an exception for simultaneously checking out another Git history,
6not a general safety badge. Prefer the current workspace and reuse an existing
7suitable worktree. A branch decision and a worktree decision are separate.
8 
9**Core principle:** create only with necessity and ownership evidence; pair every
10created worktree with a cleanup path.
11 
12**Announce at start:** explain which concrete checkout conflict requires a
13worktree.
14 
15## Step 0: Environment Detection
16 
17Before mutation, record the repository root, `HEAD`, branch/detached state,
18staged/unstaged/untracked paths, active Git operations, and:
19 
20```bash
21git worktree list --porcelain
22```
23 
24Classify the current host surface's task/chat-bound managed workspace semantics
25as `managed`, `non-managed`, or `unknown`. Use trusted host/session context, an
26explicit host contract, or a host-native lifecycle result; do not infer the
27classification from a product name, directory prefix, command-level `workdir`,
28missing tool, or absent metadata. `non-managed` requires positive evidence that
29the current surface lacks task-bound managed semantics. When the host exposes
30workspace fields, record the task workspace and the command's default `cwd`
31without a per-command directory override.
32 
33Stop on unresolved conflicts, an active merge/rebase/cherry-pick/revert/bisect,
34or an unexplained detached HEAD. A detached HEAD is acceptable only when
35…