UAT: plan diff --correction is a stub returning placeholder text instead of actual correction diff #5416

Open
opened 2026-04-09 06:36:57 +00:00 by HAL9000 · 1 comment
Owner

Bug Report

Feature Area: Plan Lifecycle Core — agents plan diff
Severity: Priority/Backlog (feature gap, not blocking core lifecycle)

What Was Tested

Code-level analysis of agents plan diff <plan_id> --correction <correction_id> against the specification.

Expected Behavior (from spec)

The agents plan diff --correction <correction_id> command should display the unified diff for a specific correction attempt, showing what changes the correction would make to the plan's changeset.

Actual Behavior

The --correction path in agents plan diff is a stub that returns a placeholder panel instead of actual diff output:

# src/cleveragents/cli/commands/plan.py lines 2949-2960
if correction:
    # Show correction-specific diff (stub: shows info panel)
    console.print(
        Panel(
            f"[bold]Correction Attempt:[/bold] {correction}\n"
            f"[bold]Plan:[/bold] {plan_id}\n\n"
            "[dim]Correction diff will be available after M4.2.[/dim]",
            title="Correction Diff",
            expand=False,
        )
    )
    return

The message "Correction diff will be available after M4.2." indicates this was a planned feature that was never implemented.

Impact

  • Users cannot inspect what a correction attempt would change before applying it
  • The --correction flag is documented in the CLI help but does not work
  • This breaks the correction workflow's review step

Code Location

  • Bug: src/cleveragents/cli/commands/plan.py, lines 2949–2960 (the plan_diff command's correction branch)
  • Fix: Implement actual correction diff retrieval from the correction service and render it as a unified diff

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

## Bug Report **Feature Area**: Plan Lifecycle Core — `agents plan diff` **Severity**: Priority/Backlog (feature gap, not blocking core lifecycle) ## What Was Tested Code-level analysis of `agents plan diff <plan_id> --correction <correction_id>` against the specification. ## Expected Behavior (from spec) The `agents plan diff --correction <correction_id>` command should display the unified diff for a specific correction attempt, showing what changes the correction would make to the plan's changeset. ## Actual Behavior The `--correction` path in `agents plan diff` is a stub that returns a placeholder panel instead of actual diff output: ```python # src/cleveragents/cli/commands/plan.py lines 2949-2960 if correction: # Show correction-specific diff (stub: shows info panel) console.print( Panel( f"[bold]Correction Attempt:[/bold] {correction}\n" f"[bold]Plan:[/bold] {plan_id}\n\n" "[dim]Correction diff will be available after M4.2.[/dim]", title="Correction Diff", expand=False, ) ) return ``` The message "Correction diff will be available after M4.2." indicates this was a planned feature that was never implemented. ## Impact - Users cannot inspect what a correction attempt would change before applying it - The `--correction` flag is documented in the CLI help but does not work - This breaks the correction workflow's review step ## Code Location - **Bug**: `src/cleveragents/cli/commands/plan.py`, lines 2949–2960 (the `plan_diff` command's correction branch) - **Fix**: Implement actual correction diff retrieval from the correction service and render it as a unified diff --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester
HAL9000 added this to the v3.4.0 milestone 2026-04-09 06:50:04 +00:00
Author
Owner

Label compliance fix applied:

  • Added missing labels to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
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.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#5416
No description provided.