feat(checkpoints): implement agents plan rollback CLI command with CheckpointService integration #5002

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

Metadata

  • Commit Message: feat(checkpoints): implement agents plan rollback CLI command with CheckpointService integration
  • Branch: feat/m4/plan-rollback-command
  • Parent Epic: #4973

Background and Context

The agents plan rollback [--yes|-y] <PLAN_ID> <CHECKPOINT_ID> command needs to be implemented. It uses CheckpointService.rollback_to_checkpoint() which currently has issues with path resolution.

Expected Behavior

  • agents plan rollback <PLAN_ID> <CHECKPOINT_ID> prompts for confirmation then rolls back
  • agents plan rollback --yes <PLAN_ID> <CHECKPOINT_ID> skips confirmation
  • CheckpointService.rollback_to_checkpoint() uses correct path resolution
  • Rich output shows rollback progress and result
  • JSON output uses spec-required envelope

Acceptance Criteria

  • agents plan rollback CLI command implemented
  • --yes / -y flag skips confirmation prompt
  • CheckpointService.rollback_to_checkpoint() path resolution fixed
  • Rich output shows rollback progress (checkpoint ID, files reverted, status)
  • JSON output uses spec-required envelope
  • Unit tests (Behave) cover rollback scenarios
  • Integration test (Robot) verifies end-to-end rollback

Subtasks

  • Implement agents plan rollback CLI command
  • Implement --yes / -y confirmation bypass
  • Fix CheckpointService.rollback_to_checkpoint() path resolution
  • Implement Rich output for rollback result
  • Implement JSON envelope output
  • Tests (Behave): Add scenarios for rollback command
  • Tests (Robot): Add integration test
  • Verify coverage >=97% via nox -s coverage_report
  • Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

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

## Metadata - **Commit Message**: `feat(checkpoints): implement agents plan rollback CLI command with CheckpointService integration` - **Branch**: `feat/m4/plan-rollback-command` - **Parent Epic**: #4973 ## Background and Context The `agents plan rollback [--yes|-y] <PLAN_ID> <CHECKPOINT_ID>` command needs to be implemented. It uses `CheckpointService.rollback_to_checkpoint()` which currently has issues with path resolution. ## Expected Behavior - `agents plan rollback <PLAN_ID> <CHECKPOINT_ID>` prompts for confirmation then rolls back - `agents plan rollback --yes <PLAN_ID> <CHECKPOINT_ID>` skips confirmation - `CheckpointService.rollback_to_checkpoint()` uses correct path resolution - Rich output shows rollback progress and result - JSON output uses spec-required envelope ## Acceptance Criteria - [ ] `agents plan rollback` CLI command implemented - [ ] `--yes` / `-y` flag skips confirmation prompt - [ ] `CheckpointService.rollback_to_checkpoint()` path resolution fixed - [ ] Rich output shows rollback progress (checkpoint ID, files reverted, status) - [ ] JSON output uses spec-required envelope - [ ] Unit tests (Behave) cover rollback scenarios - [ ] Integration test (Robot) verifies end-to-end rollback ## Subtasks - [ ] Implement `agents plan rollback` CLI command - [ ] Implement `--yes` / `-y` confirmation bypass - [ ] Fix `CheckpointService.rollback_to_checkpoint()` path resolution - [ ] Implement Rich output for rollback result - [ ] Implement JSON envelope output - [ ] Tests (Behave): Add scenarios for rollback command - [ ] Tests (Robot): Add integration test - [ ] Verify coverage >=97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.3.0 milestone 2026-04-09 01:03:25 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — Core checkpoint/subplan feature required for Decision Intelligence Legendary
  • Milestone: v3.3.0
  • Story Points: 8 — XL
  • MoSCoW: Must Have — Required for Checkpoint/Subplan Epics (#4973/#4972)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — Core checkpoint/subplan feature required for Decision Intelligence Legendary - **Milestone**: v3.3.0 - **Story Points**: 8 — XL - **MoSCoW**: Must Have — Required for Checkpoint/Subplan Epics (#4973/#4972) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
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#5002
No description provided.