Record delegated configuration exit status gaps
This commit is contained in:
@@ -51,6 +51,40 @@ input, and status 1 for cancellation. While the supporting release is pending,
|
||||
record the mismatch explicitly. A test that asserts only nonzero status does
|
||||
not verify this fix.
|
||||
|
||||
**Complete.** The upstream handoff is recorded below. The exit-status fix
|
||||
remains outstanding for the final verification pass.
|
||||
|
||||
Build a temporary executable with `go build -o /tmp/audita-inspection ./cmd/audita`.
|
||||
In a scratch directory, put `version: 3` in `config.yml`, `profiles: [` in the
|
||||
adjacent `prompts.yml`, and `[]` in `transcript.json`. End each file with a newline.
|
||||
|
||||
| Invocation with `/tmp/audita-inspection` | Status | Diagnostic |
|
||||
| --- | --- | --- |
|
||||
| `promptkit list prompts --config config.yml` | 1 | `yaml.invalid` in `prompts.yml` |
|
||||
| `process transcript.json --config config.yml` | 2 | `yaml.invalid` in `prompts.yml` |
|
||||
| `config show --scope promptkit --config config.yml` | 1 | `yaml.invalid` in `prompts.yml` |
|
||||
|
||||
`config sources`, `config validate`, `config explain --list`, and
|
||||
`config diff --against-config config.yml` also returned 1 for the `promptkit`
|
||||
scope with the same diagnostic. All five `app` scope operations succeeded
|
||||
with the malformed companion and returned 1 with `yaml.invalid` for a
|
||||
separately selected main file containing `version: [`. These failures occur
|
||||
during configuration loading, before provider work. The cancellation test
|
||||
passes an already canceled context through the application entry point and
|
||||
verifies status 1, `context.Canceled`, and empty stdout for catalog listing,
|
||||
configuration show, and processing.
|
||||
|
||||
Both native adapters receive the typed ConfigKit load cause from Audita's
|
||||
existing loaders. In `ckprompt`, `runCatalogList` assigns the operational
|
||||
outcome through `definitionFailure`. In `ckconfig`, the scope handlers
|
||||
assign it through `configFailure`, with `show` calling it through
|
||||
`configAcquisitionFailure`. The upstream owners are the respective CommandKit
|
||||
integrations. They need to assign status 2 for typed operator-input failures
|
||||
at those boundaries, preserving diagnostics, available inspection evidence,
|
||||
and the cause. Cancellation and other operational failures need status 1.
|
||||
The upstream tag list contained releases through `v0.7.0` for each
|
||||
integration, which are already pinned. Recheck both in the final stage.
|
||||
|
||||
## Stage 2 — Remove application credential substitution
|
||||
|
||||
Audit #3, #9, #31 (source bytes), #63–65. Use the
|
||||
|
||||
Reference in New Issue
Block a user