cleveragents/cleveragents-core

Fork 3

UAT: `agents plan list --format json` does not produce spec-required JSON envelope #4964

New issue

Open

opened 2026-04-08 23:40:48 +00:00 by freemo · 1 comment

freemo commented

2026-04-08 23:40:48 +00:00

Owner

Bug Report

Feature Area: Plan Lifecycle — agents plan list
Severity: High
Discovered by: UAT tester (uat-worker-plan-lifecycle)

What Was Tested

The JSON output format of agents plan list (and agents plan list --format json).

Expected Behavior (from spec §agents plan list)

The spec requires a structured JSON envelope:

{
  "command": "plan list",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "plans": [
      {
        "id": "01HXM7A9",
        "phase": "execute",
        "state": "processing",
        "action": "local/code-coverage",
        "project": "local/api-service",
        "elapsed": "00:01:12"
      }
    ],
    "filters": {
      "phase": "execute",
      "state": null,
      "project": null,
      "action": null
    },
    "summary": {
      "total": 1,
      "processing": 1,
      "completed": 0,
      "errored": 0,
      "cancelled": 1
    }
  },
  "timing": { "started": "2026-02-09T14:30:00Z", "duration_ms": 95 },
  "messages": ["1 plan listed"]
}

Actual Behavior (from code analysis)

The lifecycle_list_plans command at src/cleveragents/cli/commands/plan.py line 2656-2658 outputs a raw list of plan dicts when fmt != "rich":

data = [_plan_spec_dict(p) for p in plans]
console.print(format_output(data, fmt))

This produces a flat list of plan objects without the required command, status, exit_code, data, timing, and messages envelope fields.

Additionally, the data.plans items in the spec use simplified fields (id, phase, state, action, project, elapsed) but _plan_spec_dict() returns a much more verbose object with different field names (plan_id, namespaced_name, processing_state, etc.).

Additional Issue: Missing "Cancelled" count in Summary panel

The spec's rich output (line 12269) shows Cancelled: 1 in the Summary panel, but the code (lines 2756-2763) only shows Total/Processing/Completed/Errored — the cancelled_count is missing.

Code Location

src/cleveragents/cli/commands/plan.py, lines 2656-2763 (lifecycle_list_plans function)

Steps to Reproduce

agents plan list --format json

Impact

Any tooling or scripts that parse agents plan list --format json output will fail because the output structure does not match the spec. This breaks machine-readable consumption of plan list data.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area**: Plan Lifecycle — `agents plan list` **Severity**: High **Discovered by**: UAT tester (uat-worker-plan-lifecycle) ### What Was Tested The JSON output format of `agents plan list` (and `agents plan list --format json`). ### Expected Behavior (from spec §agents plan list) The spec requires a structured JSON envelope: ```json { "command": "plan list", "status": "ok", "exit_code": 0, "data": { "plans": [ { "id": "01HXM7A9", "phase": "execute", "state": "processing", "action": "local/code-coverage", "project": "local/api-service", "elapsed": "00:01:12" } ], "filters": { "phase": "execute", "state": null, "project": null, "action": null }, "summary": { "total": 1, "processing": 1, "completed": 0, "errored": 0, "cancelled": 1 } }, "timing": { "started": "2026-02-09T14:30:00Z", "duration_ms": 95 }, "messages": ["1 plan listed"] } ``` ### Actual Behavior (from code analysis) The `lifecycle_list_plans` command at `src/cleveragents/cli/commands/plan.py` line 2656-2658 outputs a **raw list** of plan dicts when `fmt != "rich"`: ```python data = [_plan_spec_dict(p) for p in plans] console.print(format_output(data, fmt)) ``` This produces a flat list of plan objects without the required `command`, `status`, `exit_code`, `data`, `timing`, and `messages` envelope fields. Additionally, the `data.plans` items in the spec use simplified fields (`id`, `phase`, `state`, `action`, `project`, `elapsed`) but `_plan_spec_dict()` returns a much more verbose object with different field names (`plan_id`, `namespaced_name`, `processing_state`, etc.). ### Additional Issue: Missing "Cancelled" count in Summary panel The spec's rich output (line 12269) shows `Cancelled: 1` in the Summary panel, but the code (lines 2756-2763) only shows Total/Processing/Completed/Errored — the `cancelled_count` is missing. ### Code Location - `src/cleveragents/cli/commands/plan.py`, lines 2656-2763 (`lifecycle_list_plans` function) ### Steps to Reproduce ```bash agents plan list --format json ``` ### Impact Any tooling or scripts that parse `agents plan list --format json` output will fail because the output structure does not match the spec. This breaks machine-readable consumption of plan list data. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

freemo added the

Type

Bug

label

2026-04-08 23:40:53 +00:00

HAL9000 added the

labels

2026-04-09 00:29:16 +00:00

HAL9000 commented

2026-04-09 00:50:43 +00:00

Owner

Issue triaged by project owner:

State: Verified
Priority: High — JSON output envelope is required by the spec for all CLI commands; missing envelope breaks any tooling or scripts parsing CLI output
Milestone: v3.2.0 (plan list is a core plan lifecycle command)
Story Points: 3 — M — Fix requires wrapping existing output in the standard JSON envelope with command, status, exit_code, data, timing, and messages fields
MoSCoW: Must Have — The spec explicitly requires the JSON envelope format for all --format json output; this is a spec compliance bug
Parent Epic: #4958 (Decision Recording Epic covers plan output formats)

This is a valid spec compliance bug. The fix is straightforward: wrap the existing plan list output in the standard JSON envelope.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — JSON output envelope is required by the spec for all CLI commands; missing envelope breaks any tooling or scripts parsing CLI output - **Milestone**: v3.2.0 (plan list is a core plan lifecycle command) - **Story Points**: 3 — M — Fix requires wrapping existing output in the standard JSON envelope with command, status, exit_code, data, timing, and messages fields - **MoSCoW**: Must Have — The spec explicitly requires the JSON envelope format for all `--format json` output; this is a spec compliance bug - **Parent Epic**: #4958 (Decision Recording Epic covers plan output formats) This is a valid spec compliance bug. The fix is straightforward: wrap the existing plan list output in the standard JSON envelope. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed