@cplieger/web-terminal-engine 3.3.0 → 3.4.2

package/jsr.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-engine",
-  "version": "3.3.0",
+  "version": "3.4.2",
   "exports": {
     ".": "./src/index.ts"
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-engine",
-  "version": "3.3.0",
+  "version": "3.4.2",
   "type": "module",
   "scripts": {
     "typecheck": "tsc -p tsconfig.json",
@@ -11,7 +11,7 @@
   "devDependencies": {
     "@cplieger/web-terminal-engine-v3": "npm:@cplieger/web-terminal-engine@2.8.0",
     "@eslint/js": "10.0.1",
-    "@playwright/test": "1.62.0",
+    "@playwright/test": "1.62.1",
     "@stryker-mutator/core": "9.6.1",
     "@stryker-mutator/typescript-checker": "9.6.1",
     "@stryker-mutator/vitest-runner": "9.6.1",

package/src/types.ts

@@ -115,7 +115,7 @@ export interface ResumeAckMessage {
    * `onWireVersionMismatch` so the UI can offer a reload. Versions inside
    * the range are normal pairings (a v3 server just means the socket stays
    * in sentinel mode); a value >= 4 additionally triggers the typed-framing
-   * upgrade (docs/wire-v4-typed-framing.md).
+   * upgrade (see WIRE_PROTOCOL_VERSION in wire-compatibility.ts).
    */
   serverWireVersion?: number;
   /**
@@ -232,7 +232,8 @@ export type ControlMessage =
     }
   | { type: "ping" }
   /**
-   * v4 typed-framing transition (docs/wire-v4-typed-framing.md §4): the first
+   * v4 typed-framing transition (see WIRE_PROTOCOL_VERSION in
+   * wire-compatibility.ts): the first
    * TEXT message a client sends after the resumeAck proves the server speaks
    * wire revision >= 4. Receiving it latches the server's connection to typed
    * mode (text = control, binary = full-alphabet PTY input); otherwise a no-op.

package/src/wire.ts

@@ -13,7 +13,7 @@
 // in v3 mode (sendInputFrames splits leading NULs into solitary frames), so
 // in practice the reserved channel only ever carries real controls.
 //
-// v4 framing (docs/wire-v4-typed-framing.md) retires the sentinel once a
+// v4 framing (see WIRE_PROTOCOL_VERSION in wire-compatibility.ts) retires the sentinel once a
 // socket upgrades: control messages travel as WebSocket TEXT frames and
 // binary frames are full-alphabet PTY input. This module's controlFrame stays
 // the encoding for the v3 bootstrap (every socket's first resume) and for