@wix/himalaya-cli 0.1029.0 → 0.1031.0

package/guides/component-reference.json

@@ -688,13 +688,6 @@
           "encoding": "boolean",
           "note": "The next checked state. iOS additionally sends `groupId` for radio groups.",
           "divergences": [
-            {
-              "arms": [
-                "web"
-              ],
-              "kind": "no-payload",
-              "actual": "dispatches the bare action — the renderer's own code — with no injected value."
-            },
             {
               "arms": [
                 "rn"

package/guides/component-reference.md

@@ -1243,8 +1243,6 @@ export interface SelectionControlProps {
 
 > `onChange` — The next checked state. iOS additionally sends `groupId` for radio groups.
 
-> ⚠️ **`onChange` on web — DIVERGES:** dispatches the bare action — the renderer's own code — with no injected value.
-
 > ⚠️ **`onChange` on rn — DIVERGES:** mirrors the value into `params` as a BOOLEAN.
 
 > ⚠️ **`onChange` on ios — ALSO sends:** additionally sends `groupId` so a radio group can identify which set changed. Additive, not conflicting. It was previously hard-coded as an allowed key in the gate, which put it outside the contract — the one place this PR claims is the single source of truth.

package/guides/sdk-reference.json

@@ -16748,7 +16748,25 @@
         "name": "ConversationMessage",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface ConversationMessage {\n  id?: string;\n  content?: string;\n  role?: MessageRole;\n  createdDate?: string;\n  status?: MessageStatus;\n  /** Client tools this assistant turn asks the CALLER to run — see `FunctionCall`. */\n  functionCalls?: FunctionCall[];\n}"
+        "decl": "export interface ConversationMessage {\n  id?: string;\n  content?: string;\n  role?: MessageRole;\n  createdDate?: string;\n  status?: MessageStatus;\n  /** Files the owner attached to this turn, as the service stored them. */\n  attachments?: Attachment[];\n  /** Client tools this assistant turn asks the CALLER to run — see `FunctionCall`. */\n  functionCalls?: FunctionCall[];\n}"
+      },
+      {
+        "name": "Attachment",
+        "kind": "interface",
+        "jsdoc": "/** A file on a message — the service's `Attachment` entity.\n *\n *  `url` is the service's own REFERENCE to an uploaded file\n *  (`genie-upload://<id>`, see `genieUploadRef`), not a fetchable address: no\n *  route that resolves it to a download url is published, so a client can name a\n *  sent attachment but not show it again from the server's copy. `viewUrl` is\n *  whatever preview the SENDING client chose to store, and is not trusted to\n *  resolve anywhere else. */",
+        "decl": "export interface Attachment {\n  /** Original file name including extension. The service caps it at 255. */\n  fileName: string;\n  /** e.g. `\"image/jpeg\"`. The service caps it at 100. */\n  mimeType: string;\n  url?: string;\n  viewUrl?: string;\n}"
+      },
+      {
+        "name": "CreateFileUploadResponse",
+        "kind": "interface",
+        "jsdoc": "/** The mint of an upload: where to send the bytes, and the record's id. */",
+        "decl": "export interface CreateFileUploadResponse { upload?: { uploadUrl?: string; id?: string } }"
+      },
+      {
+        "name": "CreateFileUploadOptions",
+        "kind": "interface",
+        "jsdoc": "",
+        "decl": "export interface CreateFileUploadOptions {\n  /** The same client-declared scoping flag every other chat-service request\n   *  takes. Omitted unless given — the dashboard sends it only when its own\n   *  account-scoping gate is on. */\n  enforceAccountScopedConversations?: boolean;\n}"
       },
       {
         "name": "FunctionCall",
@@ -16820,7 +16838,7 @@
         "name": "SendMessageOptions",
         "kind": "interface",
         "jsdoc": "/** Optional wire flags on `sendMessage`. `communicationMode` /\n *  `enableRealtimeEvents` were in the original captured payload; only POLLING is\n *  verified end-to-end. The rest were added from the 2026-09-19 re-capture. */",
-        "decl": "export interface SendMessageOptions {\n  communicationMode?: CommunicationMode;\n  enableRealtimeEvents?: boolean;\n  metadata?: UserMessageMetadata;\n  /** The dashboard sends `true`. Optional: verified to answer either way. */\n  enforceAccountScopedConversations?: boolean;\n  /** Tag the turn with the same origin the conversation was created under. */\n  origin?: string;\n}"
+        "decl": "export interface SendMessageOptions {\n  communicationMode?: CommunicationMode;\n  enableRealtimeEvents?: boolean;\n  metadata?: UserMessageMetadata;\n  /** The dashboard sends `true`. Optional: verified to answer either way. */\n  enforceAccountScopedConversations?: boolean;\n  /** Tag the turn with the same origin the conversation was created under. */\n  origin?: string;\n  /** Files already UPLOADED (see `createFileUpload`) to store with the turn.\n   *  Rides step 1 only — the trigger names the stored turn, which carries them. */\n  attachments?: Attachment[];\n}"
       },
       {
         "name": "ConversationUserMessageResponse",
@@ -16870,6 +16888,30 @@
         "jsdoc": "/** Ask the service to abandon the assistant reply it is generating for\n *  `userMessageId` — the \"stop\" a chat surface puts beside a reply in progress.\n *\n *  Addressed by USER message, not by conversation: the thing being abandoned is\n *  one turn, and the id comes from that turn's own send response\n *  (`userMessageIdOf`). There is no route that looks it up afterwards, so a\n *  caller that did not keep it cannot abort.\n *\n *  Resolving means the service ACCEPTED the abort, not that generation had not\n *  already finished — a reply that was already written still lands in the\n *  transcript. Rejecting means the turn is still running: treat it as \"could\n *  not stop\", never as \"stopped\". */",
         "decl": "export function abortAssistantMessageGeneration(userMessageId: string): Promise<AbortAssistantMessageGenerationResponse>;"
       },
+      {
+        "name": "createFileUpload",
+        "kind": "function",
+        "jsdoc": "/** Mint an upload for one file: a pre-signed url to send its bytes to, and the\n *  id the message will reference it by (`genieUploadRef`).\n *\n *  Only the MINT goes through the chat-service; the bytes go straight to\n *  `upload.uploadUrl` (see the file header). Resolving is not proof the file\n *  exists — nothing is stored until those bytes land, so a caller must not\n *  attach the reference before its upload has succeeded. */",
+        "decl": "export function createFileUpload(\n  fileName: string,\n  mimeType: string,\n  opts: CreateFileUploadOptions = {},\n): Promise<CreateFileUploadResponse>;"
+      },
+      {
+        "name": "GENIE_UPLOAD_SCHEME",
+        "kind": "const",
+        "jsdoc": "/** The scheme every first-party creator uses to reference an uploaded file from\n *  a message attachment. */",
+        "decl": "export const GENIE_UPLOAD_SCHEME = \"genie-upload://\";"
+      },
+      {
+        "name": "genieUploadRef",
+        "kind": "function",
+        "jsdoc": "/** `genie-upload://<id>`, or \"\" for no id — never a reference to nothing. */",
+        "decl": "export function genieUploadRef(id: string | undefined): string;"
+      },
+      {
+        "name": "uploadTargetUrl",
+        "kind": "function",
+        "jsdoc": "/** Where the bytes actually go: `uploadUrl` with `path` and `acl=private` set.\n *\n *  Mirrors the Media Platform browser uploader every first-party client relies\n *  on. The service rewrites the storage key itself, so `path` is advisory; it is\n *  sent anyway, for parity with the clients whose uploads are known to work.\n *\n *  String surgery rather than `new URL`, because the worker runtimes (JSContext,\n *  Hermes, QuickJS) do not all ship the URL constructor — and MERGED rather than\n *  appended, because the signed url may already carry a query, and a second `?`\n *  would corrupt the signature it carries. An existing `path` / `acl` is\n *  replaced rather than duplicated; everything else, the fragment included, is\n *  kept byte for byte. */",
+        "decl": "export function uploadTargetUrl(uploadUrl: string, fileName: string): string;"
+      },
       {
         "name": "getConversationMessages",
         "kind": "function",
@@ -16906,6 +16948,12 @@
         "jsdoc": "/** A message's text. `content` is normally a string, but can arrive as an object\n *  carrying `text`; anything else is stringified rather than dropped. */",
         "decl": "export function messageText(m: ConversationMessage | null | undefined): string;"
       },
+      {
+        "name": "attachmentsOf",
+        "kind": "function",
+        "jsdoc": "/** A message's attachments that name a file, in order. Anything that is not an\n *  object with a non-empty `fileName` is dropped rather than rendered as a blank\n *  entry — the list is display-only, so a malformed row has nothing to show. */",
+        "decl": "export function attachmentsOf(m: ConversationMessage | null | undefined): Attachment[];"
+      },
       {
         "name": "lastAssistantMessage",
         "kind": "function",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1029.0",
+  "version": "0.1031.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -65,5 +65,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "785b6d68758b001717f983ccbdad398a5765dced9bf5544af3865811"
+  "falconPackageHash": "b2432c45ff8926fa8325d6f05d7cfaddf683708c33a4537c34b9fa45"
 }