Harness Init

Create or repair one harness outside every checkout. In Git repositories, store it at <git-common-dir>/project-harness/; linked worktrees share consolidated knowledge while sessions retain worktree identity. Outside Git, use $PROJECT_HARNESS_HOME or an XDG/user-data fallback keyed by project path. Canonical project knowledge belongs in README.md and docs/.

Procedure

1. Identify the project root or current worktree.
2. Run scripts/init_harness.py <project-root>.
3. Read the printed shared path. Do not assume .project-harness/ exists in the checkout.
4. Inspect migration reports and backup paths. The script copies every legacy worktree harness before merging, never overwrites differing content, and places conflicts under references/migrations/.
5. Remove or untrack a legacy .project-harness/ only after verifying the shared copy and backup. Never delete tracked or modified user content as part of initialization.
6. Run scripts/resolve_harness.py <project-root> --format json whenever another tool needs the location.

Harness Layout