remediate

Run Stage 6R remediation, which reads the 6V report, triages each failure by fixability, and applies mechanical fixes through parallel agent teammates. Each fix is typechecked and re-verified in the running app before the gate decision is updated.

6V-A issues are auto-fixable with one correct mechanical fix, such as adding a route to a middleware whitelist. 6V-B issues are semi-auto fixes based on codebase patterns that need verification. 6V-C issues require human judgment, such as business logic or architecture decisions.

Skip 6R when the 6V gate decision is PASS, or when the report contains only 6V-C issues that require human judgment. Also stop on a 6V FAIL verdict, since critical issues need manual architectural fixes before re-running 6V.

Yes, the Skill adapts to the stack defined in plancasting/tech-stack.md, mapping middleware files, route whitelists, loading patterns, i18n files, and backend directories to equivalents. Package manager commands also follow the project's CLAUDE.md conventions.

After three completed cycles tracked in loop-count.txt, remaining 6V-A and 6V-B issues auto-escalate to 6V-C and a remaining-blockers.md file is created. The operator must manually resolve them, re-run 6V, or document them as known limitations before proceeding.

A fix is reverted and moved to 6V-C if it introduces a new failure of equal or higher severity, or if typecheck, lint, or test results regress from the recorded baseline. Zero test regressions is a non-negotiable rule.