Skip to content

fix(integrations): add zed to discovery catalog.json#3266

Merged
mnriem merged 1 commit into
github:mainfrom
jawwad-ali:fix/zed-missing-from-catalog
Jun 30, 2026
Merged

fix(integrations): add zed to discovery catalog.json#3266
mnriem merged 1 commit into
github:mainfrom
jawwad-ali:fix/zed-missing-from-catalog

Conversation

@jawwad-ali

Copy link
Copy Markdown
Contributor

Description

integrations/catalog.json is the discovery manifest for Spec Kit integrations. The zed integration is registered in INTEGRATION_REGISTRY, registrar-aligned, and covered by the registry tests — but it is the only one of the 34 registered integrations missing from the catalog:

set(INTEGRATION_REGISTRY) - {"generic"} - set(catalog["integrations"])  # -> {'zed'}

So zed is undiscoverable through the catalog while every sibling (including the other skills-based editors) is listed.

Fix

  • Add the "zed" entry to integrations/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.
  • Add a TestCatalogParity regression test asserting every registered integration (except the generic fallback) appears in the catalog, so this can't silently drift again.

Testing

  • New test_every_registered_integration_is_in_catalog: fails before (missing: ['zed'], verified by stashing the catalog change), passes after.
  • Full tests/integrations/test_registry.py passes (434 tests); uvx ruff check clean; catalog.json validated as well-formed JSON.

AI Disclosure

  • I did use AI assistance (describe below)

Found and fixed with Claude Code (Claude Opus 4.8) under my direction. AI computed the registry-vs-catalog set difference; I confirmed zed was the sole omission, matched the sibling entry shape, proved fail-before via stash, and reviewed the diff before submitting.

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>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 zed entry to integrations/catalog.json, consistent with other IDE skills-based integrations.
  • Added a TestCatalogParity test that asserts every registered integration (except the generic fallback) 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

@mnriem mnriem merged commit b4a0f8b into github:main Jun 30, 2026
12 checks passed
@mnriem

mnriem commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants