repo-harness-repair

# repo-harness-repair Use this command when the repo has a harness but a specific workflow surface is broken. ## Protocol 1. Reproduce the failure and name the failing surface. 2. Run `bun scripts/inspect-project-state.ts --repo <repo> --format text`. 3. Trace the failing path, such as `settings.json -> repo-harness-hook -> route registry -> typed handler` or `plans/ -> tasks/todos.md -> tasks/contracts/`. 4. Apply the smallest targeted fix. 5. Re-run the failing check and the relevant workflow gate. ## Failure Modes - If the repo lacks a current harness, route to `repo-harness-init` or `repo-harness-migrate`. - If the broken path is release readiness, route to `repo-harness-check`. - If the failure cannot be reproduced, report the missing evidence and stop before editing. ## Boundaries - Do not use repair to migrate a legacy repo; route legacy contract drift to `repo-harness-migrate`. - Do not use repair to scaffold product code. - Preserve unrelated dirty worktree changes.