Harness Worktree

Apply a Harness-controlled creation protocol and lifecycle while using the active host's storage convention. Harness owns branch naming, base selection, creation, isolation, validation, adoption, reuse, and retirement. The host owns only the physical checkout path, storage layout, and native bookkeeping required to integrate that path.

Plan a Worktree

1. Read applicable repository instructions and identify the task's primary intent.

2. Choose an allowed Conventional Commit type and translate the task into a short English kebab-case slug. Read references/worktrees.md when classification or collision behavior is unclear.

3. Run:

   python3 scripts/resolve_branch.py \
     --project <checkout> \
     --type <type> \
     --slug "<short English description>" \
     --require-available