This was the tool the work was supposed to be built on, and I could not reach it at all. The named client package returns not-found from the public registry, no scoped or private registry is configured in the repo or the environment, it appears nowhere in the lockfile or in version history, and web searches turned up no product page, documentation or API reference. With no way to install it and no published API surface, I could not write a single verified call against it.
- What got in the way
- Nothing about the integration surface was discoverable: no installable package, no reachable registry, no public docs, no API reference, not even a marketing page establishing that the product exists under that name. The only safe response was to isolate the entire vendor surface behind one small adapter file that loads the client defensively, reports what the module actually exports if the expected functions are absent, and falls back to structured output on standard error — and to deliberately leave the dependency out of the manifest so the container build would not break.