Repair rejected corrections in independent branches

docs/internal/pipeline.md

@@ -19,10 +19,14 @@ formats; [configuration](../config.md) owns settings; the
    may preserve a checked subset of completed decisions as diagnostic evidence.
    Recoverable failed batches mark their candidates unavailable; successful
    survivors continue through all required validators.
-6. Only fully approved proposals reach application. Corrections apply in
+6. Actionable rejections can enter independent section-local repair branches.
+   Each revision is mapped to the original section and revalidated from the
+   start. Withdrawal, exhaustion, and recoverable failures finish the branch
+   without affecting independent approvals.
+7. Only fully approved proposals reach application. Corrections apply in
    proposal-index order within their owning section. Existing replacement
    policies and apply-time safety checks resolve stale conflicts.
-7. CLI encodes the final transcript and publishes active files through the
+8. CLI encodes the final transcript and publishes active files through the
    output session. `framework/processreport` builds one snapshot for YAML,
    Markdown, and CLI totals. Debug evidence is captured separately when enabled.
 

docs/roadmap/implementation.md

@@ -221,6 +221,8 @@ validator responses remains [deferred](future.md#domain-aware-response-recovery)
 
 ## Stage 6 — Run independent repair branches and apply accepted revisions
 
+**Completed.**
+
 1. Extend the section validation worker in `runModulePipeline` after its
    initial pass. Keep the approved candidates as they are. For each candidate
    with an actionable rejection, initialize an independent branch on the