cleveragents/cleveragents-core

Fork 3

UAT: `plan status` does not display child subplan statuses — v3.3.0 Deliverable #4 unmet #5348

New issue

Open

opened 2026-04-09 05:56:48 +00:00 by HAL9000 · 3 comments

HAL9000 commented

2026-04-09 05:56:48 +00:00

Owner

Bug Report

Feature Area: subplans-checkpoints
Severity: Critical — blocks v3.3.0 milestone acceptance
Spec Reference: v3.3.0 Deliverable #4 — "Parent plan tracks all subplan statuses"

What Was Tested

The agents plan status <parent_plan_id> command output when a parent plan has spawned child subplans.

Expected Behavior (from spec)

Per the v3.3.0 specification (Deliverable #4):

Parent plan tracks all subplan statuses — plan show <parent_id> lists child plan statuses

The spec example output shows:

╭─ Execution Detail ──────────╮
│ Child Plans: 1/2 complete   │
╰─────────────────────────────╯

And from agents plan tree:

╭─ Child Plans ──────────────────────────────────────╮
│ ID          Phase    State                         │
│ ──────────  ───────  ─────────                     │
│ 01HXM9F1A   execute  processing                    │
│ 01HXM9F2B   execute  queued                        │
╰────────────────────────────────────────────────────╯

Actual Behavior

The _print_lifecycle_plan() function in src/cleveragents/cli/commands/plan.py (used by plan status) does not display subplan_statuses at all. The _plan_spec_dict() function (used for JSON/YAML output) also omits subplan_statuses and subplan_count.

Code Location

src/cleveragents/cli/commands/plan.py, function _print_lifecycle_plan() (line 1398)
src/cleveragents/cli/commands/plan.py, function _plan_spec_dict() (line 223)

The domain model Plan.subplan_statuses is correctly populated by SubplanService.spawn() and SubplanExecutionService.execute_all(), and Plan.as_cli_dict() does include subplan_count (line 1125). However, neither _print_lifecycle_plan() nor _plan_spec_dict() renders this data.

Steps to Reproduce

Create a parent plan with subplan_config set
Spawn child subplans via SubplanService.spawn()
Run agents plan status <parent_plan_id>
Observe: no child plan statuses are shown

Impact

This is a critical gap in v3.3.0 Deliverable #4. The verifiable check for this deliverable is "plan show <parent_id> lists child plan statuses" — which currently fails.

Fix Required

Add subplan status rendering to _print_lifecycle_plan():

Show a "Child Plans" section listing each SubplanStatus with subplan_id, action_name, status, started_at, completed_at, files_changed
Show summary count (e.g., "Child Plans: 1/2 complete")
Add subplan_statuses to _plan_spec_dict() for JSON/YAML output

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

## Bug Report **Feature Area**: subplans-checkpoints **Severity**: Critical — blocks v3.3.0 milestone acceptance **Spec Reference**: v3.3.0 Deliverable #4 — "Parent plan tracks all subplan statuses" --- ## What Was Tested The `agents plan status <parent_plan_id>` command output when a parent plan has spawned child subplans. ## Expected Behavior (from spec) Per the v3.3.0 specification (Deliverable #4): > **Parent plan tracks all subplan statuses** — `plan show <parent_id>` lists child plan statuses The spec example output shows: ``` ╭─ Execution Detail ──────────╮ │ Child Plans: 1/2 complete │ ╰─────────────────────────────╯ ``` And from `agents plan tree`: ``` ╭─ Child Plans ──────────────────────────────────────╮ │ ID Phase State │ │ ────────── ─────── ───────── │ │ 01HXM9F1A execute processing │ │ 01HXM9F2B execute queued │ ╰────────────────────────────────────────────────────╯ ``` ## Actual Behavior The `_print_lifecycle_plan()` function in `src/cleveragents/cli/commands/plan.py` (used by `plan status`) does **not** display `subplan_statuses` at all. The `_plan_spec_dict()` function (used for JSON/YAML output) also omits `subplan_statuses` and `subplan_count`. ## Code Location - `src/cleveragents/cli/commands/plan.py`, function `_print_lifecycle_plan()` (line 1398) - `src/cleveragents/cli/commands/plan.py`, function `_plan_spec_dict()` (line 223) The domain model `Plan.subplan_statuses` is correctly populated by `SubplanService.spawn()` and `SubplanExecutionService.execute_all()`, and `Plan.as_cli_dict()` does include `subplan_count` (line 1125). However, neither `_print_lifecycle_plan()` nor `_plan_spec_dict()` renders this data. ## Steps to Reproduce 1. Create a parent plan with `subplan_config` set 2. Spawn child subplans via `SubplanService.spawn()` 3. Run `agents plan status <parent_plan_id>` 4. Observe: no child plan statuses are shown ## Impact This is a critical gap in v3.3.0 Deliverable #4. The verifiable check for this deliverable is "`plan show <parent_id>` lists child plan statuses" — which currently fails. ## Fix Required Add subplan status rendering to `_print_lifecycle_plan()`: - Show a "Child Plans" section listing each `SubplanStatus` with `subplan_id`, `action_name`, `status`, `started_at`, `completed_at`, `files_changed` - Show summary count (e.g., "Child Plans: 1/2 complete") - Add `subplan_statuses` to `_plan_spec_dict()` for JSON/YAML output --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 05:57:28 +00:00

HAL9000 added this to the v3.3.0 milestone

2026-04-09 05:57:32 +00:00

HAL9000 added the

State

Unverified

label

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

HAL9000 commented

2026-04-09 06:01:26 +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

HAL9000 added a new dependency

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

#4972 EPIC: Subplan Spawning & Parallel Execution — Three-Way Merge

HAL9000 commented

2026-04-09 06:11:33 +00:00

Author

Owner

Hierarchical Compliance Fix: Linked to Epic #4972 (Subplan Spawning & Parallel Execution — Three-Way Merge) — this issue is part of the subplan execution system.

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

**Hierarchical Compliance Fix**: Linked to Epic #4972 (Subplan Spawning & Parallel Execution — Three-Way Merge) — this issue is part of the subplan execution system. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner

HAL9000 commented

2026-04-09 06:12:34 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Critical — v3.3.0 Deliverable #4 verifiable check: "plan show <parent_id> lists child plan statuses" — currently fails because _print_lifecycle_plan() never renders subplan_statuses
Milestone: v3.3.0 — direct acceptance criterion blocker
Story Points: 2 — S — requires adding subplan status rendering to _print_lifecycle_plan() and _plan_spec_dict()
MoSCoW: Must Have — v3.3.0 cannot be accepted without this. Parent plan tracking of subplan statuses is an explicit acceptance criterion.
Parent Epic: Needs linking to the subplans/checkpoints epic

Triage Rationale: The domain model correctly tracks subplan_statuses — this is a display gap in the CLI. The fix is well-scoped and low-risk.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Critical — v3.3.0 Deliverable #4 verifiable check: "`plan show <parent_id>` lists child plan statuses" — currently fails because `_print_lifecycle_plan()` never renders `subplan_statuses` - **Milestone**: v3.3.0 — direct acceptance criterion blocker - **Story Points**: 2 — S — requires adding subplan status rendering to `_print_lifecycle_plan()` and `_plan_spec_dict()` - **MoSCoW**: Must Have — v3.3.0 cannot be accepted without this. Parent plan tracking of subplan statuses is an explicit acceptance criterion. - **Parent Epic**: Needs linking to the subplans/checkpoints epic **Triage Rationale**: The domain model correctly tracks `subplan_statuses` — this is a display gap in the CLI. The fix is well-scoped and low-risk. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed

labels

2026-04-09 06:12:47 +00:00

HAL9000 referenced this issue