Unify structured call completion and retain typed failures

This commit is contained in:
2026-11-16 14:27:54 +00:00
parent e98e525b5c
commit c2c8050bc8
18 changed files with 313 additions and 186 deletions

View File

@@ -12,10 +12,14 @@ profiles and effective budgets. Clients share engine-local backend admission.
The adapter uses ordinary `Run` with `OperationTimeout` and `OnPrepared`, passes
Audita's per-call schema and repair budget, and decodes only validated results.
The operation budget includes preparation, admission, retries, and structural
repair. `ErrOperationTimeout` remains recoverable even when wrapped by a
preparation error. Parent cancellation remains distinct. The prepared notification
repair. An expired parent context stops processing and retains any native cause.
With an active parent, PromptKit's operation deadline remains recoverable even
when a preparation error wraps it. A native transport timeout affects the HTTP
attempt and is recorded as a transport failure. The prepared notification
provides the actual request snapshot; failures before notification have no snapshot.
PromptKit owns backend and credential selection. See the [integration contract](../integrations/openai-compatible-llm.md)
PromptKit owns backend and credential selection. When a required credential is absent,
the CLI identifies the role, profile, and environment variable using the native
diagnostic. See the [integration contract](../integrations/openai-compatible-llm.md)
for failure behavior and the [configuration reference](../config.md) for sources.
When correction repair is enabled, the proposal call captures a native immutable
@@ -26,7 +30,10 @@ for assessment. Follow-ups select the repair prompt, profile, and output schema
directly; Audita does not rerender the original proposal or assemble replay messages.
An opaque exchange in the structured-output contract keeps provider state outside
modules and validators. The adapter shares request construction, notifications,
observers, and result/failure finalization between ordinary and coordinated calls.
observers, and once-only completion between ordinary and coordinated calls.
Completion attaches terminal counts when available and records one logical finish.
Prepared requests and terminal output travel in the returned response for an
optional interaction artifact. Logical call notifications carry metadata.
Audita owns actionable rejection, revision decoding, withdrawal, current previews,
and full revalidation. Accepted siblings remain independent. Requesting more work
@@ -44,7 +51,11 @@ selected runs in a native `ExecutionGroup`. Proposal, repair, and nested validat
clients explicitly share the invocation observer; history reuse adds no extra run.
Native summaries deduplicate terminal totals by run ID and retain terminal coverage
separately from usage presence and completeness. Logical calls and run membership
can differ, especially on failures before execution. Ordinary
reports use compact safe outcomes; request and response evidence is optional
debug material. The runner preserves ordered pipeline traversal and deterministic
section collection while canceling and joining peers on fatal errors.
can differ, especially on failures before execution.
Processing operations retain the failure class, reason, and underlying error.
When a client omits the reason, the operation uses `internal_failure` and keeps
the original class and error chain. Ordinary reports use compact outcomes.
Request and response evidence is optional debug material. The runner preserves
ordered pipeline traversal and deterministic section collection while canceling
and joining peers on fatal errors.

View File

@@ -447,6 +447,14 @@ controlled budgets. Check setup class/cause and useful native information,
plus ordinary/coordinator terminal and undelivered-evidence paths. Update
[LLM runtime internals](../internal/llm-runtime.md).
**Complete.** Ordinary and coordinated calls share once-only completion,
including prepared and undelivered evidence and native terminal counts.
Proposal, validation, and repair retain typed failure facts. Independent
parent, operation, and attempt deadlines produced the expected classifications.
The CLI identifies a missing required credential by role, profile, and
environment variable while the ordinary report retains the setup reason.
The CLI build, full offline Go suite, and targeted race checks passed.
## Stage 13 — Use one proposal handoff
Audit #46.