UAT: agents plan status rich output missing spec-required panels — Progress, Timing, Execution Detail, and Cost panels not rendered #2898

Open
opened 2026-04-05 02:45:38 +00:00 by freemo · 3 comments
Owner

Metadata

  • Branch: fix/m5-plan-status-rich-output-panels
  • Commit Message: fix(cli): render spec-required panels in agents plan status rich output
  • Milestone: v3.5.0
  • Parent Epic: #397

Background and Context

The spec (docs/specification.md §agents plan status) requires the rich output to include 5 separate panels: "Plan Status", "Progress", "Timing", "Execution Detail", and "Cost". The current implementation in src/cleveragents/cli/commands/plan.py calls _print_lifecycle_plan(plan, title="Plan Status") which renders a single monolithic panel with all fields merged together. The spec-required "Progress", "Timing", "Execution Detail", and "Cost" panels are completely absent.

Current Behavior

agents plan status <PLAN_ID> renders a single panel titled "Plan Status" with all fields merged together. No Progress, Timing, Execution Detail, or Cost panels are shown.

Code location: src/cleveragents/cli/commands/plan.py, plan_status() function (around line 2093).

Expected Behavior

Per the spec, agents plan status must render 5 separate Rich panels:

  1. Plan Status — Plan ID, Phase, State, Action, Project, Automation
  2. Progress — Steps completed/total, sub-plans completed/total, current step description
  3. Timing — Started At, Elapsed, Estimated Remaining, ETA
  4. Execution Detail — Executor, Sandbox status, Files Modified, Checkpoints
  5. Cost — Token usage (prompt/completion/total), estimated cost, budget remaining

All panels followed by ✓ OK status line.

Acceptance Criteria

  • agents plan status <PLAN_ID> renders a "Plan Status" panel with Plan ID, Phase, State, Action, Project, and Automation fields
  • A separate "Progress" panel is rendered with step and sub-plan completion counts and current step
  • A separate "Timing" panel is rendered with Started At, Elapsed, Estimated Remaining, and ETA fields
  • A separate "Execution Detail" panel is rendered with Executor, Sandbox status, Files Modified, and Checkpoints fields
  • A separate "Cost" panel is rendered with token usage and budget information
  • All 5 panels appear in the correct order as specified
  • JSON/YAML output formats are unaffected
  • All nox stages pass with coverage >= 97%

Subtasks

  • Audit plan_status() in plan.py and identify the _print_lifecycle_plan() call to replace
  • Implement _print_plan_status_panels(plan) helper rendering all 5 spec-required panels
  • Replace the _print_lifecycle_plan() call in plan_status() with the new helper
  • Write Behave unit tests covering each panel's content and ordering
  • Write Robot Framework integration test for agents plan status rich output
  • Verify JSON/YAML output paths are unaffected
  • Run nox and confirm all stages pass with coverage >= 97%

Definition of Done

  • All subtasks above are checked
  • agents plan status rich output renders all 5 spec-required panels in the correct order
  • Behave unit tests cover all 5 panels
  • Robot Framework integration test passes for rich output
  • Commit pushed to fix/m5-plan-status-rich-output-panels with message fix(cli): render spec-required panels in agents plan status rich output
  • PR merged and issue closed
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-new-issue-creator

