Carry repair provenance through application workflows

docs/internal/prepared-report.md

@@ -21,8 +21,9 @@ Before accepting generated JSON, the execution boundary reconciles the prepared
 report definition, inspected prompt hash and selected profile identity, the one
 preparation callback, and the completed Promptkit result. The callback and
 completion must agree on prompt, profile, backend, model, and rendered/input
-hashes; the callback output and completed validation must name the prepared
-report's JSON Schema. A mismatch produces no rendered Markdown and leaves
+hashes; the callback output must also carry the prepared report's configured
+repair budget, while the completed validation records the actual corrective
+calls used within that budget. A mismatch produces no rendered Markdown and leaves
 results with only the inspected safe identity.
 
 Single-report generation executes one prepared profile and publishes its