worktrees

# Worktrees Manage `.oh/worktrees/`. Full policy: `/git` § Worktrees; `.oh/context/rules/git.md` is only a compatibility pointer. ## CHANGE ROUTING — TRACK VS RESET `~/harness` and `$WORKTREES_ROOT/project/<owner>/<repo>` are different Git boundaries. The parent harness ignores the latter; a project clone's files are never changes to the harness. Classify changes before committing, resetting, or removing anything. A dirty checkout is not disposable merely because it lives under `.oh/worktrees/`. ### `~/harness` — harness control plane **Track/preserve** deliberate, durable harness changes, including: - `.oh/skills/`, `.oh/agents/`, `.oh/hooks/`, `.oh/scripts/`, `.devcontainer/`, `.github/`, `workspace/`, docs, templates, and supported configuration defaults. - `.oh/worktrees/README.md` and other lifecycle documentation. - Curated wiki entries and the wiki index when intentionally promoted. The wiki corpus is ignored by default; use `git add -f` only for reviewed entries. Never promote `corpus/raw/` snapshots by accident. - A handoff only when it is deliberately shared, scrubbed of secrets, and meant to be durable in this harness checkout or its private operator fork. **Reset/remove** only known local, generated, or abandoned state, such as: - worktree contents, task progress, memory/log state, plans/spec scratch, screenshots, build output, dependencies, local env/auth files, and caches covered by `.gitignore`; - an explicit operator-local setting or a tr...