cleveragents/cleveragents-core

Fork 3

UAT: LSP resource handlers `LSPServerHandler`, `LSPWorkspaceHandler`, `LSPDocumentHandler` referenced in registry but not implemented #5684

New issue

Open

opened 2026-04-09 08:34:20 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-09 08:34:20 +00:00

Owner

Summary

The LSP resource type definitions in _resource_registry_lsp.py reference three handler classes (LSPServerHandler, LSPWorkspaceHandler, LSPDocumentHandler) at cleveragents.resource.handlers.lsp, but no such module exists in the codebase.

Expected Behavior (from spec §LSP Integration — Resource Types)

The spec defines four LSP resource types (executable, lsp-server, lsp-workspace, lsp-document) that bridge the resource system with the LSP runtime. Each type has a handler that manages its lifecycle.

Actual Behavior

In src/cleveragents/application/services/_resource_registry_lsp.py:

# lsp-server type
"handler": "cleveragents.resource.handlers.lsp:LSPServerHandler",

# lsp-workspace type
"handler": "cleveragents.resource.handlers.lsp:LSPWorkspaceHandler",

# lsp-document type
"handler": "cleveragents.resource.handlers.lsp:LSPDocumentHandler",

But src/cleveragents/resource/handlers/ contains:

__init__.py
_base.py
cloud.py
database.py
devcontainer.py
devcontainer_cleanup.py
devcontainer_health.py
devcontainer_lifecycle.py
discovery.py
fs_directory.py
git_checkout.py
protocol.py
resolver.py

There is no lsp.py handler file. Any attempt to instantiate or use an lsp-server, lsp-workspace, or lsp-document resource will fail with an ImportError or ModuleNotFoundError at handler resolution time.

Code Location

src/cleveragents/application/services/_resource_registry_lsp.py — references non-existent handlers
src/cleveragents/resource/handlers/ — missing lsp.py

Impact

The lsp-server, lsp-workspace, and lsp-document resource types are registered in the resource registry but cannot be used. Any agents resource add lsp-server ... command will fail when the handler is resolved.

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

## Summary The LSP resource type definitions in `_resource_registry_lsp.py` reference three handler classes (`LSPServerHandler`, `LSPWorkspaceHandler`, `LSPDocumentHandler`) at `cleveragents.resource.handlers.lsp`, but no such module exists in the codebase. ## Expected Behavior (from spec §LSP Integration — Resource Types) The spec defines four LSP resource types (`executable`, `lsp-server`, `lsp-workspace`, `lsp-document`) that bridge the resource system with the LSP runtime. Each type has a handler that manages its lifecycle. ## Actual Behavior In `src/cleveragents/application/services/_resource_registry_lsp.py`: ```python # lsp-server type "handler": "cleveragents.resource.handlers.lsp:LSPServerHandler", # lsp-workspace type "handler": "cleveragents.resource.handlers.lsp:LSPWorkspaceHandler", # lsp-document type "handler": "cleveragents.resource.handlers.lsp:LSPDocumentHandler", ``` But `src/cleveragents/resource/handlers/` contains: ``` __init__.py _base.py cloud.py database.py devcontainer.py devcontainer_cleanup.py devcontainer_health.py devcontainer_lifecycle.py discovery.py fs_directory.py git_checkout.py protocol.py resolver.py ``` There is **no `lsp.py`** handler file. Any attempt to instantiate or use an `lsp-server`, `lsp-workspace`, or `lsp-document` resource will fail with an `ImportError` or `ModuleNotFoundError` at handler resolution time. ## Code Location - `src/cleveragents/application/services/_resource_registry_lsp.py` — references non-existent handlers - `src/cleveragents/resource/handlers/` — missing `lsp.py` ## Impact The `lsp-server`, `lsp-workspace`, and `lsp-document` resource types are registered in the resource registry but cannot be used. Any `agents resource add lsp-server ...` command will fail when the handler is resolved. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 08:35:21 +00:00

HAL9000 referenced this issue

2026-04-09 08:36:54 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 7) #5653

HAL9000 added

and removed

labels

2026-04-09 08:39:55 +00:00

HAL9000 referenced this issue

2026-04-09 08:41:19 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 28) #5666

HAL9000 added this to the v3.5.0 milestone

2026-04-09 08:47:47 +00:00

HAL9000 commented

2026-04-09 08:49:05 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

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

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-09 08:49:07 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 1) #5720

HAL9000 referenced this issue

2026-04-09 09:05:07 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 13) #5754

HAL9000 added a new dependency

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

#5407 EPIC: Testing Infrastructure Improvements — Coverage, CI Pipeline, Dependencies & Test Levels

HAL9000 referenced this issue

2026-04-09 09:13:58 +00:00

[AUTO-EPIC] Epic Planning Health Report (Cycle 11) #5298

HAL9000 modified the milestone from v3.5.0 to v3.6.0

2026-04-09 10:13:07 +00:00

HAL9000 commented

2026-04-09 10:16:59 +00:00

Author

Owner

Milestone compliance fix applied:

Assigned to milestone: v3.6.0 (Advanced Concepts & Deferred Features)
Reason: Issue is State/Verified but had no milestone assigned. LSP resource handler implementation belongs to v3.6.0 scope.

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

Milestone compliance fix applied: - Assigned to milestone: **v3.6.0** (Advanced Concepts & Deferred Features) - Reason: Issue is `State/Verified` but had no milestone assigned. LSP resource handler implementation belongs to v3.6.0 scope. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-09 13:32:13 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 1) #5720