cleveragents/cleveragents-core

Fork 3

Legendary: Corrections + Subplans + Checkpoints (M4) #8147

New issue

Closed

opened 2026-04-13 04:02:00 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-13 04:02:00 +00:00

Owner

Metadata

Commit message: legendary: corrections subplans and checkpoints m4
Branch name: legendary/corrections-subplans-checkpoints-m4

Background and Context

The v3.3.0 milestone (M4: Corrections + Subplans + Checkpoints) extends the core execution pipeline with plan spawning, parallel subplan execution, three-way merge strategies, checkpoint-based rollback, and the full correction engine. This Legendary is the parent of all M4 Epics.

Plans must be able to spawn child subplans during execution. Subplans execute in parallel with configurable concurrency limits. Results are merged back using three-way merge strategies. The correction engine supports revert and append modes. Checkpointing enables rollback to previous plan states.

This Legendary depends on M3 (Legendary #8145) being complete, as subplan execution builds on the decision framework. It is a prerequisite for M5 (ACMS v1 + Context Scaling) and M6 (Autonomy Hardening).

Expected Behavior

Plans spawn child subplans during execution. Subplan status tracking works for both sequential and parallel execution. Correction flow is functional (plan correct --mode revert and --mode append). Checkpoint creation and rollback (plan rollback) are functional. Three-way merge combines non-conflicting changes and surfaces conflicts to the user. Parent plan tracks all subplan statuses. Test coverage >= 97%.

Child Epics

M4 (v3.3.0) Epics

#8049 Epic: Subplan Execution & Concurrency Fixes (M4) — Priority/Critical
#8050 Epic: Plan Correction & Automation Profile Fixes (M4) — Priority/Critical

Acceptance Criteria

All child Epics (#8049, #8050) are closed and merged
Plans spawn child subplans during execution
Subplan status tracking works (sequential and/or parallel execution)
Correction flow functional (plan correct --mode revert and --mode append)
Checkpoint creation and rollback (plan rollback) functional
Merge strategy application on subplan results works correctly
Parent plan tracks all subplan statuses
Three-way merge combines non-conflicting changes; conflicts surfaced to user
Test coverage >= 97%

Dependencies

Depends on: Legendary #8145 (Decisions + Validations + Invariants — M3)

Definition of Done

This Legendary is complete when all child Epics and their constituent issues are closed and merged. All M4 acceptance criteria are verified: subplan spawning, parallel execution, three-way merge, checkpoint rollback, and correction engine all work per specification.

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Metadata - **Commit message**: `legendary: corrections subplans and checkpoints m4` - **Branch name**: `legendary/corrections-subplans-checkpoints-m4` ## Background and Context The v3.3.0 milestone (M4: Corrections + Subplans + Checkpoints) extends the core execution pipeline with plan spawning, parallel subplan execution, three-way merge strategies, checkpoint-based rollback, and the full correction engine. This Legendary is the parent of all M4 Epics. Plans must be able to spawn child subplans during execution. Subplans execute in parallel with configurable concurrency limits. Results are merged back using three-way merge strategies. The correction engine supports revert and append modes. Checkpointing enables rollback to previous plan states. This Legendary depends on M3 (Legendary #8145) being complete, as subplan execution builds on the decision framework. It is a prerequisite for M5 (ACMS v1 + Context Scaling) and M6 (Autonomy Hardening). ## Expected Behavior Plans spawn child subplans during execution. Subplan status tracking works for both sequential and parallel execution. Correction flow is functional (`plan correct --mode revert` and `--mode append`). Checkpoint creation and rollback (`plan rollback`) are functional. Three-way merge combines non-conflicting changes and surfaces conflicts to the user. Parent plan tracks all subplan statuses. Test coverage >= 97%. ## Child Epics ### M4 (v3.3.0) Epics - #8049 Epic: Subplan Execution & Concurrency Fixes (M4) — Priority/Critical - #8050 Epic: Plan Correction & Automation Profile Fixes (M4) — Priority/Critical ## Acceptance Criteria - [ ] All child Epics (#8049, #8050) are closed and merged - [ ] Plans spawn child subplans during execution - [ ] Subplan status tracking works (sequential and/or parallel execution) - [ ] Correction flow functional (`plan correct --mode revert` and `--mode append`) - [ ] Checkpoint creation and rollback (`plan rollback`) functional - [ ] Merge strategy application on subplan results works correctly - [ ] Parent plan tracks all subplan statuses - [ ] Three-way merge combines non-conflicting changes; conflicts surfaced to user - [ ] Test coverage >= 97% ## Dependencies - Depends on: Legendary #8145 (Decisions + Validations + Invariants — M3) ## Definition of Done This Legendary is complete when all child Epics and their constituent issues are closed and merged. All M4 acceptance criteria are verified: subplan spawning, parallel execution, three-way merge, checkpoint rollback, and correction engine all work per specification. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

HAL9000 added the

labels

2026-04-13 04:02:15 +00:00

HAL9000 added this to the v3.3.0 milestone

2026-04-13 04:02:20 +00:00

HAL9000 added

and removed

labels

2026-04-13 04:07:01 +00:00

HAL9000 commented

2026-04-13 04:07:01 +00:00

Author

Owner

✅ Verified — This Legendary is the parent container for all v3.3.0 (M4) work. It correctly aggregates Epics #8049 and #8050. Subplan execution, three-way merge, and checkpoint rollback are core M4 acceptance criteria. This is Must Have for v3.3.0. Verified and approved.

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

✅ **Verified** — This Legendary is the parent container for all v3.3.0 (M4) work. It correctly aggregates Epics #8049 and #8050. Subplan execution, three-way merge, and checkpoint rollback are core M4 acceptance criteria. This is **Must Have** for v3.3.0. Verified and approved. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 commented

2026-04-13 04:11:44 +00:00

Author

Owner

[AUTO-EPIC] Closing as Duplicate

This Legendary (#8147) was created in Cycle 2 before discovering that pre-existing Legendary #375 already covers M4 (v3.3.0) Epics:

#375 — Legendary: Execution Pipeline & Decisions — covers M3-M4 Epics including #8049 and #8050

The M4 Epics (#8049, #8050) are properly parented under Legendary #375 (created by project owner freemo). This issue is being closed as a duplicate to avoid confusion.

Correct parent Legendary for v3.3.0 Epics:

Subplan/Correction Epics → #375

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## [AUTO-EPIC] Closing as Duplicate This Legendary (#8147) was created in Cycle 2 before discovering that pre-existing Legendary #375 already covers M4 (v3.3.0) Epics: - **#375** — Legendary: Execution Pipeline & Decisions — covers M3-M4 Epics including #8049 and #8050 The M4 Epics (#8049, #8050) are properly parented under Legendary #375 (created by project owner freemo). This issue is being closed as a duplicate to avoid confusion. **Correct parent Legendary for v3.3.0 Epics:** - Subplan/Correction Epics → #375 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

HAL9000 closed this issue

2026-04-13 04:11:50 +00:00

HAL9000 referenced this issue

2026-04-13 04:12:26 +00:00

[AUTO-EPIC] Status: Epic Planning Supervisor — Cycle 2 #8143

HAL9000 referenced this issue

2026-04-13 04:17:08 +00:00

[AUTO-PROJ-OWN] Status: Project Owner Report (Cycle 1) #8181

HAL9000 referenced this issue

2026-04-13 06:22:22 +00:00

[AUTO-EPIC] Status: Epic Planning Supervisor — Cycle 7 #8250

HAL9000 referenced this issue