Unify optional interaction capture and warnings
This commit is contained in:
@@ -32,16 +32,23 @@ On a final write error it attempts other enabled reports and one failed-status
|
||||
pass; a published transcript is never erased by a later report failure.
|
||||
|
||||
Debug is independent. The shared `--debug` flag enables a unique retained child
|
||||
under `diagnostics.work_dir`. CLI passes empty diagnostics paths and nil writers
|
||||
when debug is off. With debug enabled, it saves the source bytes as acquired, separate from the parsed and normalized
|
||||
under `diagnostics.work_dir`. The CLI creates one interaction sink rooted in
|
||||
that directory and passes it to proposal generation, validation, and repair.
|
||||
With debug enabled, it saves the source bytes as acquired, separate from the parsed and normalized
|
||||
transcript snapshots. It also captures invocation metadata, effective settings
|
||||
rendered by ConfigKit, the correction ledger, LLM execution observations, and
|
||||
model interactions. Candidate capture includes proposals later
|
||||
rejected or interrupted. Repair and revalidation artifacts use section, proposal,
|
||||
attempt, validator, and batch coordinates as applicable. Ledger mapping preserves empty proposed and applied replacements and distinguishes unavailable candidates from interrupted work.
|
||||
attempt, validator, and batch coordinates as applicable. Request metadata records
|
||||
these coordinates with the interaction role. Each interaction retains its available
|
||||
prepared request, response, and failure evidence. Ledger mapping preserves empty
|
||||
proposed and applied replacements and distinguishes unavailable candidates from
|
||||
interrupted work.
|
||||
|
||||
A concurrency-safe diagnostic callback reports optional write failures without
|
||||
aborting processing. Debug artifacts can contain sensitive transcript and
|
||||
The sink groups concurrent write failures by role, artifact operation, and cause.
|
||||
Warnings report the count and an affected path. The writer still attempts other
|
||||
artifacts and returns the paths it wrote, and the CLI presents warnings separately
|
||||
from processing outcomes and required delivery. Debug artifacts can contain sensitive transcript and
|
||||
prompt content. Execution
|
||||
position and optional operator ID are carried separately from generated safe
|
||||
artifact path coordinates.
|
||||
|
||||
Reference in New Issue
Block a user