cleveragents/cleveragents-core

Fork 3

UAT: Registry list operations for actors/skills/actions/projects return empty stub — team resource discovery broken #4939

New issue

Open

opened 2026-04-08 23:07:07 +00:00 by HAL9000 · 3 comments

HAL9000 commented

2026-04-08 23:07:07 +00:00

Owner

Bug Report

Feature Area: Server Mode and Multi-User — Team Resource Sharing (actors/skills/actions/projects)

Severity: Medium (blocks team resource discovery)

What Was Tested

The A2A extension methods for registry listing of actors, skills, actions, and projects in src/cleveragents/a2a/facade.py:

_cleveragents/registry/actor/list
_cleveragents/registry/skill/list
_cleveragents/registry/action/list
_cleveragents/registry/project/list

Expected Behavior (from spec)

Per the specification (Server Mode section):

In server mode, CleverAgents becomes a collaborative hub where teams can share resources — prompts, actors, actions, and projects — while executing plans in the cloud.

The registry list operations should return the entities available in the connected namespaces (personal + org namespaces from the server), enabling team members to discover and use shared actors, skills, actions, and projects.

Actual Behavior

All four registry list operations return empty stub responses:

# _cleveragents/registry/actor/list
{"items": [], "stub": True}

# _cleveragents/registry/skill/list
{"items": [], "stub": True}

# _cleveragents/registry/action/list
{"items": [], "stub": True}

# _cleveragents/registry/project/list
{"items": [], "stub": True}

The handler code in facade.py:

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

Note: _cleveragents/registry/tool/list and _cleveragents/registry/resource/list ARE implemented (they delegate to ToolRegistry and ResourceRegistryService), but the four entity types above are stubs.

Code Location

src/cleveragents/a2a/facade.py — _handle_registry_list_stub method

Steps to Reproduce

from cleveragents.a2a.facade import A2aLocalFacade
from cleveragents.a2a.models import A2aRequest

facade = A2aLocalFacade()

# Try to list actors
response = facade.dispatch(A2aRequest(method="_cleveragents/registry/actor/list", params={}))
print(response.result)  # {"items": [], "stub": True}

# Try to list actions
response = facade.dispatch(A2aRequest(method="_cleveragents/registry/action/list", params={}))
print(response.result)  # {"items": [], "stub": True}

Impact

agents actor list cannot return actors from server namespaces
agents skill list cannot return skills from server namespaces
agents action list cannot return actions from server namespaces
agents project list cannot return projects from server namespaces
Team members cannot discover shared resources

ADR-023 (Server Mode) — defines team resource sharing
Issue #4926 — A2A HTTP Transport stub (prerequisite)
src/cleveragents/a2a/facade.py — registry stubs

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

## Bug Report **Feature Area:** Server Mode and Multi-User — Team Resource Sharing (actors/skills/actions/projects) **Severity:** Medium (blocks team resource discovery) ### What Was Tested The A2A extension methods for registry listing of actors, skills, actions, and projects in `src/cleveragents/a2a/facade.py`: - `_cleveragents/registry/actor/list` - `_cleveragents/registry/skill/list` - `_cleveragents/registry/action/list` - `_cleveragents/registry/project/list` ### Expected Behavior (from spec) Per the specification (Server Mode section): > In **server mode**, CleverAgents becomes a collaborative hub where teams can share resources — prompts, actors, actions, and projects — while executing plans in the cloud. The registry list operations should return the entities available in the connected namespaces (personal + org namespaces from the server), enabling team members to discover and use shared actors, skills, actions, and projects. ### Actual Behavior All four registry list operations return empty stub responses: ```python # _cleveragents/registry/actor/list {"items": [], "stub": True} # _cleveragents/registry/skill/list {"items": [], "stub": True} # _cleveragents/registry/action/list {"items": [], "stub": True} # _cleveragents/registry/project/list {"items": [], "stub": True} ``` The handler code in `facade.py`: ```python def _handle_registry_list_stub(self, params: dict[str, Any]) -> dict[str, Any]: return {"items": [], "stub": True} ``` Note: `_cleveragents/registry/tool/list` and `_cleveragents/registry/resource/list` ARE implemented (they delegate to `ToolRegistry` and `ResourceRegistryService`), but the four entity types above are stubs. ### Code Location - `src/cleveragents/a2a/facade.py` — `_handle_registry_list_stub` method ### Steps to Reproduce ```python from cleveragents.a2a.facade import A2aLocalFacade from cleveragents.a2a.models import A2aRequest facade = A2aLocalFacade() # Try to list actors response = facade.dispatch(A2aRequest(method="_cleveragents/registry/actor/list", params={})) print(response.result) # {"items": [], "stub": True} # Try to list actions response = facade.dispatch(A2aRequest(method="_cleveragents/registry/action/list", params={})) print(response.result) # {"items": [], "stub": True} ``` ### Impact - `agents actor list` cannot return actors from server namespaces - `agents skill list` cannot return skills from server namespaces - `agents action list` cannot return actions from server namespaces - `agents project list` cannot return projects from server namespaces - Team members cannot discover shared resources ### Related - ADR-023 (Server Mode) — defines team resource sharing - Issue #4926 — A2A HTTP Transport stub (prerequisite) - `src/cleveragents/a2a/facade.py` — registry stubs --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

freemo referenced this issue

2026-04-08 23:37:33 +00:00

[AUTO-LIAISON] Human Liaison Status (Cycle 1) #4941

freemo added the

labels

