feat(plan): wire execute phase to actor runtime and changeset capture #153

Closed
opened 2026-02-22 23:39:39 +00:00 by freemo · 0 comments
Owner

Metadata

  • Commit: feat(plan): wire execute phase to actor runtime and changeset capture
  • Branch: feature/m1-plan-execute-runtime

Subtasks

  • Integrate PlanExecutor with strategy/execution actors using the new actor runtime and action-configured roles.
  • Introduce a PlanExecutionContext that carries project resources, sandbox root, and automation profile for tool execution.
  • Persist decision root IDs and ChangeSet IDs onto the plan, wiring ChangeSetStore for diff/artifacts.
  • Update docs/reference/plan_execute.md with tool-aware execute flow and metadata storage.
  • Tests (Behave): Add scenarios for plan execute lifecycle transitions and ChangeSet creation.
  • Tests (Robot): Add Robot CLI test for agents plan execute with tool calls against a temp repo.
  • Tests (ASV): Add benchmarks/plan_execute_bench.py for execute runtime baseline.
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M1: Minimal Local Source-Code Workflow (Target: Day 7, recovery path)
Status: Completed

## Metadata - **Commit**: `feat(plan): wire execute phase to actor runtime and changeset capture` - **Branch**: `feature/m1-plan-execute-runtime` ## Subtasks - [x] Integrate PlanExecutor with strategy/execution actors using the new actor runtime and action-configured roles. - [x] Introduce a `PlanExecutionContext` that carries project resources, sandbox root, and automation profile for tool execution. - [x] Persist decision root IDs and ChangeSet IDs onto the plan, wiring ChangeSetStore for diff/artifacts. - [x] Update `docs/reference/plan_execute.md` with tool-aware execute flow and metadata storage. - [x] Tests (Behave): Add scenarios for plan execute lifecycle transitions and ChangeSet creation. - [x] Tests (Robot): Add Robot CLI test for `agents plan execute` with tool calls against a temp repo. - [x] Tests (ASV): Add `benchmarks/plan_execute_bench.py` for execute runtime baseline. - [x] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [x] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M1: Minimal Local Source-Code Workflow (Target: Day 7, recovery path) **Status**: Completed
freemo added this to the v3.0.0 milestone 2026-02-22 23:39:39 +00:00
freemo self-assigned this 2026-02-22 23:39:39 +00:00
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.

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