cleveragents/cleveragents-core

Fork 3

UAT: `agents action list --format json` returns flat array instead of spec-required structured data object #6774

New issue

Open

opened 2026-04-10 02:05:13 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-10 02:05:13 +00:00

Owner

Bug Report

Summary

agents action list --format json wraps the action list as a flat array at data, but the spec requires data to be a structured object with actions, filters, and summary sub-keys.

What Was Tested

Code analysis of src/cleveragents/cli/commands/action.py (list_actions function) and src/cleveragents/cli/formatting.py (format_output).

Expected Behavior (from spec)

docs/specification.md line 16429–16452 specifies the JSON output for action list:

{
  "command": "action list",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "actions": [
      {
        "name": "local/code-coverage",
        "state": "available",
        "strategy_actor": "local/strategist",
        "execution_actor": "local/executor",
        "reusable": true,
        "plans": 3
      }
    ],
    "filters": { "state": "available", "namespace": null },
    "summary": { "total": 1, "available": 1, "archived": 0, "total_plans_created": 3 }
  },
  "timing": { "started": "2026-02-08T12:21:00Z", "duration_ms": 45 },
  "messages": ["1 action listed"]
}

The data field must contain three sub-keys: actions (the list), filters (applied filters), and summary (counts).

Actual Behavior

In src/cleveragents/cli/commands/action.py, the list_actions command passes:

data = [_action_spec_dict(a) for a in actions]
console.print(format_output(data, fmt))

This produces data as a flat array of action dicts, e.g.:

{
  "data": [
    { "namespaced_name": "local/code-coverage", ... }
  ]
}

This violates the spec in three ways:

data is an array, not an object with actions/filters/summary
No filters metadata (applied namespace/state filters) is returned
No summary (count statistics) is returned

Additional Issues in the Same Command

The field namespaced_name is used in the output dict (_action_spec_dict), but the spec uses name as the key
No plans count (number of plans created from this action) is returned in the list output
timing.started field is missing from the envelope (spec requires it for action commands)
messages uses [{"level": "ok", "text": "..."}] format, but the spec shows plain strings ["1 action listed"] for all action commands

Steps to Reproduce

agents action list --format json

Observe that data is an array, not an object with actions, filters, and summary.

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

## Bug Report ### Summary `agents action list --format json` wraps the action list as a flat array at `data`, but the spec requires `data` to be a structured object with `actions`, `filters`, and `summary` sub-keys. ### What Was Tested Code analysis of `src/cleveragents/cli/commands/action.py` (`list_actions` function) and `src/cleveragents/cli/formatting.py` (`format_output`). ### Expected Behavior (from spec) `docs/specification.md` line 16429–16452 specifies the JSON output for `action list`: ```json { "command": "action list", "status": "ok", "exit_code": 0, "data": { "actions": [ { "name": "local/code-coverage", "state": "available", "strategy_actor": "local/strategist", "execution_actor": "local/executor", "reusable": true, "plans": 3 } ], "filters": { "state": "available", "namespace": null }, "summary": { "total": 1, "available": 1, "archived": 0, "total_plans_created": 3 } }, "timing": { "started": "2026-02-08T12:21:00Z", "duration_ms": 45 }, "messages": ["1 action listed"] } ``` The `data` field must contain three sub-keys: `actions` (the list), `filters` (applied filters), and `summary` (counts). ### Actual Behavior In `src/cleveragents/cli/commands/action.py`, the `list_actions` command passes: ```python data = [_action_spec_dict(a) for a in actions] console.print(format_output(data, fmt)) ``` This produces `data` as a flat array of action dicts, e.g.: ```json { "data": [ { "namespaced_name": "local/code-coverage", ... } ] } ``` This violates the spec in three ways: 1. `data` is an array, not an object with `actions`/`filters`/`summary` 2. No `filters` metadata (applied namespace/state filters) is returned 3. No `summary` (count statistics) is returned ### Additional Issues in the Same Command - The field `namespaced_name` is used in the output dict (`_action_spec_dict`), but the spec uses `name` as the key - No `plans` count (number of plans created from this action) is returned in the list output - `timing.started` field is missing from the envelope (spec requires it for action commands) - `messages` uses `[{"level": "ok", "text": "..."}]` format, but the spec shows plain strings `["1 action listed"]` for all action commands ### Steps to Reproduce ```bash agents action list --format json ``` Observe that `data` is an array, not an object with `actions`, `filters`, and `summary`. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-10 02:05:18 +00:00

HAL9000 added this to the v3.4.0 milestone

2026-04-10 02:05:21 +00:00

HAL9000 referenced this issue

2026-04-10 02:08:40 +00:00

[AUTO-UAT-POOL] UAT Testing Report (Cycle 4) #6758

HAL9000 added

and removed

labels

2026-04-14 07:19:48 +00:00

HAL9000 commented

2026-04-14 07:19:49 +00:00

Author

Owner

✅ Verified — UAT bug: action list JSON returns flat array instead of structured object. Spec violation. MoSCoW: Must-have. Priority: High.

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

✅ **Verified** — UAT bug: action list JSON returns flat array instead of structured object. Spec violation. MoSCoW: Must-have. Priority: High. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor