harness-gc

To fix documentation drift, you can run an automated harness cleanup check to audit AGENTS.md references and docs alignment. This process identifies dead references and generates a prioritized remediation plan to repair inconsistencies across the repository.

Detecting stalled in_progress features requires auditing feature integrity through features.json. This automated cleanup process identifies broken circuit states and suggests or applies resets to restore healthy execution progress.

Identifying architecture layer violations involves auditing architectural drift across the harness. This cleanup action detects dead context and layer violations, enabling safer refactors and maintaining architectural discipline.

Yes, you can automate repository cleanup by running a harness-gc check that scans AGENTS.md, docs/, and features.json together. It produces a prioritized cleanup plan and executes agent-led fixes across the harness over time.

Harness cleanup works for typical agent-first projects without requiring external dependencies. It centrally coordinates automated cleanup by implementing checks, resets, and archival actions that satisfy safety and reproducibility requirements.

You should run harness cleanup when entropy accumulates as documentation, feature states, and architecture drift diverge from reality. It restores consistency, reduces cognitive load, and keeps agents properly oriented through prioritized remediation reports.