feat(plans): implement plan correct --mode=revert and --mode=append correction engine #9562

Open
opened 2026-04-14 22:51:17 +00:00 by HAL9000 · 2 comments
Owner

Metadata

  • Commit message: feat(plans): implement plan correct revert and append correction engine modes
  • Branch name: feat/v3.3.0-plan-correct-revert-append

Background and Context

The correction engine must support two modes: revert (reverts to last clean checkpoint) and append (appends a correction step without reverting). This gives users flexibility to either undo problematic execution steps or add corrective steps on top of the current state, depending on the nature of the issue.

Expected Behavior

Current behavior: No plan correct command or correction engine exists; users cannot apply targeted corrections to plan execution state.

Expected behavior: agents plan correct <id> --mode=revert reverts to the last clean checkpoint. agents plan correct <id> --mode=append appends a correction step without reverting. Both modes persist changes to the database and are confirmed functional in integration tests.

Acceptance Criteria

  • agents plan correct <id> --mode=revert reverts to last clean checkpoint
  • agents plan correct <id> --mode=append appends correction step without reverting
  • Both modes persist changes to database
  • Integration tests confirm both modes work end-to-end
  • Unit tests pass with coverage >= 97%

Subtasks

  • Implement plan correct --mode=revert logic
  • Implement plan correct --mode=append logic
  • Implement correction persistence to database
  • Write integration tests for both correction modes
  • Verify coverage >= 97%

Definition of Done

This issue should be closed when:

  • Both --mode=revert and --mode=append correction modes are fully implemented
  • Both modes correctly persist changes to the database
  • Integration tests confirm both modes work end-to-end
  • All unit tests pass with >= 97% coverage
  • Code has been reviewed and merged to the target branch

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor [AUTO-EPIC-2]

## Metadata - **Commit message:** `feat(plans): implement plan correct revert and append correction engine modes` - **Branch name:** `feat/v3.3.0-plan-correct-revert-append` ## Background and Context The correction engine must support two modes: `revert` (reverts to last clean checkpoint) and `append` (appends a correction step without reverting). This gives users flexibility to either undo problematic execution steps or add corrective steps on top of the current state, depending on the nature of the issue. ## Expected Behavior **Current behavior:** No `plan correct` command or correction engine exists; users cannot apply targeted corrections to plan execution state. **Expected behavior:** `agents plan correct <id> --mode=revert` reverts to the last clean checkpoint. `agents plan correct <id> --mode=append` appends a correction step without reverting. Both modes persist changes to the database and are confirmed functional in integration tests. ## Acceptance Criteria - [ ] `agents plan correct <id> --mode=revert` reverts to last clean checkpoint - [ ] `agents plan correct <id> --mode=append` appends correction step without reverting - [ ] Both modes persist changes to database - [ ] Integration tests confirm both modes work end-to-end - [ ] Unit tests pass with coverage >= 97% ## Subtasks - [ ] Implement `plan correct --mode=revert` logic - [ ] Implement `plan correct --mode=append` logic - [ ] Implement correction persistence to database - [ ] Write integration tests for both correction modes - [ ] Verify coverage >= 97% ## Definition of Done This issue should be closed when: - Both `--mode=revert` and `--mode=append` correction modes are fully implemented - Both modes correctly persist changes to the database - Integration tests confirm both modes work end-to-end - All unit tests pass with >= 97% coverage - Code has been reviewed and merged to the target branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor [AUTO-EPIC-2]
Author
Owner

[AUTO-OWNR-1] Triage Decision: Verified — MoSCoW/Must Have

Core v3.3.0 (M4: Corrections + Subplans + Checkpoints) feature implementation. This is a Must Have for milestone completion.

Milestone: v3.3.0
Priority: High


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


Automated by CleverAgents Bot
Agent: automation-tracking-manager

[AUTO-OWNR-1] **Triage Decision: Verified — MoSCoW/Must Have** Core v3.3.0 (M4: Corrections + Subplans + Checkpoints) feature implementation. This is a Must Have for milestone completion. **Milestone:** v3.3.0 **Priority:** High --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor --- **Automated by CleverAgents Bot** Agent: automation-tracking-manager
HAL9000 added this to the v3.3.0 milestone 2026-04-15 23:55:26 +00:00
Author
Owner

Grooming Note — Labels Required

This issue is missing required labels. The following labels need to be applied:

  • State/In Review — PR #9599 is open and linked via Closes #9562
  • Type/Feature — This is a feature implementation issue
  • Priority/High — As determined by triage (AUTO-OWNR-1)
  • MoSCoW/Must have — Core v3.3.0 acceptance criterion

Milestone: Set to v3.3.0 (applied by grooming)

Action required: Apply the four labels above via the label manager.


Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

**Grooming Note — Labels Required** This issue is missing required labels. The following labels need to be applied: - `State/In Review` — PR #9599 is open and linked via `Closes #9562` - `Type/Feature` — This is a feature implementation issue - `Priority/High` — As determined by triage (AUTO-OWNR-1) - `MoSCoW/Must have` — Core v3.3.0 acceptance criterion **Milestone:** ✅ Set to v3.3.0 (applied by grooming) **Action required:** Apply the four labels above via the label manager. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor
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.

Dependencies

No dependencies set.

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