UAT: plan diff --correction returns placeholder instead of diff #6977

New issue

Open

opened 2026-04-10 06:09:55 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-10 06:09:55 +00:00

Owner

What was tested

Executed agents plan diff --correction <CORRECTION_ATTEMPT_ID> after creating a plan with the v3 lifecycle

Expected behavior (spec reference)

According to docs/specification.md (Plan Lifecycle System > CLI > agents plan diff), the command must render a "Correction Diff" panel (and JSON/YAML envelopes) with:
- Correction metadata (correction ID, original decision, mode)
- File-level changes compared between the original decision and the correction attempt
- Summary counts for files changed

Actual behavior

The CLI prints a placeholder panel:

╭─────────────── Correction Diff ───────────────╮
│ Correction Attempt: <ID>                      │
│ Plan: <PLAN_ID>                               │
│                                               │
│ Correction diff will be available after M4.2. │
╰───────────────────────────────────────────────╯

No diff data, file summary, or structured output is produced.

Steps to Reproduce

From a clean checkout of 51aab18411
Run agents plan use local/test-action local/project (any action/project is fine)
Run agents plan diff --correction 01TESTCORRECTION123456789ABCDEFG
Observe the placeholder output instead of the spec-defined correction diff

Code locations

src/cleveragents/cli/commands/plan.py (plan_diff) short-circuits the --correction branch and prints the stub panel instead of calling into PlanApplyService.diff

Impact

Users cannot review correction diffs as required by the Plan Lifecycle specification, blocking correction workflows and spec compliance.

## What was tested - Executed `agents plan diff --correction <CORRECTION_ATTEMPT_ID>` after creating a plan with the v3 lifecycle ## Expected behavior (spec reference) - According to `docs/specification.md` (Plan Lifecycle System > CLI > `agents plan diff`), the command must render a "Correction Diff" panel (and JSON/YAML envelopes) with: - Correction metadata (correction ID, original decision, mode) - File-level changes compared between the original decision and the correction attempt - Summary counts for files changed ## Actual behavior - The CLI prints a placeholder panel: ``` ╭─────────────── Correction Diff ───────────────╮ │ Correction Attempt: <ID> │ │ Plan: <PLAN_ID> │ │ │ │ Correction diff will be available after M4.2. │ ╰───────────────────────────────────────────────╯ ``` - No diff data, file summary, or structured output is produced. ## Steps to Reproduce 1. From a clean checkout of 51aab184112728471a44d5a91c334663cf8cd016 2. Run `agents plan use local/test-action local/project` (any action/project is fine) 3. Run `agents plan diff --correction 01TESTCORRECTION123456789ABCDEFG` 4. Observe the placeholder output instead of the spec-defined correction diff ## Code locations - `src/cleveragents/cli/commands/plan.py` (`plan_diff`) short-circuits the `--correction` branch and prints the stub panel instead of calling into `PlanApplyService.diff` ## Impact - Users cannot review correction diffs as required by the Plan Lifecycle specification, blocking correction workflows and spec compliance.

Rows
Columns