Report live correction progress through CommandKit
This commit is contained in:
@@ -20,6 +20,12 @@ audita process [flags] transcript.json
|
||||
messages. Quiet processing requires an output file or `/dev/null`. See
|
||||
[operations](operations.md) for output and report lifecycle.
|
||||
|
||||
Progress for processing goes to stderr. Use `--progress` to show stage and
|
||||
chunk activity, model proposal, validation and repair operations, and observed
|
||||
counts as work completes. Debug mode enables progress by default.
|
||||
`--progress=false` disables it, and quiet mode suppresses it even when
|
||||
`--progress` is explicit.
|
||||
|
||||
Explicit process flags override root settings only. `--glossaries` and
|
||||
`--protected-terms` each accept one JSON array of collection names or `null`;
|
||||
`[]` clears the selection. Set pipeline order and per-entry overrides in YAML.
|
||||
@@ -35,7 +41,7 @@ The application configuration scope uses ConfigKit's native effective values,
|
||||
source evidence, explanation, comparison, and redaction. PromptKit supplies its
|
||||
own configuration and resource scopes and request preparation, validation, and
|
||||
explicit smoke diagnostics. Inspection does not require a processing-ready
|
||||
pipeline or contact a provider. Smoke tests can contact providers and are run
|
||||
pipeline or contact a provider. Processing preflight separately checks the selected\nprofiles and glossary entries. Smoke tests can contact providers and are run
|
||||
only on explicit request.
|
||||
|
||||
Process stdout contains transcript JSON when no output file is selected. Ordinary
|
||||
|
||||
@@ -18,10 +18,21 @@ not redirect file-output reports. `--work-dir` selects a debug root, while
|
||||
Supplying a configuration path also makes file selection predictable; only
|
||||
explicitly referenced credential variables are read from the environment.
|
||||
|
||||
Choose a trusted configuration bundle. An explicit main path still allows
|
||||
its configured imports and automatic overlay, glossary, and prompt companions.
|
||||
Without a main path, Audita uses the configured discovery locations. The
|
||||
parent controls who can write those sources and which report destinations and
|
||||
retained debug directories the invocation will use. Native inspection is
|
||||
separate from processing preflight.
|
||||
|
||||
Resolve the executable deliberately and set the child's working directory so
|
||||
relative input/output paths and reported artifact paths have a known base.
|
||||
Read stdout and stderr concurrently to avoid pipe blocking, and impose timeout
|
||||
or cancellation in the parent process when needed.
|
||||
or cancellation in the parent process when needed. Optional `--progress`
|
||||
messages arrive on stderr during stage and chunk execution, including model
|
||||
operations and completions. Debug enables progress by default, and
|
||||
`--progress=false` or quiet mode suppresses it. Consume progress as
|
||||
human-readable telemetry. Stdout remains the transcript stream.
|
||||
|
||||
## Result Handling
|
||||
|
||||
|
||||
@@ -17,6 +17,17 @@ history to the selected repair provider. A provider rejection ends that branch
|
||||
as unavailable; other approved edits can still be applied. See
|
||||
[configuration](config.md#settings) for the attempt budget and profile selection.
|
||||
|
||||
## Configuration trust
|
||||
|
||||
Treat the selected main file, imports, overlay, and automatically loaded
|
||||
glossary and prompt companions as one trusted bundle. Choose the working
|
||||
directory deliberately when using automatic discovery. A bundle can select
|
||||
the provider, prompt content, and local files consumed by processing. Review
|
||||
these sources before running with sensitive transcript data. Native inspection
|
||||
describes the loaded configuration and resources. Processing readiness also
|
||||
depends on the profiles and glossaries selected by the pipeline. See
|
||||
[configuration loading](config.md#loading-and-composition) for discovery rules.
|
||||
|
||||
## Outputs and lifecycle
|
||||
|
||||
Reporting is enabled by default. For transcript file output, `errors.yml`,
|
||||
@@ -37,6 +48,8 @@ delivery failure while preserving the new destination. Parent directories for
|
||||
required outputs must already exist. Publication uses the destinations resolved
|
||||
during preparation. Give concurrent invocations separate destinations, and
|
||||
choose separate report directories when retaining reports from multiple runs.
|
||||
The caller owns these directories and their retention. Later runs can replace
|
||||
ordinary report files at the same destination.
|
||||
|
||||
Enabled reports are initialized as `in_progress` before processing. The
|
||||
transcript is published before final reports; the files do not form a single
|
||||
@@ -49,6 +62,13 @@ the reader. If failed reports cannot be rendered, available report evidence
|
||||
remains. An uncatchable termination can leave `in_progress` evidence. Use the
|
||||
exit status and report status to determine the outcome.
|
||||
|
||||
## Live progress
|
||||
|
||||
Use `--progress` to follow stage, chunk, proposal, validation, and repair
|
||||
activity on stderr. Report and transcript files provide the retained outcome.
|
||||
Debug mode enables live progress by default. Use `--progress=false` to keep
|
||||
debug evidence with progress disabled.
|
||||
|
||||
## Debug evidence
|
||||
|
||||
The shared `--debug` flag enables retained artifacts in a run directory beneath
|
||||
|
||||
@@ -700,6 +700,14 @@ asserting useful identities and stream separation without exact wording or
|
||||
concurrent ordering. Keep a progress-specific check separate from delegated
|
||||
inspection availability.
|
||||
|
||||
**Complete.** Runner lifecycle and native model events flow through
|
||||
CommandKit progress reporting. Subprocess tests observed proposal progress
|
||||
while a provider was blocked, checked repair activity, verified stdout
|
||||
separation and reporting-mode combinations, and confirmed that a failed
|
||||
progress destination leaves completed output intact. The CLI, operations,
|
||||
and subprocess guides cover live progress, destination ownership, and
|
||||
configuration trust. The full offline Go suite passed.
|
||||
|
||||
## Stage 20 — Verify the integrated sprint and release bootstrap
|
||||
|
||||
Audit #28, #29, #58, #60–62 and sprint closure.
|
||||
|
||||
Reference in New Issue
Block a user