@cplieger/web-terminal-ui 4.3.1 → 4.4.0

package/README.md

@@ -128,12 +128,15 @@ are importable from `…/features/<name>` (`clipboard`, `context-menu`,
   keeps clean, label-only tabs. Requires a server that speaks the session API
   (`/api/sessions` and `/ws?session=`), such as `web-terminal-server`.
 - `presetAgentTabbed()` — the same feature set as `presetTabbed()` (activity
-  monitor included), but with `preferInputTitle`: each tab's label follows the
-  latest submitted line (persisted server-side and recovered on reload) and the
-  program's OSC 0/2 title is ignored — for an agent shell such as `web-terminal-kiro`
-  whose program emits a non-empty but useless OSC title. Its status dots
-  (idle / working / done / needs-input) come from the same activity monitor,
-  driven by the server's status SSE and its OSC-9 classifier.
+  monitor included), tuned for an agent shell such as `web-terminal-kiro`: with
+  `preferInputTitle`, each tab's label follows the latest submitted line
+  (persisted server-side and recovered on reload) and the program's non-empty
+  but useless OSC 0/2 title is ignored; and with `presumeReports`, the idle
+  activity dot shows from tab creation instead of waiting for the session's
+  first OSC 9;4 signal — every session is an agent, so there is nothing to
+  prove. Its status dots (idle / working / done / needs-input) come from the
+  same activity monitor, driven by the server's status SSE and its OSC-9
+  classifier.
 
 ### Options
 

package/css/30-tabs.css

@@ -357,8 +357,11 @@
    tabs feature adds .wt-reports to that dot (paintStatusDot). A program that
    emits no OSC 9 signal (a plain bash/sh) has no activity concept, so its tabs
    stay clean, label-only; a progress-reporting agent (kiro-cli, Claude Code)
-   lights up. The element stays in the DOM either way (JS sets data-status
-   regardless), so revealing it is a pure CSS switch. */
+   lights up. An agent-shell consumer can PRESUME the report instead (tabs'
+   presumeReports option, on in presetAgentTabbed): .wt-reports is then set
+   from tab creation, so the idle dot shows immediately rather than popping in
+   after the agent's first signal. The element stays in the DOM either way (JS
+   sets data-status regardless), so revealing it is a pure CSS switch. */
 :where(.wt-root) .wt-status-dot {
   display: none;
   width: 9px;
@@ -391,19 +394,43 @@
   border: 1.5px solid color-mix(in oklch, var(--text) 45%, transparent);
 }
 
