Harness Audit

Audit the harness for shared location, migration state, size, routing, and stale sessions.

Procedure

Run scripts/check_harness.py <project-root> --strict. The script resolves the Git-common harness; do not construct a checkout-local path.
Read reported files only when needed to fix the issue.
Prefer consolidation over deletion.
Do not remove user content unless the user explicitly asks.
Verify that active sessions contain worktree and worktree_id and that .project-harness is no longer tracked.
Compare likely stable guidance with README.md and docs/; recommend promotion or replacement with a pointer when the harness is acting as a second source of truth.

Use --format json for structured findings. Structural issues always fail; warnings fail only with --strict.