h4tcher-audit-execute

Progressive audit execution triages findings into tiers and dispatches parallel sub-agents wave-by-wave. It maintains a finding registry that updates statuses from pending to in_progress, then resolved, deferred, or rejected, ensuring closed-loop tracking throughout the remediation workflow.

A regression gate validates tests, typecheck, lint, build, and content checks against a captured baseline before shipping. It enforces an 18-check validation process that blocks deployment on failures, ensuring audit fixes do not introduce regressions.

Finding registry tracking maintains execution tier metadata and updates statuses through pending, in_progress, resolved, deferred, or rejected. This creates a closed-loop audit evolution with a traceable registry throughout the remediation workflow.

Audit evolution proposals update PRD and produce content specifications with explicit user consent. The workflow applies these proposals during the closed-loop archival phase after regression gate enforcement passes successfully.

Governance audit execution requires reading the AUDIT-EXECUTE.md file and the audit report, running baseline hygiene checks, and defining exclusions, wave scope, and branch strategy before dispatching wave sub-agents.

Use a four-wave progressive model for repository-wide audit remediation workflows requiring tier classification and parallel sub-agent execution. It applies fixes safely with regression gating and traceable finding registry updates.