UAT: ContextTierService is never hydrated during plan execution #6284

New issue

Open

opened 2026-04-09 19:49:09 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 19:49:09 +00:00

Owner

Summary

ACMS spec §Context Tiering requires the hot/warm/cold tier service to be populated during plan execution so CLI commands (e.g., agents project context inspect) reflect active context fragments.
ContextTierService is registered in the DI container but nothing ever hydrates it with project resources when plans run.
The provided hydrator (context_tier_hydrator.py) is never invoked, so tier stores remain empty and all inspect/simulate commands show zero fragments.

Steps to Reproduce

Link a repository to a project and run agents plan execute <PLAN_ID>.
Run agents project context inspect <project>.
All tier counts stay zero, regardless of the files in the project.

Observed

PlanExecutor and related execution services never call ContextTierService.store() or the hydrator helpers.
context_tier_hydrator.hydrate_tiers_for_plan has no callers in the codebase.
CLI context commands simply query an empty tier service, exposing no context to the user or downstream actors.

Expected

During plan execution (or prior to context assembly), the CLI should hydrate ContextTierService with fragments for the plan’s linked resources so hot/warm/cold tiers contain data.
agents project context inspect/simulate should reflect actual fragment counts and metadata per spec.

References

src/cleveragents/application/services/context_tier_hydrator.py (unused helper).
src/cleveragents/application/services/plan_executor.py (no tier hydration before execution).
src/cleveragents/cli/commands/project_context.py (commands rely on tier service data but receive empty lists).

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Summary - ACMS spec §Context Tiering requires the hot/warm/cold tier service to be populated during plan execution so CLI commands (e.g., `agents project context inspect`) reflect active context fragments. - `ContextTierService` is registered in the DI container but nothing ever hydrates it with project resources when plans run. - The provided hydrator (`context_tier_hydrator.py`) is never invoked, so tier stores remain empty and all inspect/simulate commands show zero fragments. ## Steps to Reproduce 1. Link a repository to a project and run `agents plan execute <PLAN_ID>`. 2. Run `agents project context inspect <project>`. 3. All tier counts stay zero, regardless of the files in the project. ## Observed - `PlanExecutor` and related execution services never call `ContextTierService.store()` or the hydrator helpers. - `context_tier_hydrator.hydrate_tiers_for_plan` has no callers in the codebase. - CLI context commands simply query an empty tier service, exposing no context to the user or downstream actors. ## Expected - During plan execution (or prior to context assembly), the CLI should hydrate `ContextTierService` with fragments for the plan’s linked resources so hot/warm/cold tiers contain data. - `agents project context inspect/simulate` should reflect actual fragment counts and metadata per spec. ## References - `src/cleveragents/application/services/context_tier_hydrator.py` (unused helper). - `src/cleveragents/application/services/plan_executor.py` (no tier hydration before execution). - `src/cleveragents/cli/commands/project_context.py` (commands rely on tier service data but receive empty lists). --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

Rows
Columns