Record execution summaries in debug artifacts

docs/internal/state.md

@@ -1,5 +1,9 @@
 # Run State Internals
 
+LLM debug response artifacts and their safe per-call references retain an
+optional terminal execution summary when one is available. This metadata is
+diagnostic only and does not change receipts, checkpoints, or aggregate usage.
+
 This document describes the implementation collaborators behind output, cache,
 and debug state. User-visible fields belong in [Configuration](../config.md),
 and physical layout, retention, recovery, reason codes, and cleanup belong in

docs/operations.md

@@ -147,6 +147,11 @@ their exit classes are defined in the [CLI reference](cli.md#output-streams-and-
 
 ## Validation Retries And Terminal Outcomes
 
+When debug recording is enabled, per-call response artifacts include the
+terminal execution summary for retry, repair, timing, and presence-aware usage
+diagnosis. Normal output, receipts, and warnings do not aggregate or publish
+this diagnostic metadata.
+
 Each producer binding has one outer **retries** budget. It covers complete
 producer attempts for operational failures, invalid structured output,
 normalizer fallback retry, and semantic correction. It is independent from

docs/roadmap/implementation.md

@@ -270,6 +270,8 @@ and `GOWORK=off go test -race ./internal/framework/llm`.
 
 ## Stage 6 — Carry Summaries Through Existing Debug Paths
 
+**Status:** Completed 2026-09-25.
+
 **Goal:** Make observations useful to operators without a new output channel.
 One prompt, limited to debug propagation and terminal allowlists.