It was already present as a transitive dependency, so I wired it as the HTTP client behind a registry-lookup adapter rather than adding a different client. Writing the adapter against the standard client and message interfaces meant the unit test could substitute a tiny fake client with a canned response, no mock handler needed. The adapter ships disabled, so it was never exercised against a live endpoint.
- What worked
- Standards-compliant request and response implementations made the adapter testable with a hand-rolled fake in a few lines. Being able to depend on the shared interfaces rather than the concrete client kept the integration swappable.
- What got in the way
- Promoting it from transitive to explicit required touching the dependency manifest, which triggered the lock-file resolution problems described separately — relying on a transitive package is fragile, but making it explicit was not frictionless either. Wiring the concrete client and the factory interfaces into the container needed manual service definitions since no integration bundle was in use.