fix(integrations): add zed to discovery catalog.json#3266
Merged
Conversation
zed is registered, registrar-aligned and registry-tested, but it was the only one of the 34 integrations absent from integrations/catalog.json, making it undiscoverable through the discovery manifest. Add the missing 'zed' entry (mirroring the sibling skills entries) and a registry<->catalog parity regression test so a future integration can't silently drift. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request fixes an integration discoverability gap by ensuring the zed integration is included in the Spec Kit discovery manifest (integrations/catalog.json) and adds a regression test to prevent future registry-vs-catalog drift.
Changes:
- Added a
zedentry tointegrations/catalog.json, consistent with other IDE skills-based integrations. - Added a
TestCatalogParitytest that asserts every registered integration (except thegenericfallback) is present in the catalog.
Show a summary per file
| File | Description |
|---|---|
tests/integrations/test_registry.py |
Adds a regression test to enforce catalog parity with INTEGRATION_REGISTRY (excluding generic). |
integrations/catalog.json |
Adds the missing zed integration entry so it becomes discoverable via the catalog. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Low
Collaborator
|
Thank you! |
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
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.
Description
integrations/catalog.jsonis the discovery manifest for Spec Kit integrations. Thezedintegration is registered inINTEGRATION_REGISTRY, registrar-aligned, and covered by the registry tests — but it is the only one of the 34 registered integrations missing from the catalog:So
zedis undiscoverable through the catalog while every sibling (including the other skills-based editors) is listed.Fix
"zed"entry tointegrations/catalog.json, mirroring the sibling skills entries (e.g.agy,lingma) —name: "Zed",description: "Zed editor skills-based integration",tags: ["ide", "skills"], consistent with the module's own "Zed editor integration — skills-based agent" description.TestCatalogParityregression test asserting every registered integration (except thegenericfallback) appears in the catalog, so this can't silently drift again.Testing
test_every_registered_integration_is_in_catalog: fails before (missing: ['zed'], verified by stashing the catalog change), passes after.tests/integrations/test_registry.pypasses (434 tests);uvx ruff checkclean; catalog.json validated as well-formed JSON.AI Disclosure
Found and fixed with Claude Code (Claude Opus 4.8) under my direction. AI computed the registry-vs-catalog set difference; I confirmed
zedwas the sole omission, matched the sibling entry shape, proved fail-before via stash, and reviewed the diff before submitting.