feat(context): implement adaptive context strategy selector and context fusion #5255

Open
opened 2026-04-09 04:15:10 +00:00 by HAL9000 · 1 comment
Owner

Background

Part of Epic #5172 (Advanced Context Strategies). Implements the adaptive strategy selector that chooses the best context strategy based on plan type, and context fusion that combines results from multiple strategies.

Expected Behavior

  • AdaptiveContextSelector chooses strategy based on plan type (coding, analysis, etc.)
  • ContextFusion combines results from multiple strategies with configurable weights
  • Strategy selection configurable in context policy YAML
  • Fusion produces a single ranked file list from multiple strategy outputs

Subtasks

  • Implement AdaptiveContextSelector with plan-type-based strategy selection
  • Implement ContextFusion with weighted combination of strategy results
  • Add strategy configuration to context policy YAML schema
  • Wire adaptive selector into ContextAssembler
  • Write Behave unit tests for adaptive selection and fusion

Definition of Done

  • Adaptive strategy selection works per plan type
  • Context fusion combines multiple strategies correctly
  • Strategy configuration works via YAML
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch: feat/v3.6.0/adaptive-context-selector
  • Commit Message: feat(context): implement adaptive context strategy selector and fusion
  • Milestone: v3.6.0
  • Parent Epic: #5172
  • Depends on: #5254 (semantic strategy must exist first)

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Background Part of Epic #5172 (Advanced Context Strategies). Implements the adaptive strategy selector that chooses the best context strategy based on plan type, and context fusion that combines results from multiple strategies. ## Expected Behavior - `AdaptiveContextSelector` chooses strategy based on plan type (coding, analysis, etc.) - `ContextFusion` combines results from multiple strategies with configurable weights - Strategy selection configurable in context policy YAML - Fusion produces a single ranked file list from multiple strategy outputs ## Subtasks - [ ] Implement `AdaptiveContextSelector` with plan-type-based strategy selection - [ ] Implement `ContextFusion` with weighted combination of strategy results - [ ] Add strategy configuration to context policy YAML schema - [ ] Wire adaptive selector into `ContextAssembler` - [ ] Write Behave unit tests for adaptive selection and fusion ## Definition of Done - [ ] Adaptive strategy selection works per plan type - [ ] Context fusion combines multiple strategies correctly - [ ] Strategy configuration works via YAML - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch**: `feat/v3.6.0/adaptive-context-selector` - **Commit Message**: `feat(context): implement adaptive context strategy selector and fusion` - **Milestone**: v3.6.0 - **Parent Epic**: #5172 - **Depends on**: #5254 (semantic strategy must exist first) --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.6.0 milestone 2026-04-09 04:15:30 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — v3.6.0 feature implementation
  • Story Points: 5 (L) — substantial implementation work
  • MoSCoW: Must Have — required for v3.6.0 milestone delivery
  • Assignee: HAL9000 — default assignment to maintain velocity

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: High — v3.6.0 feature implementation - **Story Points**: 5 (L) — substantial implementation work - **MoSCoW**: Must Have — required for v3.6.0 milestone delivery - **Assignee**: HAL9000 — default assignment to maintain velocity --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 self-assigned this 2026-04-09 04:21:58 +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#5255
No description provided.