feat(agent): capability registry + read-only /capabilities view#167
Open
OnlyTerp wants to merge 4 commits into
Open
feat(agent): capability registry + read-only /capabilities view#167OnlyTerp wants to merge 4 commits into
OnlyTerp wants to merge 4 commits into
Conversation
Create a new capabilities module with the unified CapabilityEntry view type and pure adapter functions that project existing scattered definitions (MCP catalogue, stored servers, skills, prompt templates) into CapabilityEntry[]. Includes a detectCollisions function for cross-source id collision detection. No existing consumers modified; this is purely additive. Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Add CapabilityRegistry class with register/registerAll/get/has/list methods. Shadow-rejects on id collision unless override:true is passed. Includes static fromSources() builder and collision audit log. Non-breaking parallel layer; does not rewire existing consumers. Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Add a /capabilities dashboard page that builds a CapabilityRegistry from all four client-side sources (MCP catalogue, stored servers, skills, prompt templates) and renders capabilities grouped by provenance with availability indicators and a collisions section for duplicate-id conflicts. Added to sidebar nav. Sources that lack client-side accessors are gracefully skipped and noted. Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A capability registry that unifies the currently-scattered capability definitions (MCP catalogue, stored MCP servers, skills, prompt templates) into one read-only view, plus a
/capabilitiespage. This is a non-breaking parallel layer — existing registration/consumption paths are untouched.Changes
frontend/src/features/agent/capabilities/: pure read-only adapters mapping each source into a unifiedCapabilityEntry; a non-enforcingdetectCollisions; and aCapabilityRegistryclass that shadow-rejects id collisions (with explicit{ override: true }opt-in), records an audit log, and builds from sources viafromSources(...)./capabilitiesdashboard view: capabilities grouped by provenance + a collisions section. Reads the static MCP catalogue and GETs plugins/skills/prompt-templates; degrades gracefully if a source is unavailable.Verification
typecheck+lint+build→ clean; adapter + registry + view-model unit tests pass.Non-goals