Skip to content

feat: add --verbosity levels (compact, normal, verbose) to status command (console only) #311

@jimisola

Description

@jimisola

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

  • --verbosity compact|normal|verbose accepted by status --format console (default normal)
  • compact outputs a single summary line (counts + exit code)
  • normal reproduces current behaviour exactly (no regression)
  • verbose shows full per-requirement breakdown
  • --format json ignores --verbosity and always dumps full output
  • --format json accepts --req-ids / --svc-ids filters
  • Unit tests cover all three console levels and JSON filtering

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions