Track unavailable validator decisions in reports and debug records

docs/internal/diagnostics-reporting.md

@@ -15,6 +15,11 @@ Audita's versioned YAML DTOs, fixed Markdown rendering, and brief CLI
 completion formatter. YAML redaction walks serialized string nodes so numeric
 and boolean values retain their types. Ordinary reports omit raw causes,
 transcript text, complete decisions, and token/timing payloads.
+Validation operations with unavailable decisions report only affected requested
+indices, even when other candidates in the batch continue. Ignored extra
+validator entries yield `validation_decisions_filtered` only for a successful
+operation; they do not count as filtered correction proposals. Failed operations
+retain their execution counts and never produce a recovery record.
 
 `internal/core/diagnostics.OutputSession` owns active destination checks,
 transcript preflight, report initialization, regular-file replacement, and direct
@@ -40,6 +45,12 @@ Debug write failures reach the CLI through an explicit concurrency-safe diagnost
 callback and produce redacted stderr messages without aborting processing.
 Completed validator decisions returned with a fatal batch error remain available
 to the debug ledger; they never authorize applying an incompletely validated edit.
+Runner decision records carry the validator's explicit approved, rejected, or
+unavailable disposition into the ledger. Unavailable candidates have a distinct
+top-level ledger disposition, while fatal interruptions remain interrupted when
+no rejection or unavailable decision was returned. Successful validation
+interaction payloads contain the full decoded response, final content, and
+reconciliation outcomes; ignored indices do not become ledger candidates.
 Every debug writer uses all configured backend secrets for redaction, including
 unselected backend credentials and source snapshots. Debug can still contain
 sensitive transcript and prompt content.