Normalize JSON and JSONL output
This commit is contained in:
parent
3c84713472
commit
116a431a12
5 changed files with 276 additions and 191 deletions
|
|
@ -121,6 +121,17 @@ For deployment-readiness work that cuts across feature areas, see
|
|||
- `[x]` Tests cover transient path detection/copying, file-log states, and
|
||||
user-scoped generated definitions.
|
||||
|
||||
- `[x]` Normalize machine-readable CLI output.
|
||||
Acceptance criteria:
|
||||
- `[x]` `--json` emits one pretty JSON document and `--jsonl` emits each
|
||||
result as one compact physical line; the flags are mutually exclusive.
|
||||
- `[x]` Direct CLI results, local-control responses, and service reports use
|
||||
stable top-level `type` fields without mixing operator prose into stdout.
|
||||
- `[x]` Machine-mode failures use the stable error envelope, include a
|
||||
focused recovery hint when available, and exit nonzero.
|
||||
- `[x]` Tests and automation documentation define the single-document and
|
||||
line-oriented contracts.
|
||||
|
||||
- `[ ]` Publish copy-paste installation entrypoints for release artifacts.
|
||||
Acceptance criteria:
|
||||
- `[ ]` Linux, macOS, and Windows installation instructions verify artifact
|
||||
|
|
|
|||
Loading…
Reference in a new issue