Connect processing to shared PromptKit backend capacity

docs/internal/llm-runtime.md

@@ -23,12 +23,12 @@ message and a typed cause; only exhausted structural repair is a malformed
 output failure. Secrets from all configured backends, including unselected
 ones, are available to the diagnostics redaction boundary.
 
-## Current Orchestration
+## Orchestration
 
-The old `llm.Scheduler` and runner instrumentation still exist pending the
-orchestration migration. The final runtime uses PromptKit backend admission,
-retry, and repair rather than that scheduler. `llm.DiagnosticsWriter` remains
-the current protected artifact writer.
-
-Focused adapter tests use controlled local HTTP responses. Complete runner and
-CLI integration checks follow the caller and orchestration migration.
+CLI processing supplies two role clients from the same engine to the runner.
+PromptKit's per-backend admission applies to both roles and every generation,
+retry, and repair. The runner still processes module instances in order,
+collects concurrent section work deterministically, and cancels remaining
+section work on a runtime failure. `llm.DiagnosticsWriter` remains the protected
+request/response artifact writer. Execution observations and report summaries
+are completed by the following roadmap work.

docs/internal/pipeline.md

@@ -38,10 +38,11 @@ Pipeline inputs are:
 
 `runner.Run` returns:
 - final transcript;
-- per-module results;
-- utilization diagnostics.
+- per-module results.
 
-CLI/reporting then map this into process report and diagnostics artifacts.
+CLI/reporting then map these results into process reports and diagnostics
+artifacts. PromptKit execution observations are collected at the role-client
+boundary for the new report summary.
 
 ## Failure Behavior