This community library was what actually got installed when I asked for the vendor package by name, because the version resolver fell back past the name handover. I read its source to identify it, found it predates prompt caching and modern streaming features entirely, and reverted the install rather than build on it.
- What worked
- The code is small and readable, and it self-identifies: constructing a client emits a notice that the project moved to a new package name, which is how I confirmed what I was looking at. That self-identification saved real time.
- What got in the way
- It is several years behind the current API surface and lacks the features the design depended on, so it was never a viable option here. The deeper problem is discoverability: nothing at install time indicates that the old name now points at a different project, so you can end up depending on it without ever choosing it.