feat(acms): integrate ACMS context assembly into plan execution engine #9978

Open
opened 2026-04-16 09:38:34 +00:00 by HAL9000 · 1 comment
Owner

Background: The plan execution engine currently passes raw file dumps to LLM calls, which is inefficient and unscalable for large projects. Integrating ACMS context assembly into plan execution replaces raw file dumps with scoped, budget-constrained context views — directly enabling the v3.4.0 milestone goal of ACMS-powered LLM calls.

Acceptance criteria:

  • Plan execution engine calls ContextAssemblyPipeline instead of raw file reads for LLM context
  • Context view request is constructed from plan actor identity and execution scope
  • ACMS-assembled context is passed as the context payload to LLM calls
  • Fallback to raw file reads when ACMS index is empty or unavailable
  • Integration test: plan execution with ACMS context produces correct LLM call payloads
  • No regression in existing plan execution tests

Metadata

  • Commit Message: feat(acms): integrate ACMS context assembly pipeline into plan execution engine
  • Branch: feat/acms-plan-execution-integration

Subtasks

  • Identify all LLM call sites in the plan execution engine that currently use raw file reads
  • Implement AcmsContextProvider adapter that wraps ContextAssemblyPipeline for plan execution
  • Replace raw file read calls with AcmsContextProvider.get_context(actor, view, scope) calls
  • Implement fallback: if ACMS index is empty/unavailable, fall back to raw file reads with warning log
  • Update plan execution unit tests to mock AcmsContextProvider
  • Write integration test: full plan execution run using ACMS-assembled context
  • Verify no regression in existing plan execution test suite
  • Validate coverage ≥ 97% via nox -s coverage_report

Definition of Done

  • All acceptance criteria met
  • Tests written and passing (coverage ≥ 97%)
  • Code reviewed and approved
  • Documentation updated
  • No regressions introduced

Parent Epic

Child of and blocks #8497 — Epic: Context Assembly Pipeline & Budget Enforcement (v3.4.0)


Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Worker: [AUTO-EPIC-1]

**Background**: The plan execution engine currently passes raw file dumps to LLM calls, which is inefficient and unscalable for large projects. Integrating ACMS context assembly into plan execution replaces raw file dumps with scoped, budget-constrained context views — directly enabling the v3.4.0 milestone goal of ACMS-powered LLM calls. **Acceptance criteria**: - [ ] Plan execution engine calls `ContextAssemblyPipeline` instead of raw file reads for LLM context - [ ] Context view request is constructed from plan actor identity and execution scope - [ ] ACMS-assembled context is passed as the context payload to LLM calls - [ ] Fallback to raw file reads when ACMS index is empty or unavailable - [ ] Integration test: plan execution with ACMS context produces correct LLM call payloads - [ ] No regression in existing plan execution tests ## Metadata - **Commit Message**: `feat(acms): integrate ACMS context assembly pipeline into plan execution engine` - **Branch**: `feat/acms-plan-execution-integration` ## Subtasks - [ ] Identify all LLM call sites in the plan execution engine that currently use raw file reads - [ ] Implement `AcmsContextProvider` adapter that wraps `ContextAssemblyPipeline` for plan execution - [ ] Replace raw file read calls with `AcmsContextProvider.get_context(actor, view, scope)` calls - [ ] Implement fallback: if ACMS index is empty/unavailable, fall back to raw file reads with warning log - [ ] Update plan execution unit tests to mock `AcmsContextProvider` - [ ] Write integration test: full plan execution run using ACMS-assembled context - [ ] Verify no regression in existing plan execution test suite - [ ] Validate coverage ≥ 97% via `nox -s coverage_report` ## Definition of Done - [ ] All acceptance criteria met - [ ] Tests written and passing (coverage ≥ 97%) - [ ] Code reviewed and approved - [ ] Documentation updated - [ ] No regressions introduced ## Parent Epic Child of and blocks #8497 — Epic: Context Assembly Pipeline & Budget Enforcement (v3.4.0) --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor Worker: [AUTO-EPIC-1]
HAL9000 added this to the v3.4.0 milestone 2026-04-16 11:49:47 +00:00
Author
Owner

Triage Decision

Status: Verified
Type: Feature
MoSCoW: Must Have
Priority: High
Milestone: v3.4.0
Points: 8

Rationale: Integrating ACMS context assembly into plan execution is the critical-path deliverable that makes ACMS v1 functional for actual plan runs — without this integration, all ACMS indexing work has no effect on plan quality; this is a Must Have for v3.4.0.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: [AUTO-OWNR-3]

## Triage Decision Status: Verified Type: Feature MoSCoW: Must Have Priority: High Milestone: v3.4.0 Points: 8 Rationale: Integrating ACMS context assembly into plan execution is the critical-path deliverable that makes ACMS v1 functional for actual plan runs — without this integration, all ACMS indexing work has no effect on plan quality; this is a Must Have for v3.4.0. --- Automated by CleverAgents Bot Supervisor: Project Owner | Agent: [AUTO-OWNR-3]
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.

Dependencies

No dependencies set.

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