UAT: No dedicated YAML configuration file schema or loader for LSP server registration — agents lsp add --config cannot validate LSP server YAML configs #3004

Open
opened 2026-04-05 03:31:39 +00:00 by freemo · 5 comments
Owner

Transitioning issue to State/In Progress. Removed State/Verified. Added State/In Progress label. Blocked label remains unchanged.

Transitioning issue to State/In Progress. Removed State/Verified. Added State/In Progress label. Blocked label remains unchanged.
Author
Owner

Label compliance fix applied:

  • Added missing labels: Priority/Medium, State/Unverified, Type/Bug
  • Reason: Issue was missing all required labels per CONTRIBUTING.md. Inferred Type/Bug from the "UAT:" prefix. Applied Priority/Medium and State/Unverified as defaults.

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

Label compliance fix applied: - Added missing labels: `Priority/Medium`, `State/Unverified`, `Type/Bug` - Reason: Issue was missing all required labels per CONTRIBUTING.md. Inferred `Type/Bug` from the "UAT:" prefix. Applied `Priority/Medium` and `State/Unverified` as defaults. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
freemo added this to the v3.6.0 milestone 2026-04-05 03:38:05 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Confirmed
  • MoSCoW: Should Have

Valid finding verified during batch triage.


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

Issue triaged by project owner: - **State**: Verified - **Priority**: Confirmed - **MoSCoW**: Should Have Valid finding verified during batch triage. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — this is a spec compliance gap. The specification defines LSP server configuration files as a distinct entity type with YAML loading, but the implementation is missing the from_yaml_file() factory method, env var interpolation, and camelCase normalization. This creates inconsistency with all other config file types.
  • Milestone: v3.6.0 (already assigned — correct, as LSP integration is in scope for M7)
  • MoSCoW: Should Have — the spec defines this capability and it creates an inconsistency with other config loaders. It's important for completeness but not strictly blocking the milestone's core deliverables (container execution, cost/session budgets, etc.).
  • Parent Epic: #824

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — this is a spec compliance gap. The specification defines LSP server configuration files as a distinct entity type with YAML loading, but the implementation is missing the `from_yaml_file()` factory method, env var interpolation, and camelCase normalization. This creates inconsistency with all other config file types. - **Milestone**: v3.6.0 (already assigned — correct, as LSP integration is in scope for M7) - **MoSCoW**: Should Have — the spec defines this capability and it creates an inconsistency with other config loaders. It's important for completeness but not strictly blocking the milestone's core deliverables (container execution, cost/session budgets, etc.). - **Parent Epic**: #824 --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

Starting implementation on branch bugfix/m7-lsp-server-config-yaml-loader.

Difficulty assessment: Medium → starting at sonnet tier.

Plan:

  1. TDD: Write failing Behave scenarios first
  2. Implement from_yaml() and from_yaml_file() on LspServerConfig
  3. Add ${ENV_VAR} and ${ENV_VAR:default} interpolation
  4. Add camelCase → snake_case key normalization
  5. Verify CLI integration and coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

Starting implementation on branch `bugfix/m7-lsp-server-config-yaml-loader`. Difficulty assessment: Medium → starting at sonnet tier. Plan: 1. TDD: Write failing Behave scenarios first 2. Implement `from_yaml()` and `from_yaml_file()` on `LspServerConfig` 3. Add `${ENV_VAR}` and `${ENV_VAR:default}` interpolation 4. Add camelCase → snake_case key normalization 5. Verify CLI integration and coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
Author
Owner

All subtasks complete. Quality gates passed.

Implementation summary:

  • Added from_yaml(yaml_string) class method to LspServerConfig with full validation
  • Added from_yaml_file(path) class method to LspServerConfig with file existence checks
  • Added ${ENV_VAR} and ${ENV_VAR:default} interpolation for all string fields
  • Added camelCase → snake_case key normalization (workspaceSettingsworkspace_settings, initializationOptionsinitialization)
  • Updated agents lsp add --config CLI to use from_yaml_file() for proper validation
  • 18 Behave scenarios passing, lint clean, typecheck clean

Creating PR.


Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

All subtasks complete. Quality gates passed. **Implementation summary:** - Added `from_yaml(yaml_string)` class method to `LspServerConfig` with full validation - Added `from_yaml_file(path)` class method to `LspServerConfig` with file existence checks - Added `${ENV_VAR}` and `${ENV_VAR:default}` interpolation for all string fields - Added camelCase → snake_case key normalization (`workspaceSettings` → `workspace_settings`, `initializationOptions` → `initialization`) - Updated `agents lsp add --config` CLI to use `from_yaml_file()` for proper validation - 18 Behave scenarios passing, lint clean, typecheck clean Creating PR. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
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.

Blocks
#824 Epic: LSP Functional Runtime
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#3004
No description provided.