UAT: plan list --applied phase filter is missing — applied plans cannot be listed by phase #5433

New issue

Open

opened 2026-04-09 06:40:32 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 06:40:32 +00:00

Owner

Bug Report

Feature Area: Plan Lifecycle Core — agents plan list
Severity: Priority/Backlog (UX gap — applied plans are still accessible via plan status)

What Was Tested

Code-level analysis of agents plan list --phase applied against the specification.

Expected Behavior (from spec)

The agents plan list --phase applied command should list all plans that have completed the Apply phase with APPLIED terminal state. The CLI help text at src/cleveragents/cli/commands/plan.py line 2534 explicitly lists applied as a valid phase value: "Filter by phase (strategize, execute, apply, applied)".

Actual Behavior

The PlanPhase enum at src/cleveragents/domain/models/core/plan.py lines 79–94 only defines four phases:

class PlanPhase(StrEnum):
    ACTION = "action"
    STRATEGIZE = "strategize"
    EXECUTE = "execute"
    APPLY = "apply"

There is no APPLIED phase. The applied state is a ProcessingState within the APPLY phase, not a separate phase. When a user runs agents plan list --phase applied, the code at line 2603 will raise a ValueError because PlanPhase("applied") is invalid:

# plan.py lines 2601-2609:
if phase:
    try:
        phase_filter = PlanPhase(phase.lower())  # ← ValueError for "applied"
    except ValueError as exc:
        console.print(
            f"[red]Invalid phase:[/red] {phase}. "
            "Valid values: strategize, execute, apply, applied"  # ← "applied" listed as valid!
        )
        raise typer.Abort() from exc

This creates a contradiction: the error message says applied is a valid value, but the code rejects it.

Impact

agents plan list --phase applied fails with "Invalid phase: applied" even though the help text says it's valid
Users cannot filter the plan list to show only completed (applied) plans using the --phase flag
The correct approach would be to use --state applied instead, but this is not documented

Code Location

Bug: src/cleveragents/cli/commands/plan.py, lines 2534 (help text) and 2601–2609 (phase validation)
Fix: Either:
1. Remove applied from the help text and document that users should use --state applied instead
2. OR add special handling for --phase applied to filter by phase=APPLY AND state=APPLIED

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

## Bug Report **Feature Area**: Plan Lifecycle Core — `agents plan list` **Severity**: Priority/Backlog (UX gap — applied plans are still accessible via `plan status`) ## What Was Tested Code-level analysis of `agents plan list --phase applied` against the specification. ## Expected Behavior (from spec) The `agents plan list --phase applied` command should list all plans that have completed the Apply phase with `APPLIED` terminal state. The CLI help text at `src/cleveragents/cli/commands/plan.py` line 2534 explicitly lists `applied` as a valid phase value: `"Filter by phase (strategize, execute, apply, applied)"`. ## Actual Behavior The `PlanPhase` enum at `src/cleveragents/domain/models/core/plan.py` lines 79–94 only defines four phases: ```python class PlanPhase(StrEnum): ACTION = "action" STRATEGIZE = "strategize" EXECUTE = "execute" APPLY = "apply" ``` There is no `APPLIED` phase. The `applied` state is a `ProcessingState` within the `APPLY` phase, not a separate phase. When a user runs `agents plan list --phase applied`, the code at line 2603 will raise a `ValueError` because `PlanPhase("applied")` is invalid: ```python # plan.py lines 2601-2609: if phase: try: phase_filter = PlanPhase(phase.lower()) # ← ValueError for "applied" except ValueError as exc: console.print( f"[red]Invalid phase:[/red] {phase}. " "Valid values: strategize, execute, apply, applied" # ← "applied" listed as valid! ) raise typer.Abort() from exc ``` This creates a contradiction: the error message says `applied` is a valid value, but the code rejects it. ## Impact - `agents plan list --phase applied` fails with "Invalid phase: applied" even though the help text says it's valid - Users cannot filter the plan list to show only completed (applied) plans using the `--phase` flag - The correct approach would be to use `--state applied` instead, but this is not documented ## Code Location - **Bug**: `src/cleveragents/cli/commands/plan.py`, lines 2534 (help text) and 2601–2609 (phase validation) - **Fix**: Either: 1. Remove `applied` from the help text and document that users should use `--state applied` instead 2. OR add special handling for `--phase applied` to filter by `phase=APPLY AND state=APPLIED` --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 06:43:32 +00:00

HAL9000 commented

2026-04-09 06:50:06 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: High — (adjusting from Critical) plan list --applied phase filter is missing, so users cannot list plans in the Applied phase. This is a spec compliance gap in the CLI.
Milestone: v3.2.0 — plan list is a core v3.2.0 CLI feature
Story Points: 1 — XS — adding "applied" to the phase filter enum is a trivial change
MoSCoW: Should Have — the spec documents --applied as a valid filter. The workaround is to list all plans and filter manually. Not a data loss issue.
Parent Epic: Needs linking to the plan CLI epic

Triage Rationale: Missing CLI filter option is a spec compliance gap. The fix is trivial (add "applied" to the phase enum), but the impact is limited — users can still find applied plans through other means.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — (adjusting from Critical) `plan list --applied` phase filter is missing, so users cannot list plans in the Applied phase. This is a spec compliance gap in the CLI. - **Milestone**: v3.2.0 — plan list is a core v3.2.0 CLI feature - **Story Points**: 1 — XS — adding "applied" to the phase filter enum is a trivial change - **MoSCoW**: Should Have — the spec documents `--applied` as a valid filter. The workaround is to list all plans and filter manually. Not a data loss issue. - **Parent Epic**: Needs linking to the plan CLI epic **Triage Rationale**: Missing CLI filter option is a spec compliance gap. The fix is trivial (add "applied" to the phase enum), but the impact is limited — users can still find applied plans through other means. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed

labels