UAT: A2A _cleveragents/context/show returns stub response — ACMS ContextAssemblyPipeline not wired to A2A facade #4140

Open
opened 2026-04-06 10:40:54 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: fix/a2a-context-pipeline-wiring
  • Commit Message: fix(a2a): wire ACMS ContextAssemblyPipeline to A2A context/show handler
  • Milestone: (none — backlog)
  • Parent Epic: #539 (ACMS v1 + Context Scaling M5)

Bug Report

What Was Tested

The A2A _cleveragents/context/show operation and its connection to the ACMS ContextAssemblyPipeline.

Expected Behavior (from spec)

Per docs/specification.md §ACMS:

The Context Assembly Pipeline is the central ACMS orchestrator. It receives a ContextRequest, processes it through a chain of pluggable components, and produces a budget-respecting AssembledContext.

The _cleveragents/context/show A2A operation should invoke the ACMS ContextAssemblyPipeline to assemble and return context for the requesting actor.

Similarly, _cleveragents/context/inspect and _cleveragents/context/simulate should invoke the pipeline with appropriate parameters.

Actual Behavior

The _handle_context_get() handler in src/cleveragents/a2a/facade.py (line 471) explicitly returns a stub response:

def _handle_context_get(self, params: dict[str, Any]) -> dict[str, Any]:
    # TODO: Wire to ACMS ContextAssemblyPipeline once available.
    # For now return a stub response indicating the pipeline is pending.
    return {
        "context": {},
        "stub": True,
        "message": "ACMS ContextAssemblyPipeline not yet wired",
    }

The _handle_context_stub() handler (used for context/inspect and context/simulate) also returns a stub:

def _handle_context_stub(self, params: dict[str, Any]) -> dict[str, Any]:
    return {"context": {}, "stub": True}

The ContextAssemblyPipeline class exists in src/cleveragents/application/services/acms_pipeline.py and is fully implemented, but it is never wired into the A2A facade's service registry.

Impact

  • Actors cannot retrieve assembled context via the A2A protocol
  • The project context inspect and project context simulate CLI commands return empty/stub context
  • The ACMS hot/warm/cold tier system is not accessible via the standard A2A interface
  • Any client (CLI, TUI, IDE plugin) that calls _cleveragents/context/show receives an empty context

Code Locations

  • src/cleveragents/a2a/facade.py_handle_context_get() at line 471 (TODO comment)
  • src/cleveragents/a2a/facade.py_handle_context_stub() (used for inspect/simulate)
  • src/cleveragents/application/services/acms_pipeline.pyContextAssemblyPipeline (implemented but not wired)
  • src/cleveragents/application/container.py — DI container (missing acms_pipeline service registration)

Steps to Reproduce

  1. Make an A2A request: {"method": "_cleveragents/context/show", "params": {"project": "local/my-project"}}
  2. Observe response: {"context": {}, "stub": True, "message": "ACMS ContextAssemblyPipeline not yet wired"}

Subtasks

  • Register ContextAssemblyPipeline in the DI container
  • Wire acms_pipeline service into A2aLocalFacade via services dict
  • Implement _handle_context_get() to invoke the pipeline with a ContextRequest
  • Implement _handle_context_stub() for inspect/simulate operations
  • Add integration test verifying context assembly returns non-empty results
  • Remove TODO comment from _handle_context_get()

Definition of Done

  • _cleveragents/context/show returns assembled context from the ACMS pipeline
  • _cleveragents/context/inspect and _cleveragents/context/simulate work
  • No stub: True in context responses
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous UAT testing.
The ACMS pipeline exists but is not wired to the A2A facade. This is a
significant gap between the implemented pipeline and its actual use.

Backlog note: This issue was discovered during autonomous operation
on milestone M5. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.


Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-new-issue-creator

