Document resilient reports and remove obsolete warning material

docs/internal/validators.md

@@ -42,7 +42,7 @@ Glossary, homophones, spoken_word, and grammar each resolve a fixed ordered chai
 For each module section:
 1. run deterministic validators;
 2. run LLM-backed validators;
-3. record decisions and warnings;
+3. record decisions and compact operation outcomes;
 4. carry only approved proposals forward.
 
 Decision cardinality is enforced: each candidate proposal must receive exactly one decision per validator.
@@ -55,15 +55,16 @@ LLM validators:
 - select an embedded prompt ID and pass payload/description variables to the
   role-bound structured client with the validator-decision schema.
 
-Oversized single proposals are rejected with `validator_input_too_large`.
-Exhausted structural repair becomes a warning and rejected batch decisions.
-Provider, malformed HTTP envelope, deadline, and admission failures propagate
-as runtime errors. Schema-valid decisions still undergo exact index/cardinality
-checks and domain acceptance without a semantic retry.
+Oversized single inputs are rejected with a consolidated
+`validation_input_too_large` operation, without a provider call. Recoverable
+model failures make only their batch candidates unavailable while other
+batches continue. Missing, duplicate, or unknown decision indices invalidate
+that batch as a whole. Fatal errors stop the chain without returning unchecked
+candidates as approved. Domain acceptance has no semantic retry.
 
 ## Decision and Rejection Reporting
 
-Runner collects decisions, rejected candidates, and warning records. Ledger
+Runner collects decisions, rejected candidates, and operation outcomes. Ledger
 assembly groups decisions by deterministic versus LLM-backed execution metadata.
 The serialized names and fields belong to the
 [report and ledger contract](../integrations/output-files.md); implementation mapping