Changelog
Yogiyo's upstream user journey is an anonymous guest checkout with phone/SMS verification, not a reusable personal app-account login. The provider now matches the same frontend UX pattern as Modu Parking: discovery and cart preview run without a Connection, verify-phone creates a short-lived server-side anonymous session, and the following OTP/order handoff steps consume the returned yogiyo_session_id.
Stop creating or passing Yogiyo APIFuse Connections. Call yogiyo/verify-phone without X-ApiFuse-Connection-Id, persist the returned opaque yogiyo_session_id only for the current checkout attempt, then pass that id to yogiyo/confirm-phone and yogiyo/place-order. If the session expires, restart at verify-phone. Read operations remain connection-free.