UAT: plan status doesn't list checkpoints with ULID and timestamp (v3.3.0 deliverable #7) #6035

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

Summary

The agents plan status command does not list checkpoints with their ULID and timestamp, which is required by v3.3.0 deliverable #7. The spec's "Execution Detail" panel shows Checkpoints: 2 created and the v3.3.0 acceptance criteria states "plan show lists checkpoints; each has a ULID and timestamp."

Expected Behavior (from spec §agents plan status and v3.3.0 deliverables)

v3.3.0 Deliverable #7: "Checkpoint creation during Execute — plan show lists checkpoints; each has a ULID and timestamp"

The spec's plan status Rich output (lines 13604–13610) shows:

╭─ Execution Detail ──────────╮
│ Sandbox: git_worktree       │
│ Tool Calls: 8               │
│ Files Modified: 3           │
│ Child Plans: 1/2 complete   │
│ Checkpoints: 2 created      │
╰─────────────────────────────╯

And the JSON output (lines 13685–13691) includes:

"execution": {
  "sandbox": "git_worktree",
  "tool_calls": 8,
  "files_modified": 3,
  "child_plans": "1/2 complete",
  "checkpoints": 2
}

Additionally, the deliverable requires that each checkpoint has a ULID and timestamp visible in the plan status output.

Actual Behavior

The plan status command (src/cleveragents/cli/commands/plan.py):

  1. No "Execution Detail" panel_print_lifecycle_plan() (lines 1398–1595) does not render an "Execution Detail" panel with sandbox strategy, tool calls, files modified, child plans, or checkpoint count.

  2. No checkpoint list — Only last_checkpoint_id is shown (line 1536–1537), not a list of all checkpoints with ULIDs and timestamps.

  3. JSON output missing execution block_plan_spec_dict() (lines 223–297) does not include an execution key with sandbox, tool_calls, files_modified, child_plans, or checkpoints fields.

Impact

  • v3.3.0 deliverable #7 is not verifiable: "plan show lists checkpoints; each has a ULID and timestamp"
  • Users cannot see how many checkpoints exist for a plan without querying the database directly
  • The spec's "Execution Detail" panel is entirely absent from the implementation
  • JSON consumers expecting data.execution.checkpoints will get undefined

Code Locations

  • src/cleveragents/cli/commands/plan.py lines 1398–1595 (_print_lifecycle_plan — missing Execution Detail panel)
  • src/cleveragents/cli/commands/plan.py lines 223–297 (_plan_spec_dict — missing execution block)
  • src/cleveragents/application/services/checkpoint_service.pylist_checkpoints() exists and could be called

Fix Required

  1. Add "Execution Detail" panel to _print_lifecycle_plan() showing: sandbox strategy, tool calls, files modified, child plans count, checkpoint count
  2. Add execution block to _plan_spec_dict() JSON output
  3. Either list all checkpoints inline (ULID + timestamp) or provide a separate agents plan checkpoints <PLAN_ID> command
  4. Wire CheckpointService.list_checkpoints(plan_id) into the plan status command to get the checkpoint count and list

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

## Summary The `agents plan status` command does not list checkpoints with their ULID and timestamp, which is required by v3.3.0 deliverable #7. The spec's "Execution Detail" panel shows `Checkpoints: 2 created` and the v3.3.0 acceptance criteria states "`plan show` lists checkpoints; each has a ULID and timestamp." ## Expected Behavior (from spec §agents plan status and v3.3.0 deliverables) **v3.3.0 Deliverable #7**: "Checkpoint creation during Execute — `plan show` lists checkpoints; each has a ULID and timestamp" The spec's `plan status` Rich output (lines 13604–13610) shows: ``` ╭─ Execution Detail ──────────╮ │ Sandbox: git_worktree │ │ Tool Calls: 8 │ │ Files Modified: 3 │ │ Child Plans: 1/2 complete │ │ Checkpoints: 2 created │ ╰─────────────────────────────╯ ``` And the JSON output (lines 13685–13691) includes: ```json "execution": { "sandbox": "git_worktree", "tool_calls": 8, "files_modified": 3, "child_plans": "1/2 complete", "checkpoints": 2 } ``` Additionally, the deliverable requires that each checkpoint has a ULID and timestamp visible in the plan status output. ## Actual Behavior The `plan status` command (`src/cleveragents/cli/commands/plan.py`): 1. **No "Execution Detail" panel** — `_print_lifecycle_plan()` (lines 1398–1595) does not render an "Execution Detail" panel with sandbox strategy, tool calls, files modified, child plans, or checkpoint count. 2. **No checkpoint list** — Only `last_checkpoint_id` is shown (line 1536–1537), not a list of all checkpoints with ULIDs and timestamps. 3. **JSON output missing `execution` block** — `_plan_spec_dict()` (lines 223–297) does not include an `execution` key with `sandbox`, `tool_calls`, `files_modified`, `child_plans`, or `checkpoints` fields. ## Impact - v3.3.0 deliverable #7 is not verifiable: "plan show lists checkpoints; each has a ULID and timestamp" - Users cannot see how many checkpoints exist for a plan without querying the database directly - The spec's "Execution Detail" panel is entirely absent from the implementation - JSON consumers expecting `data.execution.checkpoints` will get `undefined` ## Code Locations - `src/cleveragents/cli/commands/plan.py` lines 1398–1595 (`_print_lifecycle_plan` — missing Execution Detail panel) - `src/cleveragents/cli/commands/plan.py` lines 223–297 (`_plan_spec_dict` — missing `execution` block) - `src/cleveragents/application/services/checkpoint_service.py` — `list_checkpoints()` exists and could be called ## Fix Required 1. Add "Execution Detail" panel to `_print_lifecycle_plan()` showing: sandbox strategy, tool calls, files modified, child plans count, checkpoint count 2. Add `execution` block to `_plan_spec_dict()` JSON output 3. Either list all checkpoints inline (ULID + timestamp) or provide a separate `agents plan checkpoints <PLAN_ID>` command 4. Wire `CheckpointService.list_checkpoints(plan_id)` into the `plan status` command to get the checkpoint count and list --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester
HAL9000 added this to the v3.2.0 milestone 2026-04-09 14:31:51 +00:00
Author
Owner

Label compliance fix applied:

  • Added missing labels and/or milestone 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 and/or milestone 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.

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