@biab-dev/sdk 0.7.5 → 0.7.51

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +29 -0
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -2,6 +2,35 @@
2
2
 
3
3
  **Alpha:** This package is in an **alpha** release. APIs and behavior may change without notice. It is **not** intended for production use yet—evaluate only in development, staging, or experiments.
4
4
 
5
+ ## Releases
6
+
7
+ > **Versioning convention:** the patch field's tens digit identifies the
8
+ > feature group (e.g. `0.7.5x` = chatbot work). Hot-fixes within a group
9
+ > stay in the same band — `0.7.51`, `0.7.52`, … — so consumers on
10
+ > `^0.7.5` pick them up automatically. New features bump the next band
11
+ > (`0.7.6`, then `0.7.61`, `0.7.62`, …).
12
+
13
+ ### 0.7.51
14
+
15
+ - **CORS preflight on the chatbot routes.** The browser-side widget on a
16
+ developer's site (e.g. `*.vercel.app`) was hitting
17
+ `Access-Control-Allow-Origin` failures against `biab.app/api/package/v1/chatbot/*`.
18
+ The host now reflects the request `Origin` (gated by the API key's
19
+ per-host allowlist) and serves a 204 preflight on `OPTIONS`. No SDK
20
+ code change — bumping ensures consumers pick up the matching host
21
+ release.
22
+
23
+ ### 0.7.5
24
+
25
+ - **Chatbot UI passthrough working.** Fixed the `Window.fetch` binding bug that broke every embed (`Embed unavailable: Can only call Window.fetch on instances of Window`) when the SDK client was used inside a browser. The widget now mounts cleanly and renders whatever the org configured in their dashboard — system prompt, knowledge base, model, temperature, handoff dial — without the consumer having to know any of those values exist.
26
+ - Typed `ChatbotConfig.frontDeskEnabled` and `ChatbotConfig.handoffThreshold` so consumers can branch on the org's subscription tier (e.g. render their own "Talk to a person" CTA only when live front-desk handoff is unlocked). The host enforces tier server-side regardless; these fields are for SDK-side UI.
27
+
28
+ ### 0.7.4
29
+
30
+ - **Tenant auth is live.** An org's end-users can sign in / sign up / sign out of a developer site through the `createAuthHandler` mounted at `/api/biab-auth`, with the `<SignIn>`, `<SignOut>`, and `useUser` hooks ready to drop into a host UI. WorkOS handles the identity round-trip; the SDK keeps the session and exposes the current user.
31
+
32
+ ---
33
+
5
34
  Phase 4 scaffold for the Business In A Box developer SDK.
6
35
 
7
36
  This package is the client-side half of the package architecture defined in:
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@biab-dev/sdk",
3
- "version": "0.7.5",
3
+ "version": "0.7.51",
4
4
  "private": false,
5
- "description": "[alpha] Business In A Box developer SDK — not for production; site-scoped collections, assets, named actions, and embeddable storefront / cart / checkout / blog / chatbot surfaces.",
5
+ "description": "[alpha] Business In A Box developer SDK — not for production. Embeddable storefront / cart / checkout / blog / chatbot surfaces, tenant sign-in / sign-up / sign-out flow, site-scoped collections + assets + named actions, and a typed package-API client. The chatbot widget passes the org's dashboard config (model, knowledge base, tone, handoff dial) straight through; live front-desk handoff is gated on the org's subscription plan server-side.",
6
6
  "type": "module",
7
7
  "sideEffects": false,
8
8
  "files": [