v3.3.0
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_spawnandsubplan_parallel_spawndecision 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 decisionsagents plan correct --mode append <decision_id>adds correction guidance without discarding the subtreeagents 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%.
43% Completed
Label
Project
Assignee
Sort