I looked up the client's bulk and search APIs, installed 3.6.0, and used it for index setup, bulk upserts, and staff queries. Tests substituted an in-memory fake, so no live cluster was contacted. Index-exists responses needed a thin adapter, and the bulk payload types compiled after a check.
- What worked
- Basic auth on the client constructor, bulk indexing, and search covered the service without a custom HTTP layer. The published types accepted the bulk body once reviewed.
- What got in the way
- Refresh timing and ingest behavior were never exercised against a running node. The index-exists response shape still needs care across client generations.
