remediating-devforgeai-audit

name	remediating-devforgeai-audit
description	Deterministically plan, implement, verify, compare, or render remediation for a validated DevForgeAI enterprise audit run. Use when given an explicit audit run ID or normalized finding ID; never use for custody-chain story audits or raw Markdown findings.

Remediating DevForgeAI Audit

Require explicit native arguments: run-id=<run-id>, optional finding=<id>, dry-run=true, or resume=true. Do not depend on slash-command state or hidden context.

Gate sequence

1. Run audit-findings-status for run-id. Reject raw Markdown as execution state; only a validated durable register is accepted.
2. Use audit-content-validate and audit-import-completed only for immutable completed-report intake. Use audit-findings-build once after intake.
3. Follow phases 00–07 returned by the shared phase registry and dependency plan.
4. Before source mutation, display the exact path/patch digest and require the CLI-owned one-use approval. dry-run=true stops before mutation.
5. Use audit-remediation-record. Do not edit status, events, approvals, evidence, closures, reports, or intake snapshots.
6. Use audit-remediation-verify; dispatch native audit-closure-verifier only after implementation evidence is complete and from a different actor.
7. Use audit-remediation-compare only after protected-main re-audit and audit-remediation-render only as a read-only projection.

HALT on missing CLI, exit 127, malformed JSON, missing state/schema, stale generation, wrong commit/worktree, unsupported provider capability, invalid approval, or incomplete evidence. Do not mark a finding closed before human merge and protected-main re-audit.

The shared CLI owns parsing, fingerprints, dependencies, transitions, approvals, evidence, comparison, and closure. This skill is orchestration only.