@hyperdrive.bot/paseo-server 0.3.2 → 0.3.4

package/dist/server/extensions/extension-host-manager.d.ts

@@ -1,4 +1,4 @@
-import type { AgentDetail, AgentSummary, ExtensionManifest, HostFetchInit, HostFetchResponse } from "@hyperpaseo/extension-sdk";
+import type { AgentDetail, AgentSummary, ExtensionManifest, HostFetchInit, HostFetchResponse } from "@hyperdrive.bot/paseo-extension-sdk";
 export interface ExtensionHostBackend {
     agents: {
         list(): Promise<AgentSummary[]>;

package/dist/server/extensions/extension-loader.d.ts

@@ -1,4 +1,4 @@
-import { type ExtensionManifest } from "@hyperpaseo/extension-sdk";
+import { type ExtensionManifest } from "@hyperdrive.bot/paseo-extension-sdk";
 export interface DiscoveredExtension {
     dir: string;
     manifestPath: string;

package/dist/server/extensions/extension-loader.js

@@ -9,7 +9,7 @@
 import { readdir, readFile } from "node:fs/promises";
 import { homedir } from "node:os";
 import { isAbsolute, join, resolve } from "node:path";
-import { parseManifest } from "@hyperpaseo/extension-sdk";
+import { parseManifest } from "@hyperdrive.bot/paseo-extension-sdk";
 function resolveMainPath(dir, main) {
     if (!main)
         return undefined;

package/dist/server/server/session.js

@@ -1635,6 +1635,20 @@ export class Session {
                 return this.handleFileUploadBeginRequest(msg);
             case "files.upload.complete.request":
                 return this.handleFileUploadCompleteRequest(msg);
+            case "files.upload.chunk": {
+                // Text transport for chunk bytes (base64 in a JSON message) instead of a binary
+                // FileChunk frame: binary WS frames are dropped by some proxies (the hyperdrive proxy
+                // path), which stalls the client's windowed sender with zero acks. Decode and feed the
+                // decoded bytes through the EXACT SAME queue as the binary path, so write ordering,
+                // backpressure, the per-chunk ack, and the over-cap abort are all identical. The daemon
+                // assigns its own chunkIndex in the ack (msg.payload.chunkIndex is informational only).
+                this.handleFileUploadFrame({
+                    opcode: FileTransferOpcode.FileChunk,
+                    requestId: msg.payload.requestId,
+                    payload: Buffer.from(msg.payload.data, "base64"),
+                });
+                return undefined;
+            }
             case "files.upload.error":
                 // Client already knows about its own abort — clean up without echoing an error back.
                 void this.abortFileUpload(msg.payload.requestId, null);