UAT: `agents plan explain` rich output missing Impact panel, Correction panel, and `✓ OK` message #5186

New issue

Open

opened 2026-04-09 03:02:13 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 03:02:13 +00:00

Owner

Bug Report

Feature Area: Plan Lifecycle — agents plan explain CLI command
Severity: Medium — command is functional but rich output is incomplete vs spec
Source: src/cleveragents/cli/commands/plan.py lines 3841–3910

What Was Tested

Code-level analysis of the explain_decision_cmd CLI command to verify that its rich output format matches the specification.

Expected Behavior (from spec §agents plan explain, lines 14548–14611)

The spec defines a rich output with five distinct panels:

Decision panel — ID, Type, Question, Chosen, Confidence, Plan, Sequence, Created (currently partially implemented)
Alternatives Considered panel — numbered list of alternatives with (chosen) marker
Impact panel — showing:
- Downstream Decisions: N
- Downstream Child Plans: N
- Artifacts Produced: N
- Correction Impact: low|medium|high
Context Snapshot panel (when --show-context) — showing context items and hot context hash
Rationale panel (when --show-reasoning) — showing rationale text
Correction panel — showing the exact agents plan correct <id> --mode revert --guidance "..." command to use

The spec also requires a final ✓ OK Decision explained success message.

Actual Behavior

The implementation (lines 3896–3910) renders a single flat table with all fields, missing the Impact panel and Correction panel entirely:

# Current implementation — single flat table, no panels:
table = Table(title="Decision Details", show_header=False, expand=False)
table.add_column("Field", style="bold")
table.add_column("Value")
for key, val in data.items():
    table.add_row(key, str(val))
console.print(Panel(table, expand=False))
# END — no Impact panel, no Correction panel, no ✓ OK message

Specific Deviations:

Missing Impact panel: No Downstream Decisions, Downstream Child Plans, Artifacts Produced, Correction Impact display
Missing Correction panel: No agents plan correct <id> --mode revert --guidance "..." hint shown
Alternatives format: Displayed as raw JSON list instead of numbered list with (chosen) marker
Missing ✓ OK message: No success message at end of output
Sequence format: Shows integer 2 instead of "2 of 5" (N of total)

Code Location

src/cleveragents/cli/commands/plan.py lines 3841–3910 — explain_decision_cmd() function
src/cleveragents/cli/commands/plan.py lines 3803–3838 — _build_explain_dict() helper (missing impact data)

Steps to Reproduce

Create and execute a plan to generate decisions
Run agents plan tree <plan_id> to get a decision ID
Run agents plan explain <decision_id>
Observe: flat table shown instead of structured panels; no Impact or Correction panels

Impact

Users cannot see the downstream impact of a decision without running separate commands
Users cannot easily find the correction command for a specific decision
The Alternatives panel doesn't clearly show which option was chosen
Inconsistent with the spec's UX design for decision exploration

#4708 — JSON/YAML output format also deviates from spec (separate issue)
Part of #4958 (EPIC: Decision Recording & Tree Visualization)

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

## Bug Report **Feature Area:** Plan Lifecycle — `agents plan explain` CLI command **Severity:** Medium — command is functional but rich output is incomplete vs spec **Source:** `src/cleveragents/cli/commands/plan.py` lines 3841–3910 --- ## What Was Tested Code-level analysis of the `explain_decision_cmd` CLI command to verify that its rich output format matches the specification. ## Expected Behavior (from spec §agents plan explain, lines 14548–14611) The spec defines a rich output with **five distinct panels**: 1. **Decision panel** — ID, Type, Question, Chosen, Confidence, Plan, Sequence, Created (currently partially implemented) 2. **Alternatives Considered panel** — numbered list of alternatives with `(chosen)` marker 3. **Impact panel** — showing: - `Downstream Decisions: N` - `Downstream Child Plans: N` - `Artifacts Produced: N` - `Correction Impact: low|medium|high` 4. **Context Snapshot panel** (when `--show-context`) — showing context items and hot context hash 5. **Rationale panel** (when `--show-reasoning`) — showing rationale text 6. **Correction panel** — showing the exact `agents plan correct <id> --mode revert --guidance "..."` command to use The spec also requires a final `✓ OK Decision explained` success message. ## Actual Behavior The implementation (lines 3896–3910) renders a single flat table with all fields, missing the Impact panel and Correction panel entirely: ```python # Current implementation — single flat table, no panels: table = Table(title="Decision Details", show_header=False, expand=False) table.add_column("Field", style="bold") table.add_column("Value") for key, val in data.items(): table.add_row(key, str(val)) console.print(Panel(table, expand=False)) # END — no Impact panel, no Correction panel, no ✓ OK message ``` ### Specific Deviations: 1. **Missing Impact panel**: No `Downstream Decisions`, `Downstream Child Plans`, `Artifacts Produced`, `Correction Impact` display 2. **Missing Correction panel**: No `agents plan correct <id> --mode revert --guidance "..."` hint shown 3. **Alternatives format**: Displayed as raw JSON list instead of numbered list with `(chosen)` marker 4. **Missing `✓ OK` message**: No success message at end of output 5. **Sequence format**: Shows integer `2` instead of `"2 of 5"` (N of total) ## Code Location - `src/cleveragents/cli/commands/plan.py` lines 3841–3910 — `explain_decision_cmd()` function - `src/cleveragents/cli/commands/plan.py` lines 3803–3838 — `_build_explain_dict()` helper (missing impact data) ## Steps to Reproduce 1. Create and execute a plan to generate decisions 2. Run `agents plan tree <plan_id>` to get a decision ID 3. Run `agents plan explain <decision_id>` 4. Observe: flat table shown instead of structured panels; no Impact or Correction panels ## Impact - Users cannot see the downstream impact of a decision without running separate commands - Users cannot easily find the correction command for a specific decision - The Alternatives panel doesn't clearly show which option was chosen - Inconsistent with the spec's UX design for decision exploration ## Related Issues - #4708 — JSON/YAML output format also deviates from spec (separate issue) - Part of #4958 (EPIC: Decision Recording & Tree Visualization) --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 03:02:15 +00:00

HAL9000 referenced this issue

2026-04-09 03:08:46 +00:00

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