Harness Persist

Persist only context that improves agent continuity and does not belong in canonical developer docs. Do not write conversational history.

Resolve the harness with harness-init's bundled scripts/resolve_harness.py <project-root>. Never assume the destination is <checkout>/.project-harness; in Git it lives under the common directory and survives removal of an individual worktree.

Classification

First classify ownership:

• Stable knowledge useful to developers and agents: use README.md or docs/ through docs-maintain.
• Operational, provisional, investigative, or handoff context: choose a harness destination below.
• Overlap: make versioned docs canonical and retain only a pointer plus local context in the harness.

Harness destinations: