cleveragents/cleveragents-core

Fork 3

UAT: Entity sync operations (_cleveragents/sync/*) return "not_implemented" — team resource sharing broken #4933

New issue

Open

opened 2026-04-08 23:00:44 +00:00 by HAL9000 · 1 comment

HAL9000 commented

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

Owner

Bug Report

Feature Area: Server Mode and Multi-User — Entity Sync / Team Resource Sharing

Severity: Medium (blocks team collaboration features)

What Was Tested

The A2A extension methods for entity synchronization (_cleveragents/sync/pull, _cleveragents/sync/push, _cleveragents/sync/status) in src/cleveragents/a2a/facade.py.

Expected Behavior (from spec)

Per the specification (ADR-023, Server Mode) and the spec's Server Mode section:

Entity synchronization between client and server uses A2A extension methods (_cleveragents/sync/*):

Auto-sync (server.sync.auto): Entities sync on connection and at server.sync.interval (default: 300s)

Sync interval: Background syncs at server.sync.interval (default: 300 seconds)

Manual sync: Can be triggered explicitly when auto-sync is disabled

Direction: Server namespaces are downloaded to local cache; local namespace entities are never uploaded automatically

The spec also states that in server mode, a user can:

Share actions, actors, skills, and projects with team members

Access team-shared resources from any device

Actual Behavior

All three sync operations return stub responses:

# _cleveragents/sync/pull
{"status": "not_implemented", "stub": True}

# _cleveragents/sync/push
{"status": "not_implemented", "stub": True}

# _cleveragents/sync/status
{"status": "not_implemented", "stub": True}

The handler code in facade.py:

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

Code Location

src/cleveragents/a2a/facade.py — _handle_sync_stub method (lines ~490-491)
src/cleveragents/application/services/config_service.py — server.sync.auto and server.sync.interval config keys are registered but never used

Steps to Reproduce

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

facade = A2aLocalFacade()

# Try to sync
response = facade.dispatch(A2aRequest(method="_cleveragents/sync/pull", params={}))
print(response.result)  # {"status": "not_implemented", "stub": True}

Impact

Teams cannot share actors, actions, skills, or projects via server mode
The server.sync.auto and server.sync.interval config keys are registered but have no effect
Background sync never runs
Cross-device entity access is impossible

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

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

## Bug Report **Feature Area:** Server Mode and Multi-User — Entity Sync / Team Resource Sharing **Severity:** Medium (blocks team collaboration features) ### What Was Tested The A2A extension methods for entity synchronization (`_cleveragents/sync/pull`, `_cleveragents/sync/push`, `_cleveragents/sync/status`) in `src/cleveragents/a2a/facade.py`. ### Expected Behavior (from spec) Per the specification (ADR-023, Server Mode) and the spec's Server Mode section: > Entity synchronization between client and server uses A2A extension methods (`_cleveragents/sync/*`): > - **Auto-sync** (`server.sync.auto`): Entities sync on connection and at `server.sync.interval` (default: 300s) > - **Sync interval**: Background syncs at `server.sync.interval` (default: 300 seconds) > - **Manual sync**: Can be triggered explicitly when auto-sync is disabled > - **Direction**: Server namespaces are downloaded to local cache; local namespace entities are never uploaded automatically The spec also states that in server mode, a user can: > - Share actions, actors, skills, and projects with team members > - Access team-shared resources from any device ### Actual Behavior All three sync operations return stub responses: ```python # _cleveragents/sync/pull {"status": "not_implemented", "stub": True} # _cleveragents/sync/push {"status": "not_implemented", "stub": True} # _cleveragents/sync/status {"status": "not_implemented", "stub": True} ``` The handler code in `facade.py`: ```python def _handle_sync_stub(self, params: dict[str, Any]) -> dict[str, Any]: return {"status": "not_implemented", "stub": True} ``` ### Code Location - `src/cleveragents/a2a/facade.py` — `_handle_sync_stub` method (lines ~490-491) - `src/cleveragents/application/services/config_service.py` — `server.sync.auto` and `server.sync.interval` config keys are registered but never used ### Steps to Reproduce ```python from cleveragents.a2a.facade import A2aLocalFacade from cleveragents.a2a.models import A2aRequest facade = A2aLocalFacade() # Try to sync response = facade.dispatch(A2aRequest(method="_cleveragents/sync/pull", params={})) print(response.result) # {"status": "not_implemented", "stub": True} ``` ### Impact - Teams cannot share actors, actions, skills, or projects via server mode - The `server.sync.auto` and `server.sync.interval` config keys are registered but have no effect - Background sync never runs - Cross-device entity access is impossible ### Related - ADR-023 (Server Mode) — defines sync requirements - Issue #4926 — A2A HTTP Transport stub (prerequisite) - `src/cleveragents/a2a/facade.py` — sync stubs --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

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

freemo added a new dependency

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

#4971 EPIC: Entity Sync & Namespace Management — Server-Side Resource Sharing

HAL9000 referenced this issue

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

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

HAL9000 referenced this issue

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

EPIC: Entity Sync & Namespace Management — Server-Side Resource Sharing #4971

HAL9000 referenced this issue

2026-04-09 02:58:50 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 16) #5173

HAL9000 referenced this issue

2026-04-09 03:09:37 +00:00

[AUTO-WATCHDOG] Alert: Implementation Orchestrator STOPPED — Cannot Dispatch Workers (Cycle 21) #5201

HAL9000 added this to the v3.8.0 milestone

2026-04-09 05:43:19 +00:00

HAL9000 commented

2026-04-09 05:43:25 +00:00

Author

Owner

Label compliance fix applied:

Assigned milestone: based on issue scope (server-side implementation area)
Reason: Non-Epic, non-Legendary issue in State/In Progress was missing a milestone assignment per CONTRIBUTING.md requirements.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Assigned milestone: based on issue scope (server-side implementation area) - Reason: Non-Epic, non-Legendary issue in `State/In Progress` was missing a milestone assignment per CONTRIBUTING.md requirements. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer