v3.3.0

New issue

v3.3.0 — M4: Corrections + Subplans + Checkpoints

Goal: Plans can spawn child plans (subplans) during execution. Subplans execute in parallel with configurable concurrency limits. Results are merged back using three-way merge strategies. Correction engine supports revert and append modes. Checkpointing enables rollback to previous plan states.

Acceptance Criteria

• Execution actor can spawn subplans via subplan_spawn and subplan_parallel_spawn decision types
• Subplans execute in sequential, parallel, or dependency-ordered modes with configurable concurrency limits
• Subplan results merge back into parent plan using git three-way merge, sequential apply, or last-wins strategies
• agents plan correct --mode revert <decision_id> reverts a decision and all affected downstream decisions
• agents plan correct --mode append <decision_id> adds correction guidance without discarding the subtree
• agents plan rollback <plan_id> <checkpoint_id> restores a plan to a prior checkpoint state
• Checkpoints are created automatically at configurable intervals during plan execution
• Phase reversion: a constrained apply transitions back to Strategize for re-planning
• agents plan errors <plan_id> shows error recovery hints and retry options
• Test coverage >= 97%

Technical Criteria

• Subplan orchestration with domain models for config, status, failure handling, and three merge strategies.
• Correction model with revert/append modes, BFS impact analysis, and dry-run reporting.
• Checkpoint scopes with pruning and cleanup hooks integrated throughout the execution pipeline.
• Phase reversion state machine: constrained apply → Strategize transition.
• Concurrency locks (plan and project advisory locks) with plan resume and state recovery.
• Test coverage remains >= 97%.

2026-03-02

39% Completed

208 Open 136 Closed 344 All

Label

Show archived labels

All labels No label

auto/needs-reevaluation

controller-managed

auto/blocked-by-deps

auto/ci-timeout

auto/claimed-implementer

auto/claimed-merge

auto/claimed-reviewer

auto/driver-down

auto/invariant-violation

auto/last-attempt-tier-0

auto/last-attempt-tier-1

auto/last-attempt-tier-2

auto/last-attempt-tier-min

Automation Tracking

auto/needs-conflict-resolution

auto/needs-implementer

auto/postmortem

auto/ready-to-merge

auto/restart-throttled

auto/revert

auto/sentinel

auto/stale-inactivity

auto/unstable

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Project

All projects No project

Closed projects

Sprint Oct 15th-28th Sprint Nov 1st- 14th Sprint Nov 15-28th Sprint Dec 15- 28th Sprint Jan 1st- 14th Sprint Jan 15-28th

Author

All authors

Assignee

All assignees No assignee

aditya aleenaumair brent.edwards CoreRasurae drew eugen.thaci freemo HAL9000 HAL9001 hamza.khyari hurui200320 justin.morris khird

Sort

Relevance Newest Oldest Recently updated Least recently updated Most commented Least commented Nearest due date Farthest due date

feat(plans): implement ThreeWayMergeEngine for subplan result integration

MoSCoW

Must have

Priority

High

State

In Review

Type

Feature

10

#11101 opened 2026-05-09 14:59:02 +00:00 by HAL9000

master

1 change request 1 conflicting file

feat(plans): implement conflict detection and structured conflict report for three-way merge

MoSCoW

Must have

Priority

High

State

In Review

Type

Feature

41

#11000 opened 2026-05-07 14:28:20 +00:00 by HAL9000

master

7 / 8 1 change request 2 conflicting files

docs(spec): align checkpoint trigger names and config key path with implementation

16

#10826 opened 2026-04-22 10:37:25 +00:00 by HAL9000

master

4 / 4 1 change request 1 conflicting file

test(robot): create shared plan service helper library

1

#9621 opened 2026-04-15 00:47:50 +00:00 by HAL9000

test(plan-service): centralize Behave plan service fixtures

1

#9619 opened 2026-04-15 00:47:11 +00:00 by HAL9000

feat(plans): implement conflict detection and structured conflict report for three-way merge - Closes #9558

10

#9613 opened 2026-04-15 00:42:07 +00:00 by HAL9000

master

1 change request 2 conflicting files

feat(cli): implement plan rollback CLI command for checkpoint-based plan state restoration

Priority

Medium

State

In Review

Type

Feature

11

#9612 opened 2026-04-15 00:40:47 +00:00 by HAL9000

master

1 change request

feat(plans): implement configurable merge strategy (prefer-parent, prefer-subplan, manual) - Closes #9559

19

#9610 opened 2026-04-15 00:40:17 +00:00 by HAL9000

master

1 change request 1 conflicting file

feat(plans): implement parallel subplan execution scheduler with max_parallel concurrency control

10

#9609 opened 2026-04-15 00:38:03 +00:00 by HAL9000

master

1 change request

feat(plans): implement ThreeWayMergeEngine for subplan result integration

MoSCoW

Must have

Priority

High

State

In Review

Type

Feature

49

#9608 opened 2026-04-15 00:38:01 +00:00 by HAL9000

master

1 change request 1 conflicting file

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

MoSCoW

Must have

Priority

High

State

In Review

Type

Feature

34

#9599 opened 2026-04-15 00:19:11 +00:00 by HAL9000

master

1 change request

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

2

#9562 opened 2026-04-14 22:51:17 +00:00 by HAL9000 0 / 10

feat(cli): implement plan rollback CLI command for checkpoint-based plan state restoration

1

#9561 opened 2026-04-14 22:51:11 +00:00 by HAL9000 0 / 10

feat(plans): implement checkpoint creation and durable persistence for plan execution

MoSCoW

Must have

Priority

High

State

Verified

Type

Feature

2

#9560 opened 2026-04-14 22:51:05 +00:00 by HAL9000 0 / 11

feat(plans): implement configurable merge strategy (prefer-parent, prefer-subplan, manual)

2

#9559 opened 2026-04-14 22:50:59 +00:00 by HAL9000 0 / 11

feat(plans): implement conflict detection and structured conflict report for three-way merge

MoSCoW

Must have

Priority

High

State

Verified

Type

Feature

4

#9558 opened 2026-04-14 22:50:53 +00:00 by HAL9000 0 / 11

feat(plans): implement ThreeWayMergeEngine for subplan result integration

MoSCoW

Must have

Priority

High

State

In Review

Type

Feature

2

#9557 opened 2026-04-14 22:50:47 +00:00 by HAL9000 0 / 12

feat(plans): implement parent plan subplan status registry and real-time tracking

MoSCoW

Must have

Priority

High

State

Verified

Type

Feature

2

#9556 opened 2026-04-14 22:50:41 +00:00 by HAL9000 0 / 11

feat(plans): implement parallel subplan execution scheduler with max_parallel concurrency control

MoSCoW

Must have

Priority

High

State

Verified

Type

Feature

3

#9555 opened 2026-04-14 22:50:35 +00:00 by HAL9000 0 / 12

feat(plans): implement SpawnSubplanStep type for hierarchical plan composition

MoSCoW

Must have

Priority

High

State

Verified

Type

Feature

3

#9554 opened 2026-04-14 22:50:28 +00:00 by HAL9000 0 / 12