feat(subplan): execute and merge subplans #444

Merged

CoreRasurae merged 1 commit from feature/m4-subplan-execution into master 2026-03-01 09:57:17 +00:00

Conversation 2 Commits 1 Files changed 9 +3193

CoreRasurae commented 2026-02-25 22:23:29 +00:00

Member

Copy link

Summary

Implements subplan execution scheduling and merge strategy infrastructure for the plan lifecycle system.

Changes

• SubplanExecutionService: Scheduler supporting sequential, parallel, and dependency-ordered execution modes with configurable concurrency limits and fail-fast behavior
• SubplanMergeService: Four merge strategies (git three-way, sequential apply, fail on conflict, last wins) for combining sandbox outputs from completed subplans
• BDD Tests: 21 Behave scenarios covering all execution modes, merge strategies, failure handling, and retry logic
• Robot Tests: 11 integration test cases for subplan execution and merge summaries
• ASV Benchmarks: Performance benchmarks for scheduler overhead
• Documentation: Reference documentation at docs/reference/subplans.md

Motivation

Subplan execution is a core capability for breaking down complex plans into manageable units of work. The scheduling infrastructure enables sequential, parallel, and dependency-aware execution while the merge system combines results safely using configurable strategies.

Key Design Decisions

• Split into two services (SubplanExecutionService + SubplanMergeService) following SRP
• Parallel execution uses asyncio.gather with semaphore-based concurrency limiting
• Dependency-ordered mode performs topological sort and executes independent subplans concurrently
• All services use dependency injection for testability

Closes #184

## Summary Implements subplan execution scheduling and merge strategy infrastructure for the plan lifecycle system. ### Changes - **SubplanExecutionService**: Scheduler supporting sequential, parallel, and dependency-ordered execution modes with configurable concurrency limits and fail-fast behavior - **SubplanMergeService**: Four merge strategies (git three-way, sequential apply, fail on conflict, last wins) for combining sandbox outputs from completed subplans - **BDD Tests**: 21 Behave scenarios covering all execution modes, merge strategies, failure handling, and retry logic - **Robot Tests**: 11 integration test cases for subplan execution and merge summaries - **ASV Benchmarks**: Performance benchmarks for scheduler overhead - **Documentation**: Reference documentation at `docs/reference/subplans.md` ### Motivation Subplan execution is a core capability for breaking down complex plans into manageable units of work. The scheduling infrastructure enables sequential, parallel, and dependency-aware execution while the merge system combines results safely using configurable strategies. ### Key Design Decisions - Split into two services (SubplanExecutionService + SubplanMergeService) following SRP - Parallel execution uses asyncio.gather with semaphore-based concurrency limiting - Dependency-ordered mode performs topological sort and executes independent subplans concurrently - All services use dependency injection for testability Closes #184

CoreRasurae added this to the v3.3.0 milestone 2026-02-25 22:23:53 +00:00

CoreRasurae added the

Type

Feature

label 2026-02-25 22:23:54 +00:00

CoreRasurae referenced this pull request 2026-02-25 22:24:17 +00:00

feat(subplan): execute and merge subplans #184

CoreRasurae force-pushed feature/m4-subplan-execution from cad1678bc5 to 4805e399af 2026-02-27 15:27:31 +00:00 Compare

brent.edwards reviewed 2026-02-27 21:45:48 +00:00

brent.edwards left a comment

Copy link

Review Summary (commit 4805e399af97b46f3350a05b)

Scoped to the subplan execution/merge commit. The core service design is clean and the docs/tests are thorough, but there are a few behavioral gaps that will surprise callers.

CI status isn’t visible via the API on my side. Please confirm required checks per docs/development/ci-cd.md are green (lint, typecheck, security, quality, unit_tests, integration_tests, coverage, build, docker).

Findings

P1:must-fix — timeout_per_subplan_seconds is defined in SubplanConfig and documented, but never enforced in SubplanExecutionService. There’s no per‑subplan timeout in sequential or parallel modes. Implement timeouts (e.g., future.result(timeout=...) / watchdog) or remove the field/docs.

• Code: src/cleveragents/application/services/subplan_execution_service.py
• Model: src/cleveragents/domain/models/core/plan.py
• Docs: docs/reference/subplans.md

P2:should-fix — sequential_apply is documented as “completion order,” but in parallel mode the outputs are merged in original subplan order because results are re-ordered by the input list. If completion order is intended, capture completion timestamps and sort outputs before merge.

• Code: src/cleveragents/application/services/subplan_execution_service.py (_execute_parallel, execute_all)
• Merge: src/cleveragents/application/services/subplan_merge_service.py
• Docs: docs/reference/subplans.md

P2:should-fix — In parallel fail_fast, cancelled futures surface as CancelledError and are marked ERRORED rather than CANCELLED. This makes status reporting inconsistent with sequential mode and with the “stop others” semantics.

• Code: src/cleveragents/application/services/subplan_execution_service.py

