Summary
The status command currently has a single fixed output format. Add a --verbosity flag to control how much detail is shown — applicable to --format console only. JSON output always dumps the full dataset, optionally filtered.
Console verbosity levels
| Level |
Behaviour |
compact |
One-line summary: overall pass/fail counts only |
normal |
Current default — tabular summary with per-requirement status |
verbose |
Full detail: all SVCs, MVRs, annotations, and test results per requirement |
--verbosity is ignored (or an error) when --format json is used.
JSON output
- Always emits the full status dataset (no verbosity concept).
- Add optional
--req-ids / --svc-ids filters (consistent with the export command) to narrow the output to specific requirements or SVCs.
Motivation
- CI pipelines benefit from a compact single-line console result.
- Developers debugging failures need verbose drill-down without switching to
report.
- JSON consumers want the full machine-readable payload, optionally scoped to a subset of IDs.
Acceptance criteria
Summary
The
statuscommand currently has a single fixed output format. Add a--verbosityflag to control how much detail is shown — applicable to--format consoleonly. JSON output always dumps the full dataset, optionally filtered.Console verbosity levels
compactnormalverbose--verbosityis ignored (or an error) when--format jsonis used.JSON output
--req-ids/--svc-idsfilters (consistent with theexportcommand) to narrow the output to specific requirements or SVCs.Motivation
report.Acceptance criteria
--verbosity compact|normal|verboseaccepted bystatus --format console(defaultnormal)compactoutputs a single summary line (counts + exit code)normalreproduces current behaviour exactly (no regression)verboseshows full per-requirement breakdown--format jsonignores--verbosityand always dumps full output--format jsonaccepts--req-ids/--svc-idsfilters