## Metadata - **Branch**: `fix/a2a-context-pipeline-wiring` - **Commit Message**: `fix(a2a): wire ACMS ContextAssemblyPipeline to A2A context/show handler` - **Milestone**: _(none — backlog)_ - **Parent Epic**: #539 (ACMS v1 + Context Scaling M5) ## Bug Report ### What Was Tested The A2A `_cleveragents/context/show` operation and its connection to the ACMS ContextAssemblyPipeline. ### Expected Behavior (from spec) Per `docs/specification.md` §ACMS: > The Context Assembly Pipeline is the central ACMS orchestrator. It receives a ContextRequest, processes it through a chain of pluggable components, and produces a budget-respecting AssembledContext. The `_cleveragents/context/show` A2A operation should invoke the ACMS ContextAssemblyPipeline to assemble and return context for the requesting actor. Similarly, `_cleveragents/context/inspect` and `_cleveragents/context/simulate` should invoke the pipeline with appropriate parameters. ### Actual Behavior The `_handle_context_get()` handler in `src/cleveragents/a2a/facade.py` (line 471) explicitly returns a stub response: ```python def _handle_context_get(self, params: dict[str, Any]) -> dict[str, Any]: # TODO: Wire to ACMS ContextAssemblyPipeline once available. # For now return a stub response indicating the pipeline is pending. return { "context": {}, "stub": True, "message": "ACMS ContextAssemblyPipeline not yet wired", } ``` The `_handle_context_stub()` handler (used for `context/inspect` and `context/simulate`) also returns a stub: ```python def _handle_context_stub(self, params: dict[str, Any]) -> dict[str, Any]: return {"context": {}, "stub": True} ``` The `ContextAssemblyPipeline` class exists in `src/cleveragents/application/services/acms_pipeline.py` and is fully implemented, but it is never wired into the A2A facade's service registry. ### Impact - Actors cannot retrieve assembled context via the A2A protocol - The `project context inspect` and `project context simulate` CLI commands return empty/stub context - The ACMS hot/warm/cold tier system is not accessible via the standard A2A interface - Any client (CLI, TUI, IDE plugin) that calls `_cleveragents/context/show` receives an empty context ### Code Locations - `src/cleveragents/a2a/facade.py` — `_handle_context_get()` at line 471 (TODO comment) - `src/cleveragents/a2a/facade.py` — `_handle_context_stub()` (used for inspect/simulate) - `src/cleveragents/application/services/acms_pipeline.py` — `ContextAssemblyPipeline` (implemented but not wired) - `src/cleveragents/application/container.py` — DI container (missing `acms_pipeline` service registration) ### Steps to Reproduce 1. Make an A2A request: `{"method": "_cleveragents/context/show", "params": {"project": "local/my-project"}}` 2. Observe response: `{"context": {}, "stub": True, "message": "ACMS ContextAssemblyPipeline not yet wired"}` ## Subtasks - [ ] Register `ContextAssemblyPipeline` in the DI container - [ ] Wire `acms_pipeline` service into `A2aLocalFacade` via `services` dict - [ ] Implement `_handle_context_get()` to invoke the pipeline with a `ContextRequest` - [ ] Implement `_handle_context_stub()` for inspect/simulate operations - [ ] Add integration test verifying context assembly returns non-empty results - [ ] Remove TODO comment from `_handle_context_get()` ## Definition of Done - [ ] `_cleveragents/context/show` returns assembled context from the ACMS pipeline - [ ] `_cleveragents/context/inspect` and `_cleveragents/context/simulate` work - [ ] No `stub: True` in context responses - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous UAT testing. > The ACMS pipeline exists but is not wired to the A2A facade. This is a > significant gap between the implemented pipeline and its actual use. > > **Backlog note:** This issue was discovered during autonomous operation > on milestone M5. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-new-issue-creator
freemo added this to the v3.4.0 milestone 2026-04-06 17:49:00 +00:00
freemo removed this from the v3.4.0 milestone 2026-04-06 20:42:39 +00:00
HAL9000 added this to the v3.5.0 milestone 2026-04-09 03:10: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#4140
No description provided.