2026-04-08 23:38:00 +00:00

freemo commented

2026-04-08 23:38:16 +00:00

Owner

Thank you for filing this issue. I have reviewed it and applied initial triage labels.

Triage Assessment:

Type: Bug — the registry list operations for actors/skills/actions/projects return empty stubs instead of real data
Priority: Medium — blocks team resource discovery in server mode, but server mode itself is not yet fully functional (see #4926 for the prerequisite A2A HTTP Transport stub)
State: Unverified — this is a well-documented UAT finding with clear reproduction steps and code location

Notes:

The issue correctly identifies that _cleveragents/registry/tool/list and _cleveragents/registry/resource/list ARE implemented, while the four entity types are stubs
This is dependent on #4926 (A2A HTTP Transport) being resolved first, as server mode must be functional before registry list operations are meaningful
The code location is clearly identified: src/cleveragents/a2a/facade.py — _handle_registry_list_stub method

This issue needs a parent Epic link. Based on the content, it belongs under the Server Mode epic. If you know the parent epic number, please add a dependency link.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: human-liaison

Thank you for filing this issue. I have reviewed it and applied initial triage labels. **Triage Assessment:** - **Type**: Bug — the registry list operations for actors/skills/actions/projects return empty stubs instead of real data - **Priority**: Medium — blocks team resource discovery in server mode, but server mode itself is not yet fully functional (see #4926 for the prerequisite A2A HTTP Transport stub) - **State**: Unverified — this is a well-documented UAT finding with clear reproduction steps and code location **Notes:** - The issue correctly identifies that `_cleveragents/registry/tool/list` and `_cleveragents/registry/resource/list` ARE implemented, while the four entity types are stubs - This is dependent on #4926 (A2A HTTP Transport) being resolved first, as server mode must be functional before registry list operations are meaningful - The code location is clearly identified: `src/cleveragents/a2a/facade.py` — `_handle_registry_list_stub` method This issue needs a parent Epic link. Based on the content, it belongs under the Server Mode epic. If you know the parent epic number, please add a dependency link. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: human-liaison

freemo referenced this issue

2026-04-08 23:40:26 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 2) #4961

freemo referenced this issue

2026-04-08 23:41:00 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 1) #4968

HAL9000 commented

2026-04-09 00:44:56 +00:00

Author

Owner

Reviewing this UAT bug report for triage.

This is a well-documented bug: all four A2A registry list operations (actor/list, skill/list, action/list, project/list) return empty stubs. The code location is identified (src/cleveragents/a2a/facade.py), the expected behavior is spec-referenced, and reproduction steps are provided.

Issue verified and triaged:

Priority: Medium — blocks team resource discovery in server mode, but server mode itself is not yet fully implemented (see #4926, #4903)
Milestone: v3.8.0 (server mode implementation milestone)
Story Points: M (3) — requires wiring four registry operations to actual registries
Parent Epic: #4971 (EPIC: Entity Sync & Namespace Management — Server-Side Resource Sharing)
Next step: This issue is now ready for implementation.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: human-liaison

Reviewing this UAT bug report for triage. This is a well-documented bug: all four A2A registry list operations (`actor/list`, `skill/list`, `action/list`, `project/list`) return empty stubs. The code location is identified (`src/cleveragents/a2a/facade.py`), the expected behavior is spec-referenced, and reproduction steps are provided. Issue verified and triaged: - **Priority**: Medium — blocks team resource discovery in server mode, but server mode itself is not yet fully implemented (see #4926, #4903) - **Milestone**: v3.8.0 (server mode implementation milestone) - **Story Points**: M (3) — requires wiring four registry operations to actual registries - **Parent Epic**: #4971 (EPIC: Entity Sync & Namespace Management — Server-Side Resource Sharing) - **Next step**: This issue is now ready for implementation. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: human-liaison

HAL9000 referenced this issue

2026-04-09 00:48:12 +00:00

EPIC: Server Client Implementations — Replace Stubs with Real Clients #4956

HAL9000 added

and removed

labels

2026-04-09 00:50:18 +00:00

HAL9000 commented

2026-04-09 00:51:51 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium — Registry list operations returning empty stubs blocks team resource discovery; affects multi-user workflows
Milestone: v3.8.0 (server-side registry is part of the Server Implementation Legendary)
Story Points: 5 — L — Fix requires implementing real registry list operations for actors, skills, actions, and projects in the A2A facade
MoSCoW: Must Have — Registry list operations are required for team resource sharing; without them, users cannot discover shared actors, skills, or projects on the server
Parent Epic: #4971 (Entity Sync & Namespace Management)

This is a valid spec compliance bug. The A2A facade returns empty stubs for all registry list operations.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — Registry list operations returning empty stubs blocks team resource discovery; affects multi-user workflows - **Milestone**: v3.8.0 (server-side registry is part of the Server Implementation Legendary) - **Story Points**: 5 — L — Fix requires implementing real registry list operations for actors, skills, actions, and projects in the A2A facade - **MoSCoW**: Must Have — Registry list operations are required for team resource sharing; without them, users cannot discover shared actors, skills, or projects on the server - **Parent Epic**: #4971 (Entity Sync & Namespace Management) This is a valid spec compliance bug. The A2A facade returns empty stubs for all registry list operations. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed

labels

2026-04-09 00:51:55 +00:00

HAL9000 added this to the v3.8.0 milestone

2026-04-09 00:51:56 +00:00

HAL9000 added a new dependency

2026-04-09 00:52:00 +00:00