Retain repair diagnostics and correction lineage

docs/integrations/output-files.md

@@ -101,6 +101,9 @@ holds logical calls and PromptKit execution events. Interaction request/response
 artifacts and input snapshots are also debug-only. Records carry zero-based
 `stage_index` and optional `stage_id` where an entry is identified.
 These files are diagnostic evidence, not an alternate ordinary report schema.
+For a repaired proposal, one ledger row preserves the original proposed edit,
+the final applied segment and span when applicable, and repair attempts with
+revision decisions and interaction artifact paths.
 Each candidate-backed ledger entry includes `proposed_corrected_text`, the
 literal replacement span, even when it is `""` for a deletion. Applied entries
 also include `applied_corrected_text`, likewise `""` for an applied deletion.

docs/internal/diagnostics-reporting.md

@@ -37,7 +37,9 @@ under `diagnostics.work_dir`. CLI passes empty diagnostics paths and nil writers
 when debug is off. With debug enabled, it captures source and normalized
 snapshots, invocation, effective settings, correction ledger, LLM execution
 observations, and model interactions. Candidate capture includes proposals later
-rejected or interrupted. Ledger mapping preserves empty proposed and applied
+rejected or interrupted. Repair and revalidation artifacts use section, proposal,
+attempt, validator, and batch coordinates as applicable; their retained content
+is redacted using the selected role credentials. Ledger mapping preserves empty proposed and applied
 replacements and distinguishes unavailable candidates from interrupted work.
 
 A concurrency-safe diagnostic callback reports optional write failures without

docs/roadmap/implementation.md

@@ -322,6 +322,8 @@ validator responses remains [deferred](future.md#domain-aware-response-recovery)
 
 ## Stage 8 — Retain optional repair evidence and preserve ledger lineage
 
+**Completed.**
+
 1. Extend the current interaction writers and logical execution observation
    data with a repair role, original proposal index, and one-based semantic
    attempt number. Use generated stage instance, section, proposal, and