dsh-deeppilot 0.9.3 → 0.9.5

package/lib/index.d.ts

@@ -1048,7 +1048,7 @@ interface Config {
     maxConnectionsPerSource?: number;
   };
   /**
-   * Offline push (F-9). `apns` sends directly from the Mac with the user's
+   * Offline push (F-9). `apns` sends directly from the computer with the user's
    * Apple credentials. `relay` sends notify projections to an operator-run
    * relay for distributed builds. The device reports its own APNs environment,
    * so development and TestFlight/App Store devices may coexist.

package/lib/index.js

@@ -6908,6 +6908,25 @@ function projectSessionModels(value) {
 function inProcessRemoteRequest(input, init) {
 	return new Request(new URL(input, "http://localhost/"), init);
 }
+/**
+* Install the Connection service on the resident Client.
+*
+* alpha.3 selects `interactions: 'none'` for any caller that supplies no page
+* location, and that mode forbids the forwarded-event stream this resident
+* client exists to answer. Only the explicit installer can name the
+* participation, so it takes precedence; `apply` stays for a host older than
+* the installer, reading the carrier from the process global set around it.
+*/
+function installResidentConnection(connection, ctx, transport) {
+	if (typeof connection.installConnection === "function") {
+		connection.installConnection(ctx, {
+			transport,
+			interactions: "answer"
+		});
+		return;
+	}
+	connection.apply(ctx);
+}
 let clientFaces;
 /**
 * Load DSH's browser-distributed Client faces into a tiny Host-side module
@@ -6921,6 +6940,19 @@ function pluginModule(value, specifier) {
 	if (typeof value.apply !== "function") throw new Error(`${specifier} has no Client apply() export`);
 	return value;
 }
+/**
+* Register one loaded Client face when the browser banner did not.
+*
+* alpha.3 resolves these specifiers through the `node` export condition to a
+* bundle that exports the face as ordinary ESM and never calls
+* `window.__ModuleLoader__.load`, while earlier hosts only ship the banner
+* shape. A banner registration wins, because it is what the bundle's own
+* internal `require()` calls resolve against; the ESM namespace is the fallback.
+*/
+function adoptClientModule(modules, specifier, loaded) {
+	const id = specifier.replace(/\/client$/, "");
+	if (!modules.has(id)) modules.set(id, loaded);
+}
 async function loadClientFaces() {
 	clientFaces ??= (async () => {
 		const modules = /* @__PURE__ */ new Map([["@deepseek-ai/cordis", Cordis]]);
@@ -6938,7 +6970,7 @@ async function loadClientFaces() {
 				"@deepseek-ai/dsh-typert-registry/client",
 				"@deepseek-ai/dsh-client-connection/client",
 				"@deepseek-ai/dsh-api-gateway/client"
-			]) await import(specifier);
+			]) adoptClientModule(modules, specifier, await import(specifier));
 		} finally {
 			if (previousWindow === void 0) delete loaderGlobal.window;
 			else loaderGlobal.window = previousWindow;
@@ -6964,9 +6996,27 @@ function createAgentScope(ctx, identity) {
 		}
 	});
 }
-function inProcessStream(gateway, endpoint, payload, signal) {
+/**
+* Mint the Peer every in-process carrier call speaks for.
+*
+* alpha.3 requires a Peer on `fetch` and on `wireStream.open`, and refuses a
+* forwarded-event stream unless that Peer declares `interactions: 'answer'`.
+* Its connection service therefore grows `createPeer`, the only entry point
+* that can name the principal and the participation together. Before that the
+* service holds one operator Peer and defaults every absent Peer to it, so that
+* instance is the drop-in answer. A host with neither yields undefined, which
+* only the pre-alpha.3 carrier accepts.
+*/
+function createHostPeer(connection) {
+	if (typeof connection.createPeer === "function") return connection.createPeer({
+		principal: { kind: "owner" },
+		interactions: "answer"
+	});
+	return connection.operator;
+}
+function inProcessStream(gateway, endpoint, payload, signal, peer) {
 	return (async function* () {
-		yield* await gateway.wireStream.open(endpoint, payload, void 0, void 0, signal);
+		yield* await gateway.wireStream.open(endpoint, payload, void 0, peer, signal);
 	})();
 }
 /**
@@ -6983,10 +7033,11 @@ async function startDshRemoteInteractions(hostCtx, handlers) {
 	if (gateway === void 0) throw new Error("DSH typertGateway is unavailable");
 	const faces = await loadClientFaces();
 	const client = new Context();
+	const peer = createHostPeer(connection);
 	const fetchHandler = connection.createSharedFetchHandler("/api");
 	const transport = {
-		fetch: (input, init) => fetchHandler.fetch(inProcessRemoteRequest(input, init)),
-		openStream: (endpoint, payload, signal) => inProcessStream(gateway, endpoint, payload, signal),
+		fetch: (input, init) => fetchHandler.fetch(inProcessRemoteRequest(input, init), peer),
+		openStream: (endpoint, payload, signal) => inProcessStream(gateway, endpoint, payload, signal, peer),
 		ownsHost: true
 	};
 	try {
@@ -6995,7 +7046,7 @@ async function startDshRemoteInteractions(hostCtx, handlers) {
 		const previousTransport = transportGlobal.__DSH_TRANSPORT__;
 		transportGlobal.__DSH_TRANSPORT__ = transport;
 		try {
-			faces.connection.apply(client);
+			installResidentConnection(faces.connection, client, transport);
 		} finally {
 			if (previousTransport === void 0) delete transportGlobal.__DSH_TRANSPORT__;
 			else transportGlobal.__DSH_TRANSPORT__ = previousTransport;
@@ -7066,12 +7117,12 @@ var DshApiProxy = class {
 	* Resolve the optional Schedule service lazily, on every read.
 	*
 	* The bridge is built from a `ctx.inject` on sessionController / connection
-	* / typertGateway, and `schedule` is deliberately NOT in that list: it only
-	* exists when the user enables the optional Automation tasks bundle. On a
-	* DSH 0.2.0 host those three services become ready well before
-	* ScheduleService finishes its own async init, so a value captured here in
-	* the constructor stayed `undefined` for the bridge's whole lifetime and
-	* welcome advertised `schedules=false` even with the bundle mounted.
+	* / typertGateway, and `schedule` is deliberately NOT in that list: it is a
+	* capability the host composition may or may not mount. On a DSH 0.2.0 host
+	* those three services become ready well before ScheduleService finishes its
+	* own async init, so a value captured in the constructor stayed `undefined`
+	* for the bridge's whole lifetime and welcome advertised `schedules=false`
+	* even with the service mounted.
 	*
 	* Once resolved the controller is kept: services are not torn down and
 	* rebuilt underneath a live bridge, so re-resolving per call would be pure
@@ -7182,7 +7233,7 @@ var DshApiProxy = class {
 		rename: async (request) => this.call(() => this.session.rename(request.payload)),
 		cancel: async (request) => this.call(() => this.session.cancel(request.payload)),
 		attachment: async (request) => this.call(() => this.session.attachment(request.payload)),
-		projections: async (request) => this.call(() => this.session.projections(request.payload))
+		projections: async (request) => this.call(() => this.session.projections(request.payload, new AbortController().signal))
 	};
 	workspace = {
 		list: async () => this.call(async () => {