docs(sdk-install): self-hosted bundle serving — ASSETS_URI is the serve ROOT, not the version dir

A locally built bundle (apps/sdk/dist) nests files under /<version>/<target>/;
pointing ASSETS_URI at that inner directory 404s the loader. Spell out the
serve-root semantics + USERTOURJS_BROWSER_TARGET, since this exact mistake has
burned two debugging sessions. Bump 0.3.2.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: winter100004

.agents/plugins/marketplace.json

@@ -2,7 +2,7 @@
   "plugins": [
     {
       "name": "usertour",
-      "version": "0.3.1",
+      "version": "0.3.2",
       "category": "Coding",
       "source": {
         "type": "local",

.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "usertour",
       "source": "./",
       "description": "Skills for authoring Usertour in-app onboarding content",
-      "version": "0.3.1"
+      "version": "0.3.2"
     }
   ]
 }

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "usertour",
   "description": "Skills for Usertour in-app onboarding — authoring content (flows, checklists, launchers, banners, surveys) and installing the Web SDK — via the Usertour API/MCP",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "author": {
     "name": "Usertour",
     "url": "https://www.usertour.io"

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "usertour",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Skills for Usertour in-app onboarding — authoring content (flows, checklists, launchers, banners, surveys) and installing the Web SDK — via the Usertour API/MCP",
   "author": {
     "name": "Usertour",

.cursor-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "usertour",
       "source": "./",
       "description": "Skills for authoring Usertour in-app onboarding content",
-      "version": "0.3.1"
+      "version": "0.3.2"
     }
   ]
 }

.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "usertour",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Skills for Usertour in-app onboarding — authoring content (flows, checklists, launchers, banners, surveys) and installing the Web SDK — via the Usertour API/MCP",
   "author": {
     "name": "Usertour",

skills/usertour-sdk-install/references/self-hosted.md

@@ -34,6 +34,18 @@ deployment (e.g. your app on `app.example.com`, Usertour on
 <!-- then the loader + usertour.init("<environment token>") -->
 ```
 
+That is the COMPLETE key set the loader/SDK reads, plus one more:
+`USERTOURJS_BROWSER_TARGET` (`"es2020"` | `"legacy"`) force-picks a bundle
+instead of the loader's user-agent sniff — only needed when the sniff guesses
+wrong (exotic webviews).
+
+**Serving a locally BUILT bundle (apps/sdk/dist)?** The dist layout carries a
+version layer — `/<version>/es2020/usertour.js` — and the bundle's baked-in CSS
+path expects `ASSETS_URI` to be the serve ROOT (it appends
+`/<version>/<target>/css/index.css` itself). Pointing `ASSETS_URI` at the
+target folder double-nests the path → CSS 404s → widgets render 0×0 with no
+error (this exact mistake has burned two debugging sessions).
+
 Confirm the exact key names + which are required against the docs above.
 
 ## Local dev vs full self-host — don't over-configure