@noodleseed/assistant 1.19.0 → 1.20.0

package/README.md

@@ -202,6 +202,74 @@ claims, or tool input. The endpoint key must match the authored name. Noodle val
 only in private short-lived session state, and an omitted route leaves only dependent tools unavailable.
 Mint a new session when the user's selected account or cluster changes.
 
+#### Public website embeds
+
+Everything above serves a signed-in user through your backend. A `publicWebsite(...)` surface serves the
+same assistant to anonymous visitors — a marketing site, docs, or landing page — with a **required**
+capability allowlist, per-surface daily budgets, and a kill switch. `noodle deploy` provisions a stable
+embed id and prints a one-line snippet; the embed id is deliberately not a credential:
+
+```html
+<script src="https://cloud.noodleseed.dev/v1/assistant/embed.js"
+        data-embed-id="pub_7f2q4k9x" async></script>
+```
+
+In a bundled app, the same public surface mounts through the element or React wrapper with `embedId`
+instead of `sessionEndpoint` — the two are mutually exclusive, and a public embed needs no backend route:
+
+```tsx
+<AssistantWidget embedId="pub_7f2q4k9x" serviceUrl="https://cloud.noodleseed.dev" />
+```
+
+A public embed opens its session on **first open**, never on mount — every mount would otherwise spend
+one of the surface's daily admission budget. Add `signIn: true` to the surface and it becomes **mixed**:
+anonymous visitors start immediately, and identity-dependent capabilities raise the sign-in flow below.
+Before shipping, preflight the host with `noodle assistant embed --check --surface public` (or `mixed`) —
+it verifies `script-src` too, the one CSP directive whose failure runs no widget code at all.
+
+#### Mid-conversation sign-in (mixed surfaces)
+
+On a `publicWebsite({ signIn: true })` surface, an anonymous visitor who reaches an identity-dependent
+capability sees a "Sign in to continue" card, and the widget raises `assistant-sign-in-requested` with a
+single-use `signInTicket` in its detail. The page signs the visitor in however it already does, then its
+backend spends the ticket with the **same** helper and its own client credentials — same endpoint, same
+`user` shape, plus the ticket:
+
+```ts
+const session = await createAssistantSession({
+  serviceUrl: process.env.NOODLE_SERVICE_URL!,
+  clientId: process.env.NOODLE_ASSISTANT_CLIENT_ID!,
+  clientSecret: process.env.NOODLE_ASSISTANT_CLIENT_SECRET!,
+  origin: process.env.PUBLIC_APP_ORIGIN!,
+  user: { id: user.id, email: user.email, roles: user.roles },
+  signInTicket, // from the widget's assistant-sign-in-requested event, via your page
+});
+```
+
+The visitor keeps the same conversation with a new token; the anonymous token dies at that moment.
+`signInTicket` and `context` are mutually exclusive — an elevation continues an existing session.
+`routing` IS accepted here, and this is the moment to send it: elevation is the first authenticated
+exchange, so it is the only chance a routed connector's session gets its backend-verified customer
+routes. Possession of a ticket alone elevates nothing:
+spending it also requires your client credentials, and the service checks your tenant owns that
+conversation. (The ticket is deliberately **not** called a continuation: the server-held interaction
+continuation described below must never reach browser code, while this value's whole job is to travel
+through the page.)
+
+A refused spend throws `AssistantSessionExchangeError`; branch on `error.elevationRefusal`:
+
+| Code | What happened | What to do |
+| :-- | :-- | :-- |
+| `elevation_ticket_expired` | The visitor took too long (tickets live 10 minutes) | Re-prompt; the widget raises a fresh ticket when they retry the action |
+| `elevation_ticket_invalid` | Stale, spent, or double-submitted ticket | Same recovery; log it — a burst is a replay signal |
+| `elevation_tenant_mismatch` | Your credentials do not own that conversation | Alert someone; never retry |
+| `elevation_already_signed_in` / `elevation_session_unavailable` | The conversation moved on | Ask the visitor to refresh |
+
+`error.detail.serviceCode === "elevation_unavailable"` (a 503) means the deployment has no elevation
+store configured — page the operator, not the visitor. Failures without a code (fresh-mint refusals,
+proxy errors) carry `error.detail.status`, and `error.detail.retryable` is `true` only for
+infrastructure 5xx responses.
+
 Then add the framework-neutral element:
 
 ```ts

package/dist/{chunk-S373FCAI.js → chunk-52XT7BLR.js}

@@ -8383,11 +8383,16 @@ function toAssistantClientEvent(event) {
         return event;
       }
       break;
-    case "auth_requested":
-      if (hasString(value, "id") && hasString(value, "tool") && hasString(value, "continuation") && hasString(value, "expiresAt") && hasOptionalTurnId(value)) {
-        return event;
+    case "auth_requested": {
+      const signInTicket = typeof value.signInTicket === "string" ? value.signInTicket : typeof value.continuation === "string" ? value.continuation : void 0;
+      if (hasString(value, "id") && hasString(value, "tool") && signInTicket !== void 0 && hasString(value, "expiresAt") && hasOptionalTurnId(value)) {
+        return {
+          event: "auth_requested",
+          data: { ...value, signInTicket }
+        };
       }
       break;
+    }
     case "interaction_resolved":
       if (hasString(value, "id") && (value.action === void 0 || isInteractionAction(value.action)) && hasOptionalTurnId(value)) {
         return event;
@@ -9261,4 +9266,4 @@ export {
   AssistantClientError,
   createAssistantClient
 };
-//# sourceMappingURL=chunk-S373FCAI.js.map
+//# sourceMappingURL=chunk-52XT7BLR.js.map