-/* Agent working: solid pulsing dot (--status-working; pale lime by default —
-   its high lightness keeps it clear on every tab state) wearing the same 2px
-   ring as input, so the two agent-turn states share one silhouette: a live
-   turn pulses (dot + ring together), a turn blocked on the user is that same
-   silhouette frozen and recolored (input, below). Motion separates working
-   from input; the ring separates both from done's bare disc. Server-side this
-   is driven by the OSC 9;4 progress signal, so it tracks agent activity, not
-   the user typing at the prompt. */
+/* Agent working: two INDEPENDENTLY animated layers on one element make the
+   "alive" read (the status-badge "processing" idiom — Ant Design's processing
+   badge, the classic CSS live-indicator ripple): the solid disc keeps full
+   opacity and gently GLOWS (its colors brighten mid-beat), while a ::after
+   ring — born exactly on the static 2px ring — RIPPLES outward and dissolves,
+   re-emitted each cycle. The static ring itself never moves, so working keeps
+   input's exact rest silhouette (a live turn ripples; a turn blocked on the
+   user is that same silhouette frozen — see input below). Motion separates
+   working from input; the ring separates both from done's bare disc. The old
+   single-layer pulse faded disc + ring together (opacity on the element),
+   which read as a blink and coupled the layers — an element's opacity always
+   multiplies onto its pseudos, so true independence requires animating disc
+   COLORS, not element opacity. Server-side this is driven by the OSC 9;4
+   progress signal, so it tracks agent activity, not the user typing at the
+   prompt. */
 :where(.wt-root) .wt-status-dot[data-status="working"] {
+  position: relative;
   background: var(--status-working);
   border-color: var(--status-working);
   box-shadow: 0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
-  animation: wt-pulse 1.2s ease-in-out infinite;
+  animation: wt-working-glow 1.2s ease-in-out infinite;
+}
+
+/* The ripple layer: at scale(1) its 2px border overlays the static ring's
+   9->13px band exactly (inset -2px), then the wave detaches, expanding and
+   fading. transform + opacity only, so it composites without repaints. It
+   exists only in the working state — no stale layer to pin when a dot changes
+   status. (The switcher notification dot never shows working — input/done
+   only — so its position: absolute placement never meets this rule's
+   position: relative.) */
+:where(.wt-root) .wt-status-dot[data-status="working"]::after {
+  content: "";
+  position: absolute;
+  inset: -2px;
+  border: 2px solid var(--status-working);
+  border-radius: 50%;
+  animation: wt-working-ripple 1.2s ease-in-out infinite;
 }
 
 /* Agent done / ready: solid disc (--status-done), no motion. The default green
@@ -436,39 +463,58 @@
   opacity: 0.5;
 }
 
-@keyframes wt-pulse {
+/* The disc's glow beat: base -> brighter -> base, then a rest until the next
+   cycle. Colors are set at EVERY frame, which both drives the glow and pins
+   the paint — a dot entering working in the same frame input/done ends can
+   never re-pulse the previously rasterized paint (the hazard the old
+   opacity-only pulse had to pin box-shadow against). Element opacity stays 1
+   throughout; see the layer-independence note on the working rule. */
+@keyframes wt-working-glow {
   0%,
+  70%,
   100% {
-    /* Pin the animated layer's paint as well as its opacity. When working begins
-       in the same frame that input/done ends, an opacity-only animation can
-       pulse the previously rasterized input/done paint (the input ring
-       included, hence the box-shadow pin). */
     background-color: var(--status-working);
     border-color: var(--status-working);
-    box-shadow: 0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
-    opacity: 1;
   }
 
-  50% {
-    background-color: var(--status-working);
-    border-color: var(--status-working);
-    box-shadow: 0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
+  35% {
+    background-color: color-mix(in oklch, var(--status-working) 78%, #fff);
+    border-color: color-mix(in oklch, var(--status-working) 78%, #fff);
+  }
+}
+
+/* The ripple wave: one emission per cycle, launching off the static ring and
+   dissolving by ~2.1x. Opacity starts at the static ring's own 40% weight so
+   the wave reads as the ring letting go of a copy, not a new brighter object. */
+@keyframes wt-working-ripple {
+  0% {
+    transform: scale(1);
     opacity: 0.4;
   }
+
+  100% {
+    transform: scale(2.1);
+    opacity: 0;
+  }
 }
 
-/* Reduced-motion (or the animations feature off): drop the pulse, keep color. */
+/* Reduced-motion: drop the working motion (glow + ripple), keep color. */
 @media (prefers-reduced-motion: reduce) {
   :where(.wt-root) .wt-status-dot[data-status="working"] {
     animation: none;
-    /* The pulse is what separates working from input's frozen silhouette; with
-       motion removed, punch an inner hole (dot -> donut) so working differs
-       from input (solid ringed disc) and done (bare disc) by shape, not hue
-       alone (WCAG 1.4.1). The outer ring stays. */
+    /* Motion is what separates working from input's frozen silhouette; with
+       it removed, punch an inner hole (dot -> donut) so working differs from
+       input (solid ringed disc) and done (bare disc) by shape, not hue alone
+       (WCAG 1.4.1). The outer ring stays. */
     box-shadow:
       inset 0 0 0 2px var(--bg),
       0 0 0 2px color-mix(in srgb, var(--status-working) 40%, transparent);
   }
+
+  /* The ripple layer disappears entirely (not just paused mid-wave). */
+  :where(.wt-root) .wt-status-dot[data-status="working"]::after {
+    content: none;
+  }
 }
 
 /* ===== Catching-up cue (tabs feature, sections 12/13) =====

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplieger/web-terminal-ui",
-  "version": "4.3.1",
+  "version": "4.4.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": "GPL-3.0-or-later",

package/src/features/tabs/index.ts

@@ -100,6 +100,13 @@ export interface TabsOptions {
    *  reload), and the unreliable OSC title is ignored entirely. presetAgentTabbed
    *  enables this. */
   preferInputTitle?: boolean;
+  /** Presume every session reports activity (an agent shell, where the program
+   *  always emits OSC 9;4 progress): each tab's dot is visible as idle from
+   *  creation instead of popping in seconds later when the agent has booted
+   *  far enough to first report — the server's sticky reportsActivity flag
+   *  then merely confirms. Default false (evidence-driven reveal: a plain
+   *  shell keeps clean, label-only tabs). presetAgentTabbed enables this. */
+  presumeReports?: boolean;
 }
 
 // looksLikeHardwareKey reports whether a keydown could only have come from a
@@ -135,6 +142,12 @@ function looksLikeHardwareKey(ev: KeyboardEvent): boolean {
 export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
   const apiBase = opts.apiBase ?? DEFAULT_API_BASE;
   const preferInputTitle = opts.preferInputTitle ?? false;
+  const presumeReports = opts.presumeReports ?? false;
+  // reportsOf floors the server's per-session reportsActivity flag with the
+  // consumer's presumption (see TabsOptions.presumeReports): an agent shell
+  // shows the idle dot from tab creation instead of waiting out the agent's
+  // boot-to-first-OSC-9;4 window.
+  const reportsOf = (reports?: boolean): boolean => presumeReports || (reports ?? false);
   // The session REST client (model.ts): every call timeout-bounded, list
   // shape-guarded, title persistence fire-and-forget.
   const api = createSessionAPI(apiBase);
@@ -912,7 +925,7 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
         if (!label || !dot || !close) {
           throw new Error("web-terminal-ui: tab chrome missing parts");
         }
-        paintStatusDot(dot, info.status, info.reportsActivity ?? false);
+        paintStatusDot(dot, info.status, reportsOf(info.reportsActivity));
         const aria = tablist.registerTab(el);
         // Append to the scroller's end: the tab list is ALL the scroller holds
         // (the "+" and keyboard button are fixed bar items outside it).
@@ -941,7 +954,7 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
           aria,
           scrollTop: 0,
           following: true,
-          reports: info.reportsActivity ?? false,
+          reports: reportsOf(info.reportsActivity),
         };
         // Set an initial label immediately (relabelAll refines it with de-dup
         // once the tab is in tabList and syncChrome runs).
@@ -1669,7 +1682,7 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
               info.status,
               info.title,
               info.clientTitle,
-              info.reportsActivity ?? false,
+              reportsOf(info.reportsActivity),
             );
           }
           // A tab the server no longer lists was reaped/closed elsewhere (or
