@hydranium/data-client-theia 1.0.0-next.14 → 1.0.0-next.140

package/lib/node/connection-container-module.d.ts

@@ -24,11 +24,12 @@ import { ContainerModule, type interfaces } from '@theia/core/shared/inversify';
  *
  * **More than one handler is the normal case, not an exotic one.** Theia keys a
  * frontend channel by its service path and refuses a second channel on a path
- * already open, so every frontend abstraction reaching the data head needs its
- * own path and therefore its own handler — a host-neutral `DataPort` beside a
- * Theia `AbstractDataServiceFrontend` is exactly that shape. They still forward
+ * already open, so every frontend abstraction reaching the data head on its own
+ * channel needs its own path and therefore its own handler. They still forward
  * to the SAME data server: the path distinguishes the channel, the shared
- * `portCommand` names the one process behind it.
+ * `portCommand` names the one process behind it. Several participants over ONE
+ * channel need no second handler — that is what `DataConnection`'s sessions are
+ * for, and it is the cheaper arrangement.
  */
 export declare function createDataServerConnectionContainerModule(...handlerClasses: interfaces.Newable<ConnectionHandler>[]): ContainerModule;
 //# sourceMappingURL=connection-container-module.d.ts.map

package/lib/node/connection-container-module.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"connection-container-module.d.ts","sourceRoot":"","sources":["../../src/node/connection-container-module.ts"],"names":[],"mappings":"AAAA;;;;;;;kFAOkF;AAElF,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAEhD,OAAO,EAAE,eAAe,EAAE,KAAK,UAAU,EAAE,MAAM,8BAA8B,CAAC;AAEhF;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,yCAAyC,CAAC,GAAG,cAAc,EAAE,UAAU,CAAC,OAAO,CAAC,iBAAiB,CAAC,EAAE,GAAG,eAAe,CAerI"}
+{"version":3,"file":"connection-container-module.d.ts","sourceRoot":"","sources":["../../src/node/connection-container-module.ts"],"names":[],"mappings":"AAAA;;;;;;;kFAOkF;AAElF,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAEhD,OAAO,EAAE,eAAe,EAAE,KAAK,UAAU,EAAE,MAAM,8BAA8B,CAAC;AAEhF;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,wBAAgB,yCAAyC,CAAC,GAAG,cAAc,EAAE,UAAU,CAAC,OAAO,CAAC,iBAAiB,CAAC,EAAE,GAAG,eAAe,CAerI"}

package/lib/node/connection-container-module.js

@@ -28,11 +28,12 @@ const inversify_1 = require("@theia/core/shared/inversify");
  *
  * **More than one handler is the normal case, not an exotic one.** Theia keys a
  * frontend channel by its service path and refuses a second channel on a path
- * already open, so every frontend abstraction reaching the data head needs its
- * own path and therefore its own handler — a host-neutral `DataPort` beside a
- * Theia `AbstractDataServiceFrontend` is exactly that shape. They still forward
+ * already open, so every frontend abstraction reaching the data head on its own
+ * channel needs its own path and therefore its own handler. They still forward
  * to the SAME data server: the path distinguishes the channel, the shared
