@cplieger/web-terminal-engine 4.0.1 → 5.0.0

package/jsr.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-engine",
-  "version": "4.0.1",
+  "version": "5.0.0",
   "license": "MPL-2.0",
   "exports": {
     ".": "./src/index.ts"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-engine",
-  "version": "4.0.1",
+  "version": "5.0.0",
   "type": "module",
   "scripts": {
     "typecheck": "tsc -p tsconfig.json",
@@ -12,9 +12,9 @@
     "@cplieger/web-terminal-engine-v3": "npm:@cplieger/web-terminal-engine@2.8.0",
     "@eslint/js": "10.0.1",
     "@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",
+    "@stryker-mutator/core": "10.0.0",
+    "@stryker-mutator/typescript-checker": "10.0.0",
+    "@stryker-mutator/vitest-runner": "10.0.0",
     "@types/pngjs": "6.0.5",
     "@typescript/native": "npm:typescript@7.0.2",
     "@vitest/coverage-v8": "4.1.10",

package/src/render.ts

@@ -7,7 +7,7 @@
 // "scrollback": the live window is simply the last `height` absolute indices,
 // and a line that scrolls into history just stops being updated. This is what
 // removes the live/history reconciliation that caused the duplicate-rows and
-// view-jumping bugs (see the #web-terminal-engine steering doc, "Design rationale").
+// view-jumping bugs.
 //
 // Decode frames feed the store (handleScreen/handleScroll); a single
 // requestAnimationFrame flush drains the store's change set and applies it:

package/src/scroll.ts

@@ -7,7 +7,7 @@
 // suppress timer, and no programmatic-vs-user flag. That heuristic soup (a
 // 100px tolerance, a 150ms debounce, a 60-second touch window) was the source
 // of the view-jumping and scroll-interruption bugs (the legacy heuristic-soup
-// failure mode; see the #web-terminal-engine steering doc, "Design rationale").
+// failure mode).
 //
 // The renderer calls stickToBottom() once after each flush: if following, pin
 // to the new bottom; if holding, do nothing. Holding the reading position when

package/src/store.ts

@@ -1,8 +1,7 @@
 // Absolute-index line store: the client's authoritative model of the
 // terminal. One buffer keyed by absolute line index, with the live screen
 // window sliding along it. This is the data model that resolves the
-// live/history split (see the #web-terminal-engine steering doc, "Design
-// rationale"): there is no separate
+// live/history split: there is no separate
 // "live zone" and "scrollback" here, only lines addressed by absolute index,
 // the last `height` of which happen to still be changing.
 //
@@ -160,8 +159,7 @@ function isWireRunArray(value: unknown): value is WireRun[] {
  * streaming session into one whole-layer invalidation PER LINE — on WebKit
  * (which re-rasterizes the resident tiles each time) that is the single largest
  * compositor cost this client can trigger, and on a memory-pressured iPhone it
- * is churn the page cannot afford (see the web-terminal-ui steering doc, "iOS
- * memory ceiling"). Batching keeps appends eviction-free between passes, so the
+ * is churn the page cannot afford. Batching keeps appends eviction-free between passes, so the
  * layer shifts once per batch instead of once per line. The retained count is
  * hard-bounded at `max(maxLines, live-window height)` after every apply — the
  * window is never evicted (a cap at or below the screen height keeps the full
@@ -1482,7 +1480,6 @@ export class LineStore {
 
   /**
    * applyLine is the guarded core. It enforces the apply-line guard set
-   * (see the #web-terminal-engine steering doc, "Design rationale"):
    * valid index, not stale, idempotent, and
    * cap-bounded. Returns nothing; effects are recorded in the dirty/evicted
    * sets for the next drain.

package/src/types.ts

@@ -37,8 +37,7 @@ export interface ScreenMessage {
    * Absolute line index of the top screen row (row 0). A changed row at
    * window index `y` has absolute index `base + y`. The client stores
    * every line by absolute index, so applying a row is idempotent and
-   * never duplicates (see the #web-terminal-engine steering doc,
-   * "Design rationale").
+   * never duplicates.
    */
   base: number;
   /** Cursor position as [row, col], zero-indexed within the window. */