P3:should-fix — The commit message claims dependency‑ordered mode executes independent subplans concurrently, but the implementation runs them sequentially after topological sort. Either update the description/docs or implement concurrent execution for ready nodes.

• Code: src/cleveragents/application/services/subplan_execution_service.py

Positive Notes

• Service API and merge strategy abstraction are clean and easy to test.
• Failure handling and retry logic are thoughtfully separated.
• Documentation covers execution modes and merge outcomes well.

## Review Summary (commit 4805e399af97b46f3350a05b) Scoped to the subplan execution/merge commit. The core service design is clean and the docs/tests are thorough, but there are a few behavioral gaps that will surprise callers. CI status isn’t visible via the API on my side. Please confirm required checks per `docs/development/ci-cd.md` are green (lint, typecheck, security, quality, unit_tests, integration_tests, coverage, build, docker). ## Findings **P1:must-fix** — `timeout_per_subplan_seconds` is defined in `SubplanConfig` and documented, but never enforced in `SubplanExecutionService`. There’s no per‑subplan timeout in sequential or parallel modes. Implement timeouts (e.g., `future.result(timeout=...)` / watchdog) or remove the field/docs. - Code: `src/cleveragents/application/services/subplan_execution_service.py` - Model: `src/cleveragents/domain/models/core/plan.py` - Docs: `docs/reference/subplans.md` **P2:should-fix** — `sequential_apply` is documented as “completion order,” but in parallel mode the outputs are merged in **original subplan order** because results are re-ordered by the input list. If completion order is intended, capture completion timestamps and sort outputs before merge. - Code: `src/cleveragents/application/services/subplan_execution_service.py` (`_execute_parallel`, `execute_all`) - Merge: `src/cleveragents/application/services/subplan_merge_service.py` - Docs: `docs/reference/subplans.md` **P2:should-fix** — In parallel `fail_fast`, cancelled futures surface as `CancelledError` and are marked `ERRORED` rather than `CANCELLED`. This makes status reporting inconsistent with sequential mode and with the “stop others” semantics. - Code: `src/cleveragents/application/services/subplan_execution_service.py` **P3:should-fix** — The commit message claims dependency‑ordered mode executes independent subplans concurrently, but the implementation runs them sequentially after topological sort. Either update the description/docs or implement concurrent execution for ready nodes. - Code: `src/cleveragents/application/services/subplan_execution_service.py` ## Positive Notes - Service API and merge strategy abstraction are clean and easy to test. - Failure handling and retry logic are thoughtfully separated. - Documentation covers execution modes and merge outcomes well.

CoreRasurae force-pushed feature/m4-subplan-execution from 4805e399af to 1bbec743ba 2026-02-27 23:14:50 +00:00 Compare

brent.edwards approved these changes 2026-02-27 23:27:28 +00:00

Dismissed

brent.edwards left a comment

Copy link

I (not an LLM) checked that the review comments were met. Great work!

I (not an LLM) checked that the review comments were met. Great work!

freemo added the

Points

5

Priority

Medium

State

Verified

labels 2026-03-01 04:36:13 +00:00

CoreRasurae force-pushed feature/m4-subplan-execution from 1bbec743ba to 9f6fb667c2 2026-03-01 09:07:35 +00:00 Compare

CoreRasurae dismissed brent.edwards's review 2026-03-01 09:07:35 +00:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

CoreRasurae scheduled this pull request to auto merge when all checks succeed 2026-03-01 09:07:55 +00:00

CoreRasurae merged commit 9f6fb667c2 into master 2026-03-01 09:57:17 +00:00

CoreRasurae deleted branch feature/m4-subplan-execution 2026-03-01 09:57:17 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

auto/needs-reevaluation

Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  

controller-managed

Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  

auto/blocked-by-deps

PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  

auto/ci-timeout

Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  

auto/claimed-implementer

Currently being processed by an implementer worker.

  

auto/claimed-merge

Currently being processed by the merge driver.

  

auto/claimed-reviewer

Currently being processed by a reviewer worker.

  

auto/driver-down

Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  

auto/invariant-violation

Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  

auto/last-attempt-tier-0

In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-1

In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-2

In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  

auto/last-attempt-tier-min

In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  

Automation Tracking

Tracking issues used by the AI Automation system for agents to communicate and report.

  

auto/needs-conflict-resolution

Rebase conflict needs LLM conflict-resolver.

  

auto/needs-implementer

Failing CI needs implementer attention.

  

auto/postmortem

Documenting a driver incident or rollback.

  

auto/ready-to-merge

Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  

auto/restart-throttled

Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  

auto/revert

Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  

auto/sentinel

Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  

auto/stale-inactivity

No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  

auto/unstable

Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs Feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

CI Blocker

Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Automation

Any edits or discussion about the AI automated coding system.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Refactor

A code change that restructures existing code without changing its external behavior.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

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

Milestone

Clear milestone

No items

No milestone

v3.3.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

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!444

No description provided.