UAT: A2A facade `_handle_context_get` returns stub response — ACMS ContextAssemblyPipeline not wired to A2A context operations (v3.4.0 deliverable #6) #6102

New issue

Open

opened 2026-04-09 14:40:41 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 14:40:41 +00:00

Owner

Bug Report

Feature Area: context-assembly-cli
Severity: Critical — blocks v3.4.0 deliverable #6
Spec Reference: §v3.4.0 Deliverables #6 — "Plan execution uses ACMS context; actor receives assembled fragments"
Milestone: v3.4.0

What Was Tested

Code-level analysis of src/cleveragents/a2a/facade.py _handle_context_get method.

Expected Behavior (from spec)

v3.4.0 Deliverable #6:

Context assembly pipeline produces scoped context output for actors | Plan execution uses ACMS context; actor receives assembled fragments

The A2A facade's _cleveragents/context/show operation should return assembled ACMS context fragments for a plan, not a stub response.

Actual Behavior

src/cleveragents/a2a/facade.py line 471–476:

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_get method has an explicit TODO comment and returns a stub response with "stub": True and "message": "ACMS ContextAssemblyPipeline not yet wired".

This means any A2A client calling _cleveragents/context/show will receive an empty context instead of the assembled ACMS context fragments.

Additional Context

The ACMSExecutePhaseContextAssembler IS implemented and wired to LLMExecuteActor in plan.py's _get_plan_executor() function. However, the A2A facade's context operations (_cleveragents/context/show, _cleveragents/context/inspect, _cleveragents/context/simulate, _cleveragents/context/set) all return stubs.

The stub handlers are:

_handle_context_get (line 471) — returns {"context": {}, "stub": True, ...}
_handle_context_stub (line ~640) — returns {"context": {}, "stub": True}

Code Location

src/cleveragents/a2a/facade.py lines 471–476 (_handle_context_get)
src/cleveragents/a2a/facade.py line ~640 (_handle_context_stub)

Impact

v3.4.0 deliverable #6 is not fully met via the A2A protocol path
Any A2A client requesting context assembly results receives empty stub data
The _cleveragents/context/inspect and _cleveragents/context/simulate operations are also stubs

Steps to Reproduce

Read src/cleveragents/a2a/facade.py lines 471–476
Note: _handle_context_get returns {"context": {}, "stub": True, "message": "ACMS ContextAssemblyPipeline not yet wired"}
Note: _handle_context_stub is used for inspect, simulate, and set operations

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

## Bug Report **Feature Area**: context-assembly-cli **Severity**: Critical — blocks v3.4.0 deliverable #6 **Spec Reference**: §v3.4.0 Deliverables #6 — "Plan execution uses ACMS context; actor receives assembled fragments" **Milestone**: v3.4.0 --- ## What Was Tested Code-level analysis of `src/cleveragents/a2a/facade.py` `_handle_context_get` method. ## Expected Behavior (from spec) v3.4.0 Deliverable #6: > **Context assembly pipeline produces scoped context output for actors** | Plan execution uses ACMS context; actor receives assembled fragments The A2A facade's `_cleveragents/context/show` operation should return assembled ACMS context fragments for a plan, not a stub response. ## Actual Behavior `src/cleveragents/a2a/facade.py` line 471–476: ```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_get` method has an explicit TODO comment and returns a stub response with `"stub": True` and `"message": "ACMS ContextAssemblyPipeline not yet wired"`. This means any A2A client calling `_cleveragents/context/show` will receive an empty context instead of the assembled ACMS context fragments. ## Additional Context The `ACMSExecutePhaseContextAssembler` IS implemented and wired to `LLMExecuteActor` in `plan.py`'s `_get_plan_executor()` function. However, the A2A facade's context operations (`_cleveragents/context/show`, `_cleveragents/context/inspect`, `_cleveragents/context/simulate`, `_cleveragents/context/set`) all return stubs. The stub handlers are: - `_handle_context_get` (line 471) — returns `{"context": {}, "stub": True, ...}` - `_handle_context_stub` (line ~640) — returns `{"context": {}, "stub": True}` ## Code Location - `src/cleveragents/a2a/facade.py` lines 471–476 (`_handle_context_get`) - `src/cleveragents/a2a/facade.py` line ~640 (`_handle_context_stub`) ## Impact - v3.4.0 deliverable #6 is not fully met via the A2A protocol path - Any A2A client requesting context assembly results receives empty stub data - The `_cleveragents/context/inspect` and `_cleveragents/context/simulate` operations are also stubs ## Steps to Reproduce 1. Read `src/cleveragents/a2a/facade.py` lines 471–476 2. Note: `_handle_context_get` returns `{"context": {}, "stub": True, "message": "ACMS ContextAssemblyPipeline not yet wired"}` 3. Note: `_handle_context_stub` is used for `inspect`, `simulate`, and `set` operations --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

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

HAL9000 added this to the v3.4.0 milestone

2026-04-09 14:56:24 +00:00

HAL9000 added