@@ -1703,7 +1716,7 @@ export function tabs(opts: TabsOptions = {}): TerminalFeature<TabsApi> {
           // SSE-adopted tab without its persisted title — in preferInputTitle
           // mode the label then fell back to "New tab" on reload.
           adoptSession(s);
-          applyStatus(s.id, s.status, s.title, s.clientTitle, s.reportsActivity ?? false);
+          applyStatus(s.id, s.status, s.title, s.clientTitle, reportsOf(s.reportsActivity));
           ensureActive();
           syncChrome();
         });

package/src/presets/agent-tabbed.ts

@@ -4,12 +4,19 @@ import type { TerminalFeature } from "../kernel/types.js";
 import { buildTabbed } from "./tabbed.js";
 
 /** Tabbed UI for an agent shell (web-terminal-kiro). Same features as
- *  presetTabbed, but with `preferInputTitle`: the agent's program (kiro-cli)
- *  emits a non-empty but useless OSC 0/2 title, so each tab's label follows the
- *  latest submitted line (persisted server-side and recovered on reload) and
- *  the OSC title is ignored. The agent-vs-generic status distinction remains
- *  server-side (a status classifier mapping OSC 9 notifications to
- *  done/needs-input). */
+ *  presetTabbed, tuned for sessions that ARE agents:
+ *  - `preferInputTitle`: the agent's program (kiro-cli) emits a non-empty but
+ *    useless OSC 0/2 title, so each tab's label follows the latest submitted
+ *    line (persisted server-side and recovered on reload) and the OSC title
+ *    is ignored.
+ *  - `presumeReports`: every session's program is an agent that WILL report
+ *    OSC 9;4 progress, so the idle activity dot shows from tab creation
+ *    instead of popping in seconds later when the agent has booted far enough
+ *    to first report; the server's sticky reportsActivity flag then merely
+ *    confirms. (presetTabbed keeps the evidence-driven reveal instead: a
+ *    plain shell never grows a meaningless dot.)
+ *  The agent-vs-generic status distinction remains server-side (a status
+ *  classifier mapping OSC 9 notifications to done/needs-input). */
 export function presetAgentTabbed(): TerminalFeature<unknown>[] {
   return buildTabbed(true);
 }

package/src/presets/tabbed.ts

@@ -14,19 +14,26 @@ import { presetSingle } from "./single.js";
  *  externally-driven mobile toolbar (its grid is opened from a keyboard button
  *  in the tab bar, not its own toggle), the activity monitor (the status-SSE
  *  data source), tabs wired to both, and animations. The activity dot reveals
- *  itself per tab only when a session reports activity (OSC 9;4), so the
- *  monitor is always included — a plain shell just never shows a dot. The
+ *  itself per tab only when a session reports activity (OSC 9;4) — or from tab
+ *  creation when the agent composition presumes it — so the monitor is always
+ *  included; a plain shell under presetTabbed just never shows a dot. The
  *  toolbar and monitor are ordered before tabs because tabs reads their APIs
  *  via ctx.use. Shared by presetTabbed and presetAgentTabbed (agent-tabbed.ts),
- *  which differ only in the title source. */
-export function buildTabbed(preferInputTitle: boolean): TerminalFeature<unknown>[] {
+ *  which differ only in the agent-shell tuning: input-derived titles
+ *  (preferInputTitle) + presumed activity reporting (presumeReports). */
+export function buildTabbed(agentShell: boolean): TerminalFeature<unknown>[] {
   const kb = mobileToolbar({ externalToggle: true });
   const monitor = activityMonitor();
   return [
     ...presetSingle(),
     kb,
     monitor,
-    tabs({ keyboardToggle: kb, activityMonitor: monitor, preferInputTitle }),
+    tabs({
+      keyboardToggle: kb,
+      activityMonitor: monitor,
+      preferInputTitle: agentShell,
+      presumeReports: agentShell,
+    }),
     animations(),
   ];
 }