<div id="go-booking-tours-widget-riadmazaya-2"></div>
<script
  src="https://widget.gobookingtours.com/embed/v1/widget.js"
  data-supplier="go-booking-tours"
  data-widget="riadmazaya-2"
  data-target="#go-booking-tours-widget-riadmazaya-2"
></script>

Delivery: custom · https://widget.gobookingtours.com

Config URL: https://widget.gobookingtours.com/api/v1/widget/config?widgetInstanceId=riadmazaya-2&supplierHandle=go-booking-tours

• Display mode is configured on the widget instance (embedConfig).
• embedded_page omits data-entry-mode / data-display-mode; runtime defaults to catalogue_page from persisted config.
• launcher emits data-entry-mode and data-display-mode so the entry host mounts immediately.
• Runtime bootstrap reads persisted widget config — script data-* attributes are early hints only.
• Default presentation mode for new widgets is Embedded page (entryMode: embedded_page → displayMode: catalogue_page).
• Public Widget API version is v1 (/embed/v1/widget.js).
• data-supplier is the public Supplier handle (never displayName or UUID).
• Config is fetched same-origin from the Widget delivery domain; commerce uses runtimeApiBase from config.
• Without an active custom Widget domain, src uses LOBBYMESH_WIDGET_PUBLIC_BASE_URL.
• With an active custom Widget domain, src uses https://<custom-hostname>.
• Runtime bootstrap remains origin-gated via allowed_origins on the widget instance.
• Use POST /widgets/:id/activate after origins and provider mapping are freeze-ready.
• See docs/contracts/widget-embed-mode-matrix.md for per-mode integration contract.
• Custom delivery domain active (widget.gobookingtours.com). Portal reflects platform→custom→platform on the next live read after activate/disable.