lemma-sdk 0.2.46 → 0.3.0

package/README.md

@@ -45,6 +45,22 @@ const records = await client.records.list("tickets");
 
 Pod-scoped namespaces include `tables`, `records`, `agents`, `conversations`, `workflows`, `schedules`, `functions`, `files`, `desks`, `integrations`, `resources`, and `datastore`. New runtime code should use agents plus conversations.
 
+## Browser bundle (no-build HTML)
+
+For a no-build HTML desk or a conversation widget, load the prebuilt bundle from the host instead of npm-importing. The host injects pod context as `window.__LEMMA_CONFIG__` (podId / apiUrl / authUrl), so the client takes no arguments:
+
+```html
+<script src="https://api.lemma.work/public/sdk/lemma-client.js"></script>
+<script>
+  const client = new window.LemmaClient.LemmaClient(); // reads window.__LEMMA_CONFIG__
+  const state = await client.initialize();
+  if (state.status !== "authenticated") client.auth.redirectToAuth();
+  const records = (await client.records.list("tickets", { limit: 50 })).items;
+</script>
+```
+
+The bundle exposes the same client and namespaces as the npm package (a legacy `window.Lemma` alias also points at it). `import.meta.env`/`VITE_LEMMA_*` are only for the React/Vite path; the browser bundle resolves config from `window.__LEMMA_CONFIG__`.
+
 Org and user surfaces include `users`, `organizations`, `pods`, `podMembers`, `podJoinRequests`, and `podSurfaces`.
 
 ## React Package