asteroid-odyssey 1.9.167 → 1.9.189

package/dist/index.d.mts

@@ -3014,7 +3014,7 @@ type AgentsWorkflowWorkflowFileTree = {
     variantKeys?: Array<string>;
 };
 /**
- * A single file write in a files patch: upsert the file at `path`. Content is base64 uniformly — structural files decode as UTF-8, agent files are arbitrary bytes — so one write shape carries both.
+ * A single file write in a files patch: upsert the file at `path`. Send the file as `content` or `contentBase64`, exactly one.
  */
 type AgentsWorkflowWorkflowFileWrite = {
     /**
@@ -3022,9 +3022,13 @@ type AgentsWorkflowWorkflowFileWrite = {
      */
     path: string;
     /**
-     * Base64-encoded file content.
+     * The file as UTF-8 text, for text files such as settings.yaml, instructions.md, JSON schemas and scripts. Set this or contentBase64, not both.
      */
-    contentBase64: string;
+    content?: string;
+    /**
+     * The file as base64-encoded bytes, for any file, binary included. Set this or content, not both.
+     */
+    contentBase64?: string;
 };
 /**
  * Request to patch the editable head's file representation. The server classifies each path: structural files re-derive the structured workflow, the agent's own files (memory, uploads, node scripts) go to their blob store. Agent-file writes overlay the head resolved under the edit lock, so a stale baseRev is not rejected. Structural-file writes still require a matching baseRev; a stale value is rejected with 409.

package/dist/index.d.ts

@@ -3014,7 +3014,7 @@ type AgentsWorkflowWorkflowFileTree = {
     variantKeys?: Array<string>;
 };
 /**
- * A single file write in a files patch: upsert the file at `path`. Content is base64 uniformly — structural files decode as UTF-8, agent files are arbitrary bytes — so one write shape carries both.
+ * A single file write in a files patch: upsert the file at `path`. Send the file as `content` or `contentBase64`, exactly one.
  */
 type AgentsWorkflowWorkflowFileWrite = {
     /**
@@ -3022,9 +3022,13 @@ type AgentsWorkflowWorkflowFileWrite = {
      */
     path: string;
     /**
-     * Base64-encoded file content.
+     * The file as UTF-8 text, for text files such as settings.yaml, instructions.md, JSON schemas and scripts. Set this or contentBase64, not both.
      */
-    contentBase64: string;
+    content?: string;
+    /**
+     * The file as base64-encoded bytes, for any file, binary included. Set this or content, not both.
+     */
+    contentBase64?: string;
 };
 /**
  * Request to patch the editable head's file representation. The server classifies each path: structural files re-derive the structured workflow, the agent's own files (memory, uploads, node scripts) go to their blob store. Agent-file writes overlay the head resolved under the edit lock, so a stale baseRev is not rejected. Structural-file writes still require a matching baseRev; a stale value is rejected with 409.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "asteroid-odyssey",
-  "version": "1.9.167",
+  "version": "1.9.189",
   "description": "SDK for interacting with Asteroid Agents API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",