harden-harness

What problem does it solve?

The harness-hardening stage identifies why a routed orchestration failed (misroute, no-route, hook errors, or process-friction) and autonomously implements fixes under full gates, while surfacing contract forks via NEEDS_INPUT.md and never touching the target repository’s source code.

Core Features & Use Cases

• Fires in five situations: misroute (validate-deny), no-route, inject-hook error, process-friction, and manual invocation, enabling rapid hardening without manual rework.
• Reconstructs the exact divergence point from denied prompts, probe data, and registry state to guide root-cause analysis and decision-making.
• Enforces governance by self-recursion guards, clear root-cause classification, and gated mechanical fixes with full test and lint checks before committing.
• Produces design forks when needed via NEEDS_INPUT.md to surface operator-facing decisions.

Quick Start

Invoke the harness with a brief friction description to start the hardening workflow.