## Metadata - **Branch**: `fix/m5-plan-status-rich-output-panels` - **Commit Message**: `fix(cli): render spec-required panels in agents plan status rich output` - **Milestone**: v3.5.0 - **Parent Epic**: #397 ## Background and Context The spec (`docs/specification.md` §agents plan status) requires the rich output to include 5 separate panels: "Plan Status", "Progress", "Timing", "Execution Detail", and "Cost". The current implementation in `src/cleveragents/cli/commands/plan.py` calls `_print_lifecycle_plan(plan, title="Plan Status")` which renders a single monolithic panel with all fields merged together. The spec-required "Progress", "Timing", "Execution Detail", and "Cost" panels are completely absent. ## Current Behavior `agents plan status <PLAN_ID>` renders a single panel titled "Plan Status" with all fields merged together. No Progress, Timing, Execution Detail, or Cost panels are shown. **Code location**: `src/cleveragents/cli/commands/plan.py`, `plan_status()` function (around line 2093). ## Expected Behavior Per the spec, `agents plan status` must render 5 separate Rich panels: 1. **Plan Status** — Plan ID, Phase, State, Action, Project, Automation 2. **Progress** — Steps completed/total, sub-plans completed/total, current step description 3. **Timing** — Started At, Elapsed, Estimated Remaining, ETA 4. **Execution Detail** — Executor, Sandbox status, Files Modified, Checkpoints 5. **Cost** — Token usage (prompt/completion/total), estimated cost, budget remaining All panels followed by `✓ OK` status line. ## Acceptance Criteria - [ ] `agents plan status <PLAN_ID>` renders a "Plan Status" panel with Plan ID, Phase, State, Action, Project, and Automation fields - [ ] A separate "Progress" panel is rendered with step and sub-plan completion counts and current step - [ ] A separate "Timing" panel is rendered with Started At, Elapsed, Estimated Remaining, and ETA fields - [ ] A separate "Execution Detail" panel is rendered with Executor, Sandbox status, Files Modified, and Checkpoints fields - [ ] A separate "Cost" panel is rendered with token usage and budget information - [ ] All 5 panels appear in the correct order as specified - [ ] JSON/YAML output formats are unaffected - [ ] All nox stages pass with coverage >= 97% ## Subtasks - [ ] Audit `plan_status()` in `plan.py` and identify the `_print_lifecycle_plan()` call to replace - [ ] Implement `_print_plan_status_panels(plan)` helper rendering all 5 spec-required panels - [ ] Replace the `_print_lifecycle_plan()` call in `plan_status()` with the new helper - [ ] Write Behave unit tests covering each panel's content and ordering - [ ] Write Robot Framework integration test for `agents plan status` rich output - [ ] Verify JSON/YAML output paths are unaffected - [ ] Run `nox` and confirm all stages pass with coverage >= 97% ## Definition of Done - [ ] All subtasks above are checked - [ ] `agents plan status` rich output renders all 5 spec-required panels in the correct order - [ ] Behave unit tests cover all 5 panels - [ ] Robot Framework integration test passes for rich output - [ ] Commit pushed to `fix/m5-plan-status-rich-output-panels` with message `fix(cli): render spec-required panels in agents plan status rich output` - [ ] PR merged and issue closed - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-new-issue-creator
freemo added this to the v3.5.0 milestone 2026-04-05 02:46:51 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Medium (confirmed)
  • MoSCoW: Should Have — rich output panels missing per spec

Valid UAT finding verified during batch triage.


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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium (confirmed) - **MoSCoW**: Should Have — rich output panels missing per spec Valid UAT finding verified during batch triage. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

Milestone Triage Decision: Moved to Backlog

This CLI panel implementation issue has been moved out of v3.5.0 during aggressive milestone triage. While important for spec compliance, it does not block core autonomy hardening functionality.

Reasoning:

  • v3.5.0 focus: Essential autonomy hardening (guard enforcement, A2A facade, plan lifecycle)
  • This issue: CLI spec panels (plan status) - UX enhancement
  • Impact: UX consistency, not functional capability

Will be addressed in a future milestone focused on CLI polish and spec compliance.

**Milestone Triage Decision: Moved to Backlog** This CLI panel implementation issue has been moved out of v3.5.0 during aggressive milestone triage. While important for spec compliance, it does not block core autonomy hardening functionality. **Reasoning:** - v3.5.0 focus: Essential autonomy hardening (guard enforcement, A2A facade, plan lifecycle) - This issue: CLI spec panels (`plan status`) - UX enhancement - Impact: UX consistency, not functional capability Will be addressed in a future milestone focused on CLI polish and spec compliance.
Author
Owner

This issue has been moved to the backlog as part of an aggressive grooming of the v3.5.0 milestone. It has been deemed non-critical for the minimal viability of the milestone and will be addressed in a future release.

This issue has been moved to the backlog as part of an aggressive grooming of the v3.5.0 milestone. It has been deemed non-critical for the minimal viability of the milestone and will be addressed in a future release.
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
#397 Epic: Server & Autonomy Infrastructure
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#2898
No description provided.