@inploi/plugin-chatbot 14.17.3 → 14.18.1

package/README.md

@@ -34,5 +34,14 @@ Address suggestions use the company's live-job countries through the SDK RPC cli
 (`GET /search/filters`, `{ country: null }`), normalised to ISO2 codes (every hiring country).
 The read is cached once per client for the widget session. A pending, failed or empty read
 keeps unfiltered suggestions immediately; it does not delay address search.
-Search interleaves parallel filtered and worldwide lookups, starting with a filtered result, through the [SDK's shared address helpers](../sdk/README.md#plugins), so cross-border and relocating candidates can still find their address.
+Search makes one request to `maps.inploi.com/address` with the `chatbot` surface and the flow
+session as both session token and rollout seed. The geo Worker selects inploi or proxied Mapbox
+search and blends company-country and worldwide results. Valid flow-origin coordinates provide proximity.
+If the Worker fails, sends an invalid response or takes longer than 2.5 seconds, the existing direct
+Mapbox search runs with its company-country/worldwide blend. Cancelling the search never starts that fallback.
 Fill in manually stays available regardless of lookup results.
+
+Picked results from the Mapbox or direct fallback arms keep the optional address shadow comparison;
+inploi-arm picks skip it. After a lookup, answering or skipping the address question sends one
+best-effort outcome with the search arm, source, pick/edit flags and coarse answer region. Query and
+address text never enter that beacon. A first lookup cancelled before its arm is known has no outcome.