- * `portCommand` names the one process behind it.
+ * `portCommand` names the one process behind it. Several participants over ONE
+ * channel need no second handler — that is what `DataConnection`'s sessions are
+ * for, and it is the cheaper arrangement.
  */
 function createDataServerConnectionContainerModule(...handlerClasses) {
     const frontendScopedConnectionModule = connection_container_module_1.ConnectionContainerModule.create(({ bind }) => {

package/lib/node/connection-container-module.js.map

@@ -1 +1 @@
-{"version":3,"file":"connection-container-module.js","sourceRoot":"","sources":["../../src/node/connection-container-module.ts"],"names":[],"mappings":";AAAA;;;;;;;kFAOkF;;AA4BlF,8FAeC;AAzCD,sCAAgD;AAChD,4GAAuG;AACvG,4DAAgF;AAEhF;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,SAAgB,yCAAyC,CAAC,GAAG,cAAuD;IACjH,MAAM,8BAA8B,GAAG,uDAAyB,CAAC,MAAM,CAAC,CAAC,EAAE,IAAI,EAAE,EAAE,EAAE;QAClF,KAAK,MAAM,YAAY,IAAI,cAAc,EAAE,CAAC;YACzC,IAAI,CAAC,YAAY,CAAC,CAAC,MAAM,EAAE,CAAC,gBAAgB,EAAE,CAAC;YAC/C,mEAAmE;YACnE,mEAAmE;YACnE,oEAAoE;YACpE,IAAI,CAAC,wBAAiB,CAAC;iBACnB,cAAc,CAAC,OAAO,CAAC,EAAE,CAAC,OAAO,CAAC,SAAS,CAAC,GAAG,CAAC,YAAY,CAAC,CAAC;iBAC9D,gBAAgB,EAAE,CAAC;QAC1B,CAAC;IACJ,CAAC,CAAC,CAAC;IACH,OAAO,IAAI,2BAAe,CAAC,IAAI,CAAC,EAAE;QAC/B,IAAI,CAAC,uDAAyB,CAAC,CAAC,eAAe,CAAC,8BAA8B,CAAC,CAAC;IACnF,CAAC,CAAC,CAAC;AACN,CAAC"}
+{"version":3,"file":"connection-container-module.js","sourceRoot":"","sources":["../../src/node/connection-container-module.ts"],"names":[],"mappings":";AAAA;;;;;;;kFAOkF;;AA6BlF,8FAeC;AA1CD,sCAAgD;AAChD,4GAAuG;AACvG,4DAAgF;AAEhF;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,SAAgB,yCAAyC,CAAC,GAAG,cAAuD;IACjH,MAAM,8BAA8B,GAAG,uDAAyB,CAAC,MAAM,CAAC,CAAC,EAAE,IAAI,EAAE,EAAE,EAAE;QAClF,KAAK,MAAM,YAAY,IAAI,cAAc,EAAE,CAAC;YACzC,IAAI,CAAC,YAAY,CAAC,CAAC,MAAM,EAAE,CAAC,gBAAgB,EAAE,CAAC;YAC/C,mEAAmE;YACnE,mEAAmE;YACnE,oEAAoE;YACpE,IAAI,CAAC,wBAAiB,CAAC;iBACnB,cAAc,CAAC,OAAO,CAAC,EAAE,CAAC,OAAO,CAAC,SAAS,CAAC,GAAG,CAAC,YAAY,CAAC,CAAC;iBAC9D,gBAAgB,EAAE,CAAC;QAC1B,CAAC;IACJ,CAAC,CAAC,CAAC;IACH,OAAO,IAAI,2BAAe,CAAC,IAAI,CAAC,EAAE;QAC/B,IAAI,CAAC,uDAAyB,CAAC,CAAC,eAAe,CAAC,8BAA8B,CAAC,CAAC;IACnF,CAAC,CAAC,CAAC;AACN,CAAC"}

package/lib/node/data-server-connection-handler.d.ts

@@ -7,7 +7,6 @@
  * SPDX-License-Identifier: MIT
  ********************************************************************************/
 import { AbstractSocketForwardingConnectionHandler } from '@hydranium/client-theia/lib/node';
-import { type Channel, type Disposable } from '@theia/core';
 import type * as net from 'node:net';
 /** Options for {@link DataServerConnectionHandler}. `servicePath` is the Theia
  *  service path the browser frontend opens a channel to; `portCommand` is the
@@ -25,6 +24,16 @@ export interface DataServerConnectionHandlerOptions {
      *  Defaults to the framework `DATA_SERVER_PORT_COMMAND`; override to match
      *  an adopter's established id. */
     readonly portCommand?: string;
+    /**
+     * Product name for the connect-failure dialog this handler raises.
+     *
+     * It reaches the adopter's UI verbatim, so the framework default leaks a
+     * framework noun into a product that is not ours. Not a translation concern —
+     * routing it through a catalogue would ask an adopter to "translate" English
+     * into their own product name, and would make their branding
+     * locale-dependent.
+     */
+    readonly serverName?: string;
     readonly findPortTimeout?: number;
     readonly findPortAttempts?: number;
     readonly connectTimeoutMs?: number;
@@ -41,16 +50,12 @@ export interface DataServerConnectionHandlerOptions {
  * Bridges a Theia browser-frontend channel to a data-server's TCP socket — the
  * backend half of the data-server head's transport.
  *
- * The port-discovery + buffer-and-replay race fix + connect orchestration live
- * on the cross-head {@link AbstractSocketForwardingConnectionHandler} base; this
- * subclass supplies only the data-server defaults (service path / port command /
- * log labels) and plugs in {@link SocketChannelForwarder} as the byte relay —
- * its own forwarder, so the data head carries no GLSP dependency. Sibling of
- * `@hydranium/glsp-client-theia`'s `GlspServerConnectionHandler`, which
- * subclasses the same base with `@eclipse-glsp`'s `SocketConnectionForwarder`.
+ * The port discovery, the buffer-and-replay race fix, the connect orchestration
+ * and the byte forwarder live on the cross-head
+ * {@link AbstractSocketForwardingConnectionHandler} base; this subclass supplies
+ * only the data-server defaults (service path / port command / log labels).
  */
 export declare class DataServerConnectionHandler extends AbstractSocketForwardingConnectionHandler {
     constructor(options?: DataServerConnectionHandlerOptions);
-    protected forwardToSocketConnection(clientChannel: Channel, socket: net.Socket): Disposable;
 }
 //# sourceMappingURL=data-server-connection-handler.d.ts.map

package/lib/node/data-server-connection-handler.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"data-server-connection-handler.d.ts","sourceRoot":"","sources":["../../src/node/data-server-connection-handler.ts"],"names":[],"mappings":"AAAA;;;;;;;kFAOkF;AAElF,OAAO,EAAE,yCAAyC,EAAE,MAAM,kCAAkC,CAAC;AAE7F,OAAO,EAAE,KAAK,OAAO,EAAE,KAAK,UAAU,EAAE,MAAM,aAAa,CAAC;AAE5D,OAAO,KAAK,KAAK,GAAG,MAAM,UAAU,CAAC;AAGrC;;;;kBAIkB;AAClB,MAAM,WAAW,kCAAkC;IAChD;;;;yDAIqD;IACrD,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B;;uCAEmC;IACnC,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,eAAe,CAAC,EAAE,MAAM,CAAC;IAClC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAC;IACnC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAC;IACnC;;;;;;OAMG;IACH,QAAQ,CAAC,eAAe,CAAC,EAAE,CAAC,MAAM,EAAE,GAAG,CAAC,MAAM,KAAK,IAAI,CAAC;CAC1D;AAED;;;;;;;;;;;GAWG;AACH,qBACa,2BAA4B,SAAQ,yCAAyC;gBAC9D,OAAO,GAAE,kCAAuC;IAazE,SAAS,CAAC,yBAAyB,CAAC,aAAa,EAAE,OAAO,EAAE,MAAM,EAAE,GAAG,CAAC,MAAM,GAAG,UAAU;CAG7F"}
+{"version":3,"file":"data-server-connection-handler.d.ts","sourceRoot":"","sources":["../../src/node/data-server-connection-handler.ts"],"names":[],"mappings":"AAAA;;;;;;;kFAOkF;AAElF,OAAO,EAAE,yCAAyC,EAAE,MAAM,kCAAkC,CAAC;AAG7F,OAAO,KAAK,KAAK,GAAG,MAAM,UAAU,CAAC;AAErC;;;;kBAIkB;AAClB,MAAM,WAAW,kCAAkC;IAChD;;;;yDAIqD;IACrD,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B;;uCAEmC;IACnC,QAAQ,CAAC,WAAW,CAAC,EAAE,MAAM,CAAC;IAC9B;;;;;;;;OAQG;IACH,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,eAAe,CAAC,EAAE,MAAM,CAAC;IAClC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAC;IACnC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAC;IACnC;;;;;;OAMG;IACH,QAAQ,CAAC,eAAe,CAAC,EAAE,CAAC,MAAM,EAAE,GAAG,CAAC,MAAM,KAAK,IAAI,CAAC;CAC1D;AAED;;;;;;;;GAQG;AACH,qBACa,2BAA4B,SAAQ,yCAAyC;gBAC9D,OAAO,GAAE,kCAAuC;CAY3E"}

package/lib/node/data-server-connection-handler.js

@@ -24,18 +24,14 @@ exports.DataServerConnectionHandler = void 0;
 const node_1 = require("@hydranium/client-theia/lib/node");
 const protocol_1 = require("@hydranium/protocol");
 const inversify_1 = require("@theia/core/shared/inversify");
-const socket_channel_forwarder_1 = require("./socket-channel-forwarder");
 /**
  * Bridges a Theia browser-frontend channel to a data-server's TCP socket — the
  * backend half of the data-server head's transport.
  *
- * The port-discovery + buffer-and-replay race fix + connect orchestration live
- * on the cross-head {@link AbstractSocketForwardingConnectionHandler} base; this
- * subclass supplies only the data-server defaults (service path / port command /
- * log labels) and plugs in {@link SocketChannelForwarder} as the byte relay —
- * its own forwarder, so the data head carries no GLSP dependency. Sibling of
- * `@hydranium/glsp-client-theia`'s `GlspServerConnectionHandler`, which
- * subclasses the same base with `@eclipse-glsp`'s `SocketConnectionForwarder`.
+ * The port discovery, the buffer-and-replay race fix, the connect orchestration
+ * and the byte forwarder live on the cross-head
+ * {@link AbstractSocketForwardingConnectionHandler} base; this subclass supplies
+ * only the data-server defaults (service path / port command / log labels).
  */
 let DataServerConnectionHandler = class DataServerConnectionHandler extends node_1.AbstractSocketForwardingConnectionHandler {
     constructor(options = {}) {
@@ -43,16 +39,13 @@ let DataServerConnectionHandler = class DataServerConnectionHandler extends node
             path: options.servicePath ?? protocol_1.DATA_SERVER_PATH,
             portCommand: options.portCommand ?? protocol_1.DATA_SERVER_PORT_COMMAND,
             logComponent: 'DataServer',
-            serverName: 'Model Server',
+            serverName: options.serverName ?? 'Model Server',
             findPortTimeout: options.findPortTimeout,
             findPortAttempts: options.findPortAttempts,
             connectTimeoutMs: options.connectTimeoutMs,
             onSocketCreated: options.onSocketCreated
         });
     }
-    forwardToSocketConnection(clientChannel, socket) {
-        return new socket_channel_forwarder_1.SocketChannelForwarder(clientChannel, socket);
-    }
 };
 exports.DataServerConnectionHandler = DataServerConnectionHandler;
 exports.DataServerConnectionHandler = DataServerConnectionHandler = __decorate([

package/lib/node/data-server-connection-handler.js.map

@@ -1 +1 @@
-{"version":3,"file":"data-server-connection-handler.js","sourceRoot":"","sources":["../../src/node/data-server-connection-handler.ts"],"names":[],"mappings":";AAAA;;;;;;;kFAOkF;;;;;;;;;;;;;;;AAElF,2DAA6F;AAC7F,kDAAiF;AAEjF,4DAAqE;AAErE,yEAAoE;AA+BpE;;;;;;;;;;;GAWG;AAEI,IAAM,2BAA2B,GAAjC,MAAM,2BAA4B,SAAQ,gDAAyC;IACvF,YAAyB,UAA8C,EAAE;QACtE,KAAK,CAAC;YACH,IAAI,EAAE,OAAO,CAAC,WAAW,IAAI,2BAAgB;YAC7C,WAAW,EAAE,OAAO,CAAC,WAAW,IAAI,mCAAwB;YAC5D,YAAY,EAAE,YAAY;YAC1B,UAAU,EAAE,cAAc;YAC1B,eAAe,EAAE,OAAO,CAAC,eAAe;YACxC,gBAAgB,EAAE,OAAO,CAAC,gBAAgB;YAC1C,gBAAgB,EAAE,OAAO,CAAC,gBAAgB;YAC1C,eAAe,EAAE,OAAO,CAAC,eAAe;SAC1C,CAAC,CAAC;IACN,CAAC;IAES,yBAAyB,CAAC,aAAsB,EAAE,MAAkB;QAC3E,OAAO,IAAI,iDAAsB,CAAC,aAAa,EAAE,MAAM,CAAC,CAAC;IAC5D,CAAC;CACH,CAAA;AAjBY,kEAA2B;sCAA3B,2BAA2B;IADvC,IAAA,sBAAU,GAAE;IAEG,WAAA,IAAA,qBAAS,GAAE,CAAA;;GADd,2BAA2B,CAiBvC"}
+{"version":3,"file":"data-server-connection-handler.js","sourceRoot":"","sources":["../../src/node/data-server-connection-handler.ts"],"names":[],"mappings":";AAAA;;;;;;;kFAOkF;;;;;;;;;;;;;;;AAElF,2DAA6F;AAC7F,kDAAiF;AACjF,4DAAqE;AA0CrE;;;;;;;;GAQG;AAEI,IAAM,2BAA2B,GAAjC,MAAM,2BAA4B,SAAQ,gDAAyC;IACvF,YAAyB,UAA8C,EAAE;QACtE,KAAK,CAAC;YACH,IAAI,EAAE,OAAO,CAAC,WAAW,IAAI,2BAAgB;YAC7C,WAAW,EAAE,OAAO,CAAC,WAAW,IAAI,mCAAwB;YAC5D,YAAY,EAAE,YAAY;YAC1B,UAAU,EAAE,OAAO,CAAC,UAAU,IAAI,cAAc;YAChD,eAAe,EAAE,OAAO,CAAC,eAAe;YACxC,gBAAgB,EAAE,OAAO,CAAC,gBAAgB;YAC1C,gBAAgB,EAAE,OAAO,CAAC,gBAAgB;YAC1C,eAAe,EAAE,OAAO,CAAC,eAAe;SAC1C,CAAC,CAAC;IACN,CAAC;CACH,CAAA;AAbY,kEAA2B;sCAA3B,2BAA2B;IADvC,IAAA,sBAAU,GAAE;IAEG,WAAA,IAAA,qBAAS,GAAE,CAAA;;GADd,2BAA2B,CAavC"}

package/lib/node/index.d.ts

@@ -9,5 +9,4 @@
 export * from './connection-container-module';
 export * from './data-server-connection-handler';
 export * from './host-diagnostics-server';
-export * from './socket-channel-forwarder';
 //# sourceMappingURL=index.d.ts.map

package/lib/node/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/node/index.ts"],"names":[],"mappings":"AAAA;;;;;;;kFAOkF;AAElF,cAAc,+BAA+B,CAAC;AAC9C,cAAc,kCAAkC,CAAC;AACjD,cAAc,2BAA2B,CAAC;AAC1C,cAAc,4BAA4B,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/node/index.ts"],"names":[],"mappings":"AAAA;;;;;;;kFAOkF;AAElF,cAAc,+BAA+B,CAAC;AAC9C,cAAc,kCAAkC,CAAC;AACjD,cAAc,2BAA2B,CAAC"}

package/lib/node/index.js

@@ -25,5 +25,4 @@ Object.defineProperty(exports, "__esModule", { value: true });
 __exportStar(require("./connection-container-module"), exports);
 __exportStar(require("./data-server-connection-handler"), exports);
 __exportStar(require("./host-diagnostics-server"), exports);
-__exportStar(require("./socket-channel-forwarder"), exports);
 //# sourceMappingURL=index.js.map

package/lib/node/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/node/index.ts"],"names":[],"mappings":";AAAA;;;;;;;kFAOkF;;;;;;;;;;;;;;;;AAElF,gEAA8C;AAC9C,mEAAiD;AACjD,4DAA0C;AAC1C,6DAA2C"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/node/index.ts"],"names":[],"mappings":";AAAA;;;;;;;kFAOkF;;;;;;;;;;;;;;;;AAElF,gEAA8C;AAC9C,mEAAiD;AACjD,4DAA0C"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hydranium/data-client-theia",
-  "version": "1.0.0-next.14",
+  "version": "1.0.0-next.140",
   "description": "Theia-coupled client primitives for the hydranium data-server protocol head; companion of @hydranium/data-server. Bridges framework typed errors (e.g. ConflictError) across Theia's RPC boundary so their code + data survive the wire.",
   "keywords": [
     "hydranium",
@@ -70,11 +70,11 @@
     "watch": "tsc -b -w --preserveWatchOutput"
   },
   "devDependencies": {
-    "@hydranium/client-theia": "1.0.0-next.14",
-    "@hydranium/core": "1.0.0-next.14",
-    "@hydranium/protocol": "1.0.0-next.14",
-    "@theia/core": "^1.71.0",
-    "@theia/workspace": "^1.71.0",
+    "@hydranium/client-theia": "1.0.0-next.140",
+    "@hydranium/core": "1.0.0-next.140",
+    "@hydranium/protocol": "1.0.0-next.140",
+    "@theia/core": "^1.70.0",
+    "@theia/workspace": "^1.70.0",
     "@types/node": "^22.0.0",
     "inversify": "6.2.2",
     "reflect-metadata": "0.2.2",
@@ -83,13 +83,13 @@
     "vscode-jsonrpc": "9.0.1"
   },
   "peerDependencies": {
-    "@hydranium/client-theia": "1.0.0-next.14",
-    "@hydranium/core": "1.0.0-next.14",
-    "@hydranium/protocol": "1.0.0-next.14",
-    "@theia/core": "^1.71.0",
-    "@theia/workspace": "^1.71.0",
+    "@hydranium/client-theia": "1.0.0-next.140",
+    "@hydranium/core": "1.0.0-next.140",
+    "@hydranium/protocol": "1.0.0-next.140",
+    "@theia/core": "^1.70.0",
+    "@theia/workspace": "^1.70.0",
     "inversify": "^6.0.0",
-    "vscode-jsonrpc": "^8.0.0 || ^9.0.0"
+    "vscode-jsonrpc": "9.0.1"
   },
   "engines": {
     "node": ">=22.13"
@@ -97,5 +97,6 @@
   "publishConfig": {
     "access": "public"
   },
+  "//peerDependencies": "`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.",
   "//prepack": "The publish guard, and it deliberately is NOT a `prepare`: npm runs a workspace `prepare` BEFORE the root `postinstall` that applies patches/vscode-jsonrpc+9.0.1.patch, so building there fails on a cold clone and npm rolls the entire install back. `prepack` runs only when a tarball is made (`npm pack`, `npm publish`) and never on install, so it cannot break the install it has no business touching. It FAILS rather than rebuilds, because the rebuild is exactly the part that ordering defeats. What it defends against: `files` lists `lib`, `lib` is gitignored, and a `files` entry matching nothing is skipped SILENTLY — so `npm publish` from an unbuilt tree emits a tarball of `src` and nothing else, with no error."
 }

package/src/browser/channel-connection.ts

@@ -199,8 +199,8 @@ export interface ChannelConnectionHandle {
    /**
     * The current connection. Read it per use rather than caching it: after a
     * reconnect this returns a NEW promise, and a cached one resolves to the
-    * dead connection forever. The same reasoning makes
-    * `AbstractDataServiceFrontend` rebuild its proxy rather than hold one.
+    * dead connection forever. The same reasoning makes `RpcConnection` rebuild
+    * its proxy per generation rather than hold one.
     */
    readonly current: Promise<MessageConnection>;
 

package/src/browser/channel-data-port.ts

@@ -0,0 +1,100 @@
+/********************************************************************************
+ * Copyright (c) 2026 EclipseSource and others.
+ *
+ * This program and the accompanying materials are made available under the
+ * terms of the MIT License which is available in the project root.
+ *
+ * SPDX-License-Identifier: MIT
+ ********************************************************************************/
+
+import { renderFrameworkMessage, type DataPort, type ResolvedMessage } from '@hydranium/protocol';
+import { Emitter, MessageService, nls, type Event } from '@theia/core';
+import { type ServiceConnectionProvider } from '@theia/core/lib/browser';
+import { RemoteConnectionProvider } from '@theia/core/lib/browser/messaging/service-connection-provider';
+import { inject, injectable } from '@theia/core/shared/inversify';
+import { WorkspaceService } from '@theia/workspace/lib/browser';
+import type { MessageConnection } from 'vscode-jsonrpc';
+import { type ChannelConnectionHandle, openChannelConnection } from './channel-connection';
+import { whenWorkspaceOpen } from './workspace-gate';
+
+/**
+ * A {@link DataPort} over a Theia frontend channel.
+ *
+ * Subclasses supply {@link servicePath}; everything above the port —
+ * `DataConnection`, its sessions, and whatever model a widget drives — is
+ * host-neutral and shared with the VS Code and browser shells.
+ *
+ * Bind one per service path and in singleton scope. Theia keys a frontend
+ * channel by its path and refuses a second on a path already open, and the
+ * throw escapes the `openChannelConnection` the loser is awaiting, leaving that
+ * promise unsettled rather than rejected.
+ */
+@injectable()
+export abstract class ChannelDataPort implements DataPort {
+   @inject(RemoteConnectionProvider) protected readonly connectionProvider!: ServiceConnectionProvider;
+   @inject(WorkspaceService) protected readonly workspaceService!: WorkspaceService;
+   @inject(MessageService) protected readonly messageService!: MessageService;
+
+   /** Frontend service path the backend forwarder for this head is registered under. */
+   protected abstract readonly servicePath: string;
+
+   /**
+    * Re-open the channel when the current connection is lost. Default `true` —
+    * re-opening is the only thing that recovers a restarted language server,
+    * which binds new ephemeral ports. Turn it off for a frontend that tears
+    * itself down on transport loss instead.
+    */
+   protected readonly reconnectOnConnectionLoss: boolean = true;
+
+   protected readonly disposeEmitter = new Emitter<void>();
+   readonly onDispose: Event<void> = this.disposeEmitter.event;
+
+   protected handle?: ChannelConnectionHandle;
+
+   /**
+    * Open the workspace-gated channel and hand back its listening connection.
+    *
+    * Gated because the backend forwarder discovers the head's port by executing
+    * a command the language server answers, and the language server only
+    * launches once there is a workspace to launch it for. Asking earlier polls
+    * a command nobody has registered.
+    */
+   connect(): Promise<MessageConnection> {
+      // Read per call rather than cached: `current` is repointed at a fresh
+      // promise every time the channel is re-opened, so reading through the
+      // handle is what makes a later generation reach the live server.
+      if (!this.handle) {
+         this.handle = openChannelConnection(this.connectionProvider, this.servicePath, {
+            whenReady: whenWorkspaceOpen(this.workspaceService),
+            reconnect: this.reconnectOnConnectionLoss
+         });
+         // A relaunched server binds new ephemeral ports; the handle re-opens
+         // and the forwarder rediscovers, but `DataConnection` caches its
+         // generation and would go on addressing the dead one. Its signal to
+         // drop that generation is this event.
+         this.handle.onDidLoseConnection(() => this.disposeEmitter.fire(undefined));
+      }
+      return this.handle.current;
+   }
+
+   /**
+    * Surface a transport or write failure as a Theia notification.
+    *
+    * Swallowing it is the failure this exists to prevent: a dead connection and
+    * an empty document are indistinguishable in a widget.
+    *
+    * `reported` is already a complete sentence with the detail interpolated, so
+    * wrapping it in a sentence of the host's own would nest one owner's clause
+    * inside another's and leave no translator in control of the whole.
+    */
+   reportError(_error: unknown, reported: ResolvedMessage): void {
+      this.messageService.error(renderFrameworkMessage(reported, nls.localization?.translations));
+   }
+
+   dispose(): void {
+      this.handle?.dispose();
+      this.handle = undefined;
+      this.disposeEmitter.fire(undefined);
+      this.disposeEmitter.dispose();
+   }
+}

package/src/browser/data-session-stop-contribution.ts

@@ -0,0 +1,117 @@
+/********************************************************************************
+ * Copyright (c) 2026 CrossBreeze, EclipseSource and others.
+ *
+ * This program and the accompanying materials are made available under the
+ * terms of the MIT License which is available in the project root.
+ *
+ * SPDX-License-Identifier: MIT
+ ********************************************************************************/
+
+import type { DataConnection, DataServerProtocol, DataSession, DiagnosticOf, TransferElement } from '@hydranium/protocol';
+// Type-only: the `@theia/core/lib/browser` barrel touches DOM globals at module
+// load, which the node-environment unit tests cannot provide.
+import type { FrontendApplicationContribution, OnWillStopAction } from '@theia/core/lib/browser';
+import { injectable } from '@theia/core/shared/inversify';
+
+/**
+ * Ends a Theia frontend's data sessions with its page, and holds the page
+ * while one of them is still saving. Bind it as a
+ * `FrontendApplicationContribution` in singleton scope and {@link track} each
+ * data connection the frontend binds, once.
+ *
+ * **Stop.** {@link onStop} disposes every tracked session, which sends its
+ * `closeSession`, so the server ends it as closed: each document it was the
+ * last to hold reverts at once. Otherwise the server learns of the page only
+ * when its connection goes, which Theia may hold open for its reconnect
+ * timeout, and then ends the sessions as lost, so their documents wait out the
+ * revert grace. The close is best effort: under load the page's last frames
+ * can be lost on the way, and the server then ends the sessions as lost. A
+ * session with calls still in flight at the stop closes after them, which is
+ * too late for a page going away, and is left to the server's connection-close
+ * cleanup. A call a session makes in the same tick as the stop is refused and
+ * never sent.
+ *
+ * **Veto.** While a tracked session has a save in flight, {@link onWillStop}
+ * vetoes, including a session disposed meanwhile. In Electron, Theia awaits
+ * the veto's action, which waits for the saves to answer, a save started during
+ * the wait included, up to {@link maxSettlePasses} times. The browser runs no
+ * action before unload, so there the veto shows the leave-page prompt and
+ * nothing more. Theia ignores every veto under
+ * `application.confirmExit: 'never'`, so there a save in flight at the stop
+ * may be cut off.
+ */
+@injectable()
+export class DataSessionStopContribution implements FrontendApplicationContribution {
+   /** The sessions to end at the stop, and to wait for while they save. */
+   protected readonly sessions = new Set<DataSession<TransferElement>>();
+   /**
+    * How many times the veto's action waits for the saves in flight before it
+    * lets the stop go. Each wait ends by the session's own bound, so a save
+    * that never answers holds the stop for a few bounds, not for good.
+    */
+   protected readonly maxSettlePasses: number = 3;
+
+   /**
+    * Take every session of `connection` into the stop: the ones it has
+    * started already, and each one it starts from now on. Generic, so a
+    * connection of any transfer root, server and client fits.
+    */
+   track<TTransfer extends TransferElement, TServer extends DataServerProtocol<TTransfer, DiagnosticOf<TServer>>, TClient extends object>(
+      connection: DataConnection<TTransfer, TServer, TClient>
+   ): void {
+      connection.liveSessions.forEach(session => this.trackSession(session));
+      connection.onDidCreateSession(session => this.trackSession(session));
+   }
+
+   /**
+    * Take `session` into the stop. It leaves once it has ended and its saves
+    * have answered, so a session disposed with a save in flight still holds
+    * the page.
+    */
+   protected trackSession(session: DataSession<TransferElement>): void {
+      this.sessions.add(session);
+      // A save can outlast the wait's bound, so the session stays until none
+      // is left in flight.
+      const release = (): void =>
+         void session.whenSavesSettled().then(() => (session.hasSavesInFlight ? release() : this.sessions.delete(session)));
+      // An ended session has fired its event already, and never fires it again.
+      if (session.isDisposed) {
+         release();
+      } else {
+         session.onDidDispose(release);
+      }
+   }
+
+   onWillStop(): OnWillStopAction | undefined {
+      if (this.savingSessions().length === 0) {
+         return undefined;
+      }
+      return {
+         // Theia logs the reason and shows it nowhere, so it is not translated.
+         reason: 'Data sessions are saving',
+         action: async () => {
+            // The page stays usable while Theia awaits this, so a save can
+            // start during a wait; each pass waits for the saves then in flight.
+            for (let pass = 0; pass < this.maxSettlePasses; pass++) {
+               const saving = this.savingSessions();
+               if (saving.length === 0) {
+                  break;
+               }
+               await Promise.all(saving.map(session => session.whenSavesSettled()));
+            }
+            return true;
+         }
+      };
+   }
+
+   /** The tracked sessions with a save in flight. */
+   protected savingSessions(): DataSession<TransferElement>[] {
+      return [...this.sessions].filter(session => session.hasSavesInFlight);
+   }
+
+   onStop(): void {
+      for (const session of this.sessions) {
+         session.dispose();
+      }
+   }
+}

package/src/browser/index.ts

@@ -8,8 +8,7 @@
  ********************************************************************************/
 
 export * from './channel-connection';
-export * from './data-service-frontend';
-export * from './diagnostics-data-service-frontend';
+export * from './channel-data-port';
+export * from './data-session-stop-contribution';
 export * from './host-diagnostics-frontend';
-export * from './references-data-service-frontend';
 export * from './workspace-gate';

package/src/common/emitter-data-client.ts

@@ -12,7 +12,10 @@ import type {
    Project,
    ProjectsChangedEvent,
    TransferDiagnostic,
+   TransferDocumentDeletedEvent,
+   TransferDocumentDirtyChangedEvent,
    TransferDocumentSavedEvent,
+   TransferDocumentsBuiltEvent,
    TransferDocumentUpdatedEvent,
    TransferElement
 } from '@hydranium/protocol';
@@ -46,6 +49,18 @@ export class EmitterDataClient<
    /** Fires for each inbound {@link onDocumentSaved} notification. */
    readonly onDidSaveDocument: Event<TransferDocumentSavedEvent<TTransfer, TDiagnostic>> = this.onDocumentSavedEmitter.event;
 
+   protected readonly onDocumentDirtyChangedEmitter = new Emitter<TransferDocumentDirtyChangedEvent>();
+   /** Fires for each inbound {@link onDocumentDirtyChanged} notification. */
+   readonly onDidChangeDocumentDirty: Event<TransferDocumentDirtyChangedEvent> = this.onDocumentDirtyChangedEmitter.event;
+
+   protected readonly onDocumentDeletedEmitter = new Emitter<TransferDocumentDeletedEvent>();
+   /** Fires for each inbound {@link onDocumentDeleted} notification. */
+   readonly onDidDeleteDocument: Event<TransferDocumentDeletedEvent> = this.onDocumentDeletedEmitter.event;
+
+   protected readonly onDocumentsBuiltEmitter = new Emitter<TransferDocumentsBuiltEvent>();
+   /** Fires for each inbound {@link onDocumentsBuilt} notification. */
+   readonly onDidBuildDocuments: Event<TransferDocumentsBuiltEvent> = this.onDocumentsBuiltEmitter.event;
+
    protected readonly onProjectsChangedEmitter = new Emitter<ProjectsChangedEvent<TProject>>();
    /** Fires for each inbound {@link onProjectsChanged} notification. */
    readonly onDidChangeProjects: Event<ProjectsChangedEvent<TProject>> = this.onProjectsChangedEmitter.event;
@@ -58,6 +73,18 @@ export class EmitterDataClient<
       this.onDocumentSavedEmitter.fire(event);
    }
 
+   onDocumentDirtyChanged(event: TransferDocumentDirtyChangedEvent): void {
+      this.onDocumentDirtyChangedEmitter.fire(event);
+   }
+
+   onDocumentDeleted(event: TransferDocumentDeletedEvent): void {
+      this.onDocumentDeletedEmitter.fire(event);
+   }
+
+   onDocumentsBuilt(event: TransferDocumentsBuiltEvent): void {
+      this.onDocumentsBuiltEmitter.fire(event);
+   }
+
    onProjectsChanged(event: ProjectsChangedEvent<TProject>): void {
       this.onProjectsChangedEmitter.fire(event);
    }

package/src/node/connection-container-module.ts

@@ -27,11 +27,12 @@ import { ContainerModule, type interfaces } from '@theia/core/shared/inversify';
  *
  * **More than one handler is the normal case, not an exotic one.** Theia keys a
  * frontend channel by its service path and refuses a second channel on a path
- * already open, so every frontend abstraction reaching the data head needs its
- * own path and therefore its own handler — a host-neutral `DataPort` beside a
- * Theia `AbstractDataServiceFrontend` is exactly that shape. They still forward
+ * already open, so every frontend abstraction reaching the data head on its own
+ * channel needs its own path and therefore its own handler. They still forward
  * to the SAME data server: the path distinguishes the channel, the shared
- * `portCommand` names the one process behind it.
+ * `portCommand` names the one process behind it. Several participants over ONE
+ * channel need no second handler — that is what `DataConnection`'s sessions are
+ * for, and it is the cheaper arrangement.
  */
 export function createDataServerConnectionContainerModule(...handlerClasses: interfaces.Newable<ConnectionHandler>[]): ContainerModule {
    const frontendScopedConnectionModule = ConnectionContainerModule.create(({ bind }) => {

package/src/node/data-server-connection-handler.ts

@@ -9,10 +9,8 @@
 
 import { AbstractSocketForwardingConnectionHandler } from '@hydranium/client-theia/lib/node';
 import { DATA_SERVER_PATH, DATA_SERVER_PORT_COMMAND } from '@hydranium/protocol';
-import { type Channel, type Disposable } from '@theia/core';
 import { injectable, unmanaged } from '@theia/core/shared/inversify';
 import type * as net from 'node:net';
-import { SocketChannelForwarder } from './socket-channel-forwarder';
 
 /** Options for {@link DataServerConnectionHandler}. `servicePath` is the Theia
  *  service path the browser frontend opens a channel to; `portCommand` is the
@@ -30,6 +28,16 @@ export interface DataServerConnectionHandlerOptions {
     *  Defaults to the framework `DATA_SERVER_PORT_COMMAND`; override to match
     *  an adopter's established id. */
    readonly portCommand?: string;
+   /**
+    * Product name for the connect-failure dialog this handler raises.
+    *
+    * It reaches the adopter's UI verbatim, so the framework default leaks a
+    * framework noun into a product that is not ours. Not a translation concern —
+    * routing it through a catalogue would ask an adopter to "translate" English
+    * into their own product name, and would make their branding
+    * locale-dependent.
+    */
+   readonly serverName?: string;
    readonly findPortTimeout?: number;
    readonly findPortAttempts?: number;
    readonly connectTimeoutMs?: number;
@@ -47,13 +55,10 @@ export interface DataServerConnectionHandlerOptions {
  * Bridges a Theia browser-frontend channel to a data-server's TCP socket — the
  * backend half of the data-server head's transport.
  *
- * The port-discovery + buffer-and-replay race fix + connect orchestration live
- * on the cross-head {@link AbstractSocketForwardingConnectionHandler} base; this
- * subclass supplies only the data-server defaults (service path / port command /
- * log labels) and plugs in {@link SocketChannelForwarder} as the byte relay —
- * its own forwarder, so the data head carries no GLSP dependency. Sibling of
- * `@hydranium/glsp-client-theia`'s `GlspServerConnectionHandler`, which
- * subclasses the same base with `@eclipse-glsp`'s `SocketConnectionForwarder`.
+ * The port discovery, the buffer-and-replay race fix, the connect orchestration
+ * and the byte forwarder live on the cross-head
+ * {@link AbstractSocketForwardingConnectionHandler} base; this subclass supplies
+ * only the data-server defaults (service path / port command / log labels).
  */
 @injectable()
 export class DataServerConnectionHandler extends AbstractSocketForwardingConnectionHandler {
@@ -62,15 +67,11 @@ export class DataServerConnectionHandler extends AbstractSocketForwardingConnect
          path: options.servicePath ?? DATA_SERVER_PATH,
          portCommand: options.portCommand ?? DATA_SERVER_PORT_COMMAND,
          logComponent: 'DataServer',
-         serverName: 'Model Server',
+         serverName: options.serverName ?? 'Model Server',
          findPortTimeout: options.findPortTimeout,
          findPortAttempts: options.findPortAttempts,
          connectTimeoutMs: options.connectTimeoutMs,
          onSocketCreated: options.onSocketCreated
       });
    }
-
-   protected forwardToSocketConnection(clientChannel: Channel, socket: net.Socket): Disposable {
-      return new SocketChannelForwarder(clientChannel, socket);
-   }
 }

package/src/node/index.ts

@@ -10,4 +10,3 @@
 export * from './connection-container-module';
 export * from './data-server-connection-handler';
 export * from './host-diagnostics-server';
-export * from './socket-channel-forwarder';