@cplieger/web-terminal-ui 5.6.1 → 6.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-ui",
-  "version": "5.6.1",
+  "version": "6.0.0",
   "type": "module",
   "description": "Reference touch-first browser UI for @cplieger/web-terminal-engine: a composable kernel + feature modules (tabs, activity monitor, mobile toolbar, context menu, IME, predictive echo, viewport handling) and CSS. One createTerminal() call.",
   "license": "MPL-2.0",
@@ -95,6 +95,6 @@
     "LICENSE",
     "README.md",
     "!src/**/*.test.ts",
-    "!src/**/fc-strict-setup.ts"
+    "!src/**/*-setup.ts"
   ]
 }

package/src/features/tabs/attention.ts

@@ -137,7 +137,8 @@ export function createAttention(env: AttentionEnv): AttentionSurfaces {
 }
 
 /** iconVariantHref rewrites an icon URL to its variant, by the convention the
- *  asset generator writes (scripts/gen-attention-icons.py): the `favicon` token
+ *  asset generator writes (the fleet's .kiro/scripts/gen-attention-icons.py, which
+ *  serves every consuming app rather than living in this repo): the `favicon` token
  *  of the filename gains `-<variant>`, so `/favicon.svg` becomes
  *  `/favicon-input.svg` and `/favicon-32x32.png` becomes
  *  `/favicon-input-32x32.png`. The extension is preserved, so each link keeps

package/src/features/tabs/index.ts

@@ -146,7 +146,7 @@ export interface TabsOptions {
    *  be served alongside it with `-input`, `-done` and `-alert` inserted after
    *  that token (`/favicon.svg` needs `/favicon-input.svg`; `/favicon-32x32.png`
    *  needs `/favicon-input-32x32.png`). Generate them with
-   *  `scripts/gen-attention-icons.py`, which writes exactly those names, and
+   *  `.kiro/scripts/gen-attention-icons.py`, which writes exactly those names, and
    *  assert their presence in the APP's own tests — the library cannot check a
    *  file it does not ship, and a missing variant is a blank tab icon.
    *

package/src/features/tabs/model.ts

@@ -243,7 +243,7 @@ export function worseCue(a: CueStatus | "", b: CueStatus | ""): CueStatus | "" {
 
 /** The icon variant a cue paints, which is NOT one per status: `crashed` and
  *  `failed` both render --status-failed, so they share one asset. An app ships
- *  one icon per name returned here (see scripts/gen-attention-icons.py). */
+ *  one icon per name returned here (see .kiro/scripts/gen-attention-icons.py). */
 export function cueIconName(status: CueStatus): "input" | "done" | "alert" {
   if (status === "input" || status === "done") {
     return status;

package/src/presets/tabbed.ts

@@ -35,7 +35,7 @@ export interface TabbedPresetOptions {
   /** Swap the page's icon links to a status variant while a background session
    *  wants the user. Off by default, and enabling it is a promise that the
    *  variant assets are served — see TabsOptions.attentionIcons for the naming
-   *  contract and scripts/gen-attention-icons.py, which writes them. */
+   *  contract and .kiro/scripts/gen-attention-icons.py, which writes them. */
   attentionIcons?: boolean;
 }
 

package/src/dom-isolation-setup.ts

@@ -1,32 +0,0 @@
-// Per-test cleanup of DOM state that outlives a test file.
-//
-// Loaded via vitest's `setupFiles` alongside fc-strict-setup, because
-// `vitest.config.ts` deliberately sets `isolate: false`: test FILES share one
-// happy-dom instance inside a worker thread, which is what makes the suite fast
-// and also what lets one file's leftovers reach another's assertions.
-//
-// The document selection is the state that actually bites, for two compounding
-// reasons. Several suites end with a live selection on purpose (the kernel's
-// mouse-selection and type-to-focus suites assert that a gesture PRESERVED one,
-// and contextMenu's dismissal suite clicks a real Select All). And happy-dom does
-// not apply the selection fixup a real browser does, so a range whose nodes were
-// removed by `document.body.replaceChildren()` keeps reporting its old text:
-// measured rangeCount 1, isCollapsed false, and toString() unchanged after the
-// nodes were detached.
-//
-// Left alone, that reached `context-menu.test.ts`'s "omits Copy with nothing
-// selected" case, which found text to copy and failed. Order-dependently, so it
-// passed every local run and every PR check, then failed once on main where the
-// thread layout put the files in a different order. Clearing here rather than in
-// each suite keeps the guarantee independent of which files a worker happens to
-// pair up.
-import { beforeEach } from "vitest";
-
-beforeEach(() => {
-  // Node-environment files (the default; DOM files opt in per file) have no
-  // window, and nothing to clean.
-  if (typeof window === "undefined") {
-    return;
-  }
-  window.getSelection()?.removeAllRanges();
-});