EPIC: CLI Output Format Compliance — Global Flags, JSON Envelope & Error Responses #5203

Open
opened 2026-04-09 03:12:30 +00:00 by HAL9000 · 2 comments
Owner

Background

Part of the Decision Intelligence Legendary (#4942). This Epic fixes critical CLI output format compliance issues: global flags (--format, --data-dir, --config-path, -v) not working, JSON/YAML envelope fields missing or incorrect, and error responses not structured per spec.

Demonstrable Capability

When this Epic is complete, all CLI commands respect global flags, produce correctly structured JSON/YAML envelopes with all required fields, and return structured error responses instead of plain text.

Child Issues

  • #5191 — UAT: Global --format flag ignored by subcommands
  • #5192 — UAT: Global --data-dir and --config-path flags not implemented
  • #5193 — UAT: Global -v verbosity flag not implemented
  • #5194 — UAT: JSON/YAML envelope command field is always empty string
  • #5195 — UAT: JSON/YAML envelope missing metadata field
  • #5196 — UAT: JSON/YAML messages[0].text is always "ok"
  • #5197 — UAT: JSON/YAML error responses not structured per spec
  • #5198 — UAT: JSON/YAML envelope timing.duration_ms is always 0

Definition of Done

  • All child issues are closed and merged
  • Global --format flag propagates to all subcommands
  • Global --data-dir and --config-path flags functional
  • Global -v verbosity flag works (repeatable)
  • JSON/YAML envelope has all required fields (command, metadata, timing, messages)
  • Error responses are structured JSON envelopes
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch Naming Convention: fix/v3.2.0/cli-output-format-compliance
  • Milestone: v3.2.0
  • Parent Legendary: #4942

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Background Part of the Decision Intelligence Legendary (#4942). This Epic fixes critical CLI output format compliance issues: global flags (`--format`, `--data-dir`, `--config-path`, `-v`) not working, JSON/YAML envelope fields missing or incorrect, and error responses not structured per spec. ## Demonstrable Capability When this Epic is complete, all CLI commands respect global flags, produce correctly structured JSON/YAML envelopes with all required fields, and return structured error responses instead of plain text. ## Child Issues <!-- Updated by automation after child issues are created --> - [ ] #5191 — UAT: Global `--format` flag ignored by subcommands - [ ] #5192 — UAT: Global `--data-dir` and `--config-path` flags not implemented - [ ] #5193 — UAT: Global `-v` verbosity flag not implemented - [ ] #5194 — UAT: JSON/YAML envelope `command` field is always empty string - [ ] #5195 — UAT: JSON/YAML envelope missing `metadata` field - [ ] #5196 — UAT: JSON/YAML `messages[0].text` is always `"ok"` - [ ] #5197 — UAT: JSON/YAML error responses not structured per spec - [ ] #5198 — UAT: JSON/YAML envelope `timing.duration_ms` is always 0 ## Definition of Done - [ ] All child issues are closed and merged - [ ] Global `--format` flag propagates to all subcommands - [ ] Global `--data-dir` and `--config-path` flags functional - [ ] Global `-v` verbosity flag works (repeatable) - [ ] JSON/YAML envelope has all required fields (command, metadata, timing, messages) - [ ] Error responses are structured JSON envelopes - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch Naming Convention**: `fix/v3.2.0/cli-output-format-compliance` - **Milestone**: v3.2.0 - **Parent Legendary**: #4942 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.2.0 milestone 2026-04-09 03:12:36 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Critical — CLI output format compliance is foundational; JSON envelope, global flags, and error responses affect all commands
  • Milestone: v3.2.0 (already assigned — this is a base requirement)
  • Story Points: 21 (XXL) — comprehensive output format compliance across all CLI commands
  • MoSCoW: Must Have — correct CLI output format is required for all tooling and automation that consumes the CLI
  • Parent Epic: LEGENDARY #4942 (Decision Intelligence) or core CLI

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Critical — CLI output format compliance is foundational; JSON envelope, global flags, and error responses affect all commands - **Milestone**: v3.2.0 (already assigned — this is a base requirement) - **Story Points**: 21 (XXL) — comprehensive output format compliance across all CLI commands - **MoSCoW**: Must Have — correct CLI output format is required for all tooling and automation that consumes the CLI - **Parent Epic**: LEGENDARY #4942 (Decision Intelligence) or core CLI --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
Author
Owner

Epic Planning: This Epic was created to group 8 orphaned UAT issues related to global CLI flag compliance and JSON/YAML envelope format issues.

Child Issues Linked

  • #5191 — Global --format flag ignored by subcommands (Priority/Critical)
  • #5192 — Global --data-dir and --config-path flags not implemented (Priority/Critical)
  • #5193 — Global -v verbosity flag not implemented (Priority/High)
  • #5194 — JSON/YAML envelope command field is always empty string (Priority/High)
  • #5195 — JSON/YAML envelope missing metadata field (Priority/Medium)
  • #5196 — JSON/YAML messages[0].text is always "ok" (Priority/Medium)
  • #5197 — JSON/YAML error responses not structured per spec (Priority/High)
  • #5198 — JSON/YAML envelope timing.duration_ms is always 0 (Priority/Backlog)

Dependency Chain

#5191-#5198 (UAT bugs) → EPIC #5203 → LEGENDARY #4942

Note: Issues #5191 and #5192 are Priority/Critical — global flags are fundamental to CLI usability.


Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

**Epic Planning**: This Epic was created to group 8 orphaned UAT issues related to global CLI flag compliance and JSON/YAML envelope format issues. ## Child Issues Linked - [ ] #5191 — Global `--format` flag ignored by subcommands (Priority/Critical) - [ ] #5192 — Global `--data-dir` and `--config-path` flags not implemented (Priority/Critical) - [ ] #5193 — Global `-v` verbosity flag not implemented (Priority/High) - [ ] #5194 — JSON/YAML envelope `command` field is always empty string (Priority/High) - [ ] #5195 — JSON/YAML envelope missing `metadata` field (Priority/Medium) - [ ] #5196 — JSON/YAML `messages[0].text` is always `"ok"` (Priority/Medium) - [ ] #5197 — JSON/YAML error responses not structured per spec (Priority/High) - [ ] #5198 — JSON/YAML envelope `timing.duration_ms` is always 0 (Priority/Backlog) ## Dependency Chain ``` #5191-#5198 (UAT bugs) → EPIC #5203 → LEGENDARY #4942 ``` **Note**: Issues #5191 and #5192 are Priority/Critical — global flags are fundamental to CLI usability. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks Depends on
Reference
cleveragents/cleveragents-core#5203
No description provided.