3 people e9f32eaebe fix: resolve telegram/slack name collision between tool and channel registries (#346) ...

When installing the Telegram WASM channel via the web UI, a name collision
between registry/tools/telegram.json and registry/channels/telegram.json
caused the tool entry to win, installing to ~/.ironclaw/tools/ instead of
~/.ironclaw/channels/. This made activation fail with "WASM runtime not
available".

- Add `get_with_kind()` to ExtensionRegistry for kind-aware lookup
- Use `kind_hint` parameter in `install()` to resolve collisions
- Rename tool entries to avoid future collisions: telegram → telegram-mtproto,
  slack → slack-tool
- Fix `_bundles.json` stale reference (tools/slack → tools/slack-tool)
- Fix `cache_discovered()` to deduplicate by (name, kind) consistently
- Add path traversal validation to install/activate/remove entry points
- Add tests for kind-aware lookup, discovery cache, and bundle resolution

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>

2026-02-24 15:29:25 +08:00

..

channels

feat: embedded registry catalog and WASM bundle install pipeline (#283)

2026-02-21 05:43:28 +00:00

tools

fix: resolve telegram/slack name collision between tool and channel registries (#346)

2026-02-24 15:29:25 +08:00

_bundles.json

fix: resolve telegram/slack name collision between tool and channel registries (#346)

2026-02-24 15:29:25 +08:00