@helpai/elements 0.68.5 → 0.69.0

package/index.d.ts

@@ -535,7 +535,7 @@ interface FormDef {
    * answers. Default `true`. Set `false` to keep the marker plain — e.g.
    * sensitive answers that shouldn't linger on screen (pairs with
    * `mirrorToContext: false`; the backend should also omit `values` from the
-   * `/activity` records for such forms).
+   * `bootstrap` `formSubmissions` records for such forms).
    */
   reviewable?: boolean;
   /** BCP-47 locale the top-level strings (title / fields copy) are authored in. */
@@ -1098,8 +1098,8 @@ interface ChatWidgetOptions {
   agentApiBaseUrl?: string;
   /**
    * Data-API base (no trailing slash) — the `module-help-ai-data-api`
-   * service serving content, form definitions, and form submissions at
-   * root-level paths (`/content`, `/forms`, `/activity`, `/submit-form`).
+   * service serving content, form definitions, and form submissions under
+   * `/pai/*` (`content`, `bootstrap`, `submit-form`).
    * Set it for a standalone local module (e.g. `http://localhost:3106`).
    * Precedence: this option > server-pushed `config.dataApiBaseUrl` > derived
    * from the main origin (`${baseUrl}/api/data`, e.g.
@@ -1263,7 +1263,7 @@ interface ResolvedOptions {
  * and the public key are deliberately excluded — those are client concerns.
  *
  * Form definitions no longer ride this config: the widget fetches them from
- * the data-API (`GET /forms`). A stale backend still pushing
+ * the data-API (`GET /pai/bootstrap`). A stale backend still pushing
  * `config.forms` is ignored.
  */
 interface ServerConfig$1 {
@@ -1800,9 +1800,9 @@ declare const widgetSettingsSchema: z.ZodObject<{
       label: z.ZodString;
       type: z.ZodEnum<{
         number: "number";
-        url: "url";
         email: "email";
         date: "date";
+        url: "url";
         text: "text";
         tel: "tel";
         time: "time";
@@ -2139,9 +2139,9 @@ declare const widgetConfigSchema: z.ZodObject<{
       label: z.ZodString;
       type: z.ZodEnum<{
         number: "number";
-        url: "url";
         email: "email";
         date: "date";
+        url: "url";
         text: "text";
         tel: "tel";
         time: "time";
@@ -2477,9 +2477,9 @@ declare const widgetConfigPartialSchema: z.ZodObject<{
       label: z.ZodString;
       type: z.ZodEnum<{
         number: "number";
-        url: "url";
         email: "email";
         date: "date";
+        url: "url";
         text: "text";
         tel: "tel";
         time: "time";
@@ -2775,9 +2775,9 @@ declare const widgetSettingsPartialSchema: z.ZodObject<{
       label: z.ZodString;
       type: z.ZodEnum<{
         number: "number";
-        url: "url";
         email: "email";
         date: "date";
+        url: "url";
         text: "text";
         tel: "tel";
         time: "time";
@@ -2920,7 +2920,7 @@ type ConnectionConfigPartial = z.infer<typeof connectionConfigPartialSchema>;
  *
  * Two deltas vs the editable surface:
  *   - `forms` is omitted — resolved form definitions are served by the
- *     data-API (`GET /forms`), not pushed on the handshake. A stale
+ *     data-API (`GET /pai/bootstrap`), not pushed on the handshake. A stale
  *     backend still sending `config.forms` passes through `.loose()` and is
  *     ignored by the runtime merge.
  *   - `dataApiBaseUrl` is pushable — lets a deployment point the widget at its