equiplisted

# Equip Install and configure Coral companion tooling for Claude Code. ## Verb Mapping - `/equip <pkg>` -> `coral-cli expansion equip <pkg>` - `/equip --list` -> `coral-cli expansion list` - `/equip --update <pkg>` -> `coral-cli expansion update <pkg>` - `/equip uninstall <pkg>` -> `coral-cli expansion unequip <pkg>` - If this surface exposes it, `/equip info <pkg>` -> `coral-cli expansion info <pkg>` - Internal catalog-removal diagnostics map to `coral-cli expansion remove-catalog <pkg>` when that CLI surface is exposed. ## Runtime Model `coral-cli expansion` manages engines through the Expansion lifecycle. Engine identity is package-local; commands should route by declared metadata (`id`, `tier`, `fills`, `status`) instead of hard-coding package semantics. - `fills` declares the runtime binding(s) an engine can provide, such as `kb.fts`, `kb.vector`, or `kb.embedding`. - If an engine fills `kb.vector`, vector search can use it for vector queries. If no vector engine is equipped, vector queries fail with `binding_empty` until a vector engine is equipped. - If an engine fills `kb.embedding`, engines that require embeddings can use that binding after the embedder is equipped. - If an engine fills `kb.fts`, text search can use it for full-text queries. ## Tier Semantics `coral-cli expansion list` and `coral-cli expansion info <pkg>` expose `tier` on engine entries. | tier | Status source