audit-remediation

Audit remediation automatically applies approved fixes by parsing the remediation plan, grouping changes by type (config, template, code, file-creation), executing them in dependency order using appropriate agents, and validating outcomes before returning a summary of applied and failed fixes.

Yes. Audit remediation handles template synchronization as one of its grouped fix types, applying template updates across library and consumer repositories in dependency-aware order after user approval.

Audit remediation groups and applies four fix types: config file updates, template synchronization, code fixes, and file creation. Each type is routed to its appropriate agent and validated for existence, content, and syntax.

Audit remediation executes fixes in dependency-respecting order, ensuring that prerequisite changes complete before dependent ones, preventing conflicts and validation failures across library and consumer repositories.

Audit remediation returns applied_fixes, failed_fixes, files_modified, and a summary report tracking which remediation actions succeeded, which failed, and what files were changed.

Audit remediation gracefully handles failures by continuing to process remaining fixes, accumulating both successful and failed outcomes in the final summary so you see the complete remediation state.