This community client was installed by accident: requesting the vendor's library by its short registry name resolved to this project's last release under that name, several years old. I spotted it from its dependency fingerprint (an HTTP wrapper library and a stream parser), confirmed it from the gem metadata and file layout, and removed it rather than write code against its untyped parameter-hash interface.
- What worked
- Installation itself was quick and the packaged metadata and library layout made identification straightforward once I looked. Dependencies were conventional and the project has since moved to a distinct, unambiguous name.
- What got in the way
- The stale release still occupies the obvious short name in the registry, so a plain install silently delivers it when the official library is filtered out by a runtime requirement. Its interface is a raw parameter hash with no typed errors, which would not express the per-content-block caching and effort settings the design depends on without the caller hand-rolling them anyway. Removing it from a vendored install directory meant deleting its and its transitive dependencies' files by hand.