harness-maintenance

What problem does it solve?

Enforce and maintain repository infrastructure hygiene to prevent documentation rot, configuration drift, and test decay by ensuring architectural decisions, hooks, linters, and diagnostic checks are created and executed consistently.

Core Features & Use Cases

• ADR Strict Enforcement: Require creation of ADRs for all architectural decisions, dependency changes, and pattern shifts and store them in docs/adr before proceeding.
• Hook Integrity: Preserve and restore local hooks in .claude/settings.json and refuse to bypass or weaken hook protections; repair code to satisfy hooks.
• Doctor Loop & Remediation: Run task harness:doctor at the end of every task or session, surface issues, and require immediate fixes before commit.
• Linter Primacy & Config Protection: Enforce Biome lint rules (e.g., noExplicitAny: error) and treat biome.json, Taskfile.yml, and .claude/settings.json as immutable unless the harness itself is being evolved.
• Use Case: Use when making structural changes, dependency upgrades, CI/hook adjustments, or completing task sessions to ensure long-term repository health.

Quick Start

Ask the assistant to validate the repository harness by creating any missing ADRs, running task harness:doctor, and fixing all reported issues.