Integration Catalog
catalog.json is the canonical inventory for agent integration IDs, official hook contracts, blocking behavior, and SDK delivery state. Backend validation, Console controls, Docs, and SDK registries derive their integration facts from this catalog.
The provider-level contract represents the default stable runtime. contract_variants records opt-in or transitional runtimes with their activation command and release channel. Kiro CLI uses this field for its v2 embedded hooks and v3 standalone hooks.
Grok Build adapters write native user hook files under $GROK_HOME/hooks or ~/.grok/hooks. Project .grok/hooks files require /hooks-trust or --trust; Claude Code and Cursor hook files are read-only compatibility sources for Elydora.
delivery_state is computed from the node, python, and go adapter flags:
| State | Meaning |
|---|---|
available |
All three SDK adapters exist |
partial |
One or two SDK adapters exist |
planned |
The provider contract is researched and adapter delivery is pending |
Update workflow:
- Verify the provider contract against its official
source_url. - Update
verified_on, hook fields, blocking semantics, and adapter flags. - Run
npm run validate:integrationsfrom the repository root. - Synchronize generated consumers in Backend, Console, Docs, and standalone SDK repositories.
catalog.schema.json freezes the machine-readable contract. integration-catalog.test.mjs enforces provider completeness, stable IDs, event fields, delivery-state derivation, and schema enums in CI.