Document feedback-aware validation retries

docs/consumers/dnd-pipeline.md

@@ -101,6 +101,12 @@ root. Do not scan the output root for its newest directory, guess a run ID, or
 construct a bundle path. Resolve `index_file` beneath `output_directory` and
 reject an absolute logical path or any result that escapes the bundle root.
 
+The complete configuration uses the application validation defaults. A caller
+that requires fully validated D&D artifacts must also require receipt
+`validation_status: approved`; a successful `incomplete` result reflects the
+configured validator-failure continuation policy and carries its bounded
+validator provenance in `validation_summaries`.
+
 Read `index.json` and locate each requested lane in `output_files` by its exact
 `lane_id`. Do not guess a lane filename. Before decoding a payload:
 

docs/consumers/subprocess.md

@@ -69,6 +69,13 @@ lanes. The caller decides which lane IDs are required for its own work and
 which are optional; it should make that decision explicitly rather than infer
 failure from the receipt counts alone.
 
+When complete validation is required, also require receipt
+`validation_status: approved` and inspect `validation_summaries`. A successful
+run with `validation_status: incomplete` contains a structurally valid result
+that advanced after validator execution could not complete under the configured
+`warn_continue` policy. It is not reusable checkpoint state and should not be
+silently treated as fully reviewed by the caller.
+
 ## Preserve Provenance And Handle Data Carefully
 
 Keep the receipt with the published `manifest.json`, and retain