@punica/editor 1.11.0 → 1.11.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@punica/editor",
-  "version": "1.11.0",
+  "version": "1.11.1",
   "description": "Punica Editor",
   "private": false,
   "type": "module",

package/types/punica.module.runtime.fs.d.ts

@@ -16,7 +16,11 @@ declare module 'punica' {
      *
      *  - 'streaming'         : opt-in chunked read/write for large files
      *  - 'binary'            : ranged binary reads via `readBytes` (e.g.
-     *                          Parquet); text-only providers omit this
+     *                          Parquet); text-only providers omit this.
+     *                          READS ONLY — binary WRITE support is not
+     *                          implied, because both shipped hosts declared
+     *                          this flag before either could write bytes.
+     *                          Feature-detect `writeBytes` directly instead
      *  - 'watch'             : path-scoped change notifications
      *  - 'versioning'        : per-path history + time-travel reads
      *  - 'encrypted-at-rest' : payloads stored encrypted by the host
@@ -253,6 +257,17 @@ declare module 'punica' {
         length: number
       ): Promise<ArrayBuffer>;
 
+      /**
+       * Write raw bytes to a workspace file, creating it when absent and
+       * replacing it wholesale when present. Optional/capability-gated:
+       * present on hosts with a binary bridge, absent on text-only providers
+       * — feature-detect with `typeof fs.writeBytes === 'function'` rather
+       * than the `'binary'` flag, which speaks only for reads. Use for
+       * binary content (a pasted screenshot, a copied image) that
+       * `createFileWithContent` would corrupt by encoding it as UTF-8.
+       */
+      writeBytes?(path: string, data: ArrayBuffer): Promise<void>;
+
       /**
        * Create a new file with the given textual content.
        */