UAT: agents plan execute rich output missing spec-required panels — Execution, Sandbox, Strategy Summary, and Progress panels not rendered #2899

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

Metadata

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

Background and Context

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

Current Behavior

agents plan execute <PLAN_ID> renders a single panel titled "Plan Executed" with all fields merged together. No Sandbox, Strategy Summary, or Progress panels are shown.

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

Expected Behavior

Per the spec, agents plan execute must render 4 separate Rich panels:

  1. Execution — Plan ID, Phase (execute), State, Action, Project, Executor
  2. Sandbox — Sandbox ID/path, Status, Isolation level, Files available
  3. Strategy Summary — Number of decisions, steps planned, estimated tokens, estimated cost
  4. Progress — Current step, steps completed/total, sub-plans, ETA

All panels followed by ✓ OK Plan executed status line.

Acceptance Criteria

  • agents plan execute <PLAN_ID> renders an "Execution" panel with Plan ID, Phase, State, Action, Project, and Executor fields
  • A separate "Sandbox" panel is rendered with Sandbox ID/path, Status, Isolation level, and Files available fields
  • A separate "Strategy Summary" panel is rendered with decision count, steps planned, estimated tokens, and estimated cost
  • A separate "Progress" panel is rendered with current step, completion counts, sub-plans, and ETA
  • All 4 panels appear in the correct order as specified
  • The final ✓ OK Plan executed status line is present
  • JSON/YAML output formats are unaffected
  • All nox stages pass with coverage >= 97%

Subtasks

  • Audit execute_plan() in plan.py and identify the _print_lifecycle_plan() call to replace
  • Implement _print_plan_execute_panels(plan) helper rendering all 4 spec-required panels
  • Replace the _print_lifecycle_plan() call in execute_plan() with the new helper
  • Write Behave unit tests covering each panel's content and ordering
  • Write Robot Framework integration test for agents plan execute 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 execute rich output renders all 4 spec-required panels in the correct order
  • Behave unit tests cover all 4 panels
  • Robot Framework integration test passes for rich output
  • Commit pushed to fix/m5-plan-execute-rich-output-panels with message fix(cli): render spec-required panels in agents plan execute 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-execute-rich-output-panels` - **Commit Message**: `fix(cli): render spec-required panels in agents plan execute rich output` - **Milestone**: v3.5.0 - **Parent Epic**: #397 ## Background and Context The spec (`docs/specification.md` §agents plan execute) requires the rich output to include 4 separate panels: "Execution", "Sandbox", "Strategy Summary", and "Progress". The current implementation in `src/cleveragents/cli/commands/plan.py` calls `_print_lifecycle_plan(plan, title="Plan Executed")` which renders a single monolithic panel with all fields merged together. The spec-required "Sandbox", "Strategy Summary", and "Progress" panels are completely absent. ## Current Behavior `agents plan execute <PLAN_ID>` renders a single panel titled "Plan Executed" with all fields merged together. No Sandbox, Strategy Summary, or Progress panels are shown. **Code location**: `src/cleveragents/cli/commands/plan.py`, `execute_plan()` function (around line 1732). ## Expected Behavior Per the spec, `agents plan execute` must render 4 separate Rich panels: 1. **Execution** — Plan ID, Phase (execute), State, Action, Project, Executor 2. **Sandbox** — Sandbox ID/path, Status, Isolation level, Files available 3. **Strategy Summary** — Number of decisions, steps planned, estimated tokens, estimated cost 4. **Progress** — Current step, steps completed/total, sub-plans, ETA All panels followed by `✓ OK Plan executed` status line. ## Acceptance Criteria - [ ] `agents plan execute <PLAN_ID>` renders an "Execution" panel with Plan ID, Phase, State, Action, Project, and Executor fields - [ ] A separate "Sandbox" panel is rendered with Sandbox ID/path, Status, Isolation level, and Files available fields - [ ] A separate "Strategy Summary" panel is rendered with decision count, steps planned, estimated tokens, and estimated cost - [ ] A separate "Progress" panel is rendered with current step, completion counts, sub-plans, and ETA - [ ] All 4 panels appear in the correct order as specified - [ ] The final `✓ OK Plan executed` status line is present - [ ] JSON/YAML output formats are unaffected - [ ] All nox stages pass with coverage >= 97% ## Subtasks - [ ] Audit `execute_plan()` in `plan.py` and identify the `_print_lifecycle_plan()` call to replace - [ ] Implement `_print_plan_execute_panels(plan)` helper rendering all 4 spec-required panels - [ ] Replace the `_print_lifecycle_plan()` call in `execute_plan()` with the new helper - [ ] Write Behave unit tests covering each panel's content and ordering - [ ] Write Robot Framework integration test for `agents plan execute` 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 execute` rich output renders all 4 spec-required panels in the correct order - [ ] Behave unit tests cover all 4 panels - [ ] Robot Framework integration test passes for rich output - [ ] Commit pushed to `fix/m5-plan-execute-rich-output-panels` with message `fix(cli): render spec-required panels in agents plan execute 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 execute) - 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 execute`) - 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#2899
No description provided.