@tangle-network/agent-app 0.45.50 → 0.45.51

package/dist/theme/tokens.css

@@ -522,7 +522,8 @@
 
 /* The waiting label. `background-clip: text` over a moving gradient, so the
    shimmer runs THROUGH the glyphs rather than behind them. Marked essential:
-   it is the only signal that work is still in flight. */
+   it is the only signal that work is still in flight. Its reduced-motion
+   answer is at the bottom of this file, with the floor it opts out of. */
 .agent-shimmer {
   background: linear-gradient(
     90deg,
@@ -583,6 +584,13 @@
  * out by declaring `data-motion="essential"`; the exclusion covers that element
  * and its subtree, and `:where()` keeps the selector at zero specificity so a
  * consumer's own `!important` can still win.
+ *
+ * `essential` is an exemption from the BLANKET rule, not a licence to keep
+ * running. It exists because collapsing a meaning-carrying animation to a 1ms
+ * flash destroys the meaning, so the element gets to answer for itself — and it
+ * then OWES that answer. An element with no end condition owes it most, which
+ * is why `.agent-shimmer` states its own below: the sweep stops, and what it
+ * was saying is re-stated as a static difference the reader can still see.
  */
 @media (prefers-reduced-motion: reduce) {
   :root {
@@ -603,6 +611,42 @@
     transition-duration: 1ms !important;
   }
 
+  /* The waiting label's own answer. It is `data-motion="essential"` because the
+     sweep is the ONLY thing separating an agent that is working from one that
+     is stuck, so the floor above must not collapse it — but an INFINITE
+     animation is exactly what someone asking for reduced motion is asking to be
+     rid of, and running it anyway because the element declared itself essential
+     is the override this file calls a defect.
+
+     So the meaning is carried without the motion. The sweep stops and the
+     gradient comes off (it exists only to be moved), which puts the glyphs back
+     under `color` instead of leaving them transparent windows onto it.
+
+     The DOTTED RULE is the discriminator, and it is the only one. Measured in
+     Chromium under `prefers-reduced-motion: reduce`, light and dark: the live
+     label computes `text-decoration: underline dotted` where a settled label
+     beside it computes `none`, and the two resolve to the SAME color and the
+     same weight. That is by construction — `color: inherit` hands the label
+     whatever its context already uses, and the settled label shares that
+     context. In `mission-activity`'s lane both tool names read rgb(12,12,21)
+     light / rgb(236,236,241) dark; in the chat trace toggle "Thinking · 12s"
+     and "Thought for 12s" both read rgb(96,96,99) light / rgb(158,158,160)
+     dark, because that button is `text-muted-foreground`. So the reader tells
+     in-flight from done by the rule under the word, from a still frame — not by
+     tone and not by weight.
+
+     Not `content: '…'` or any other generated text: this element's text is read
+     by a screen reader, and adding pseudo-content changes what is announced. */
+  .agent-shimmer {
+    animation: none;
+    background: none;
+    background-clip: border-box;
+    -webkit-background-clip: border-box;
+    color: inherit;
+    text-decoration: underline dotted currentColor;
+    text-underline-offset: 3px;
+  }
+
   html {
     scroll-behavior: auto !important;
   }

package/dist/web-react/index.d.ts

@@ -527,7 +527,14 @@ interface QuestionOptionListProps {
 }
 /** The radio/checkbox option rows for a select field. Renders a fragment of
  *  option `<label>` rows so a card keeps its own wrapping layout and appends
- *  its own write-in input. */
+ *  its own write-in input.
+ *
+ *  The rows arrive as a SEQUENCE (`.agent-arrive` + `--stagger-index`), which
+ *  is the difference between reading a list and being shown one: the eye is
+ *  told there are N choices and in what order before it has read any of them.
+ *  The index is safe to take straight from the map because an option list does
+ *  not re-sort under a mounted card — a different set of options is a
+ *  different `key`, and a different ask resets the card wholesale. */
 declare function QuestionOptionList({ groupName, idPrefix, options, multi, selectedValues, disabled, onToggle, answered, }: QuestionOptionListProps): react.JSX.Element;
 interface InteractionQuestionCardProps {
     interaction: ChatInteraction;
@@ -1050,6 +1057,12 @@ interface MissionActivityLaneProps {
 /**
  * Collapsed sub-rows under a mission step — one row per delegated run —
  * expanding to the step's waterfall. Renders nothing for an empty lane.
+ *
+ * A sub-row appears because a delegated run STARTED or FINISHED, which is the
+ * one kind of list change worth choreographing: it arrives, and the group
+ * arrives as a sequence. Keying on `taskId` is what keeps the rest still — the
+ * snapshot re-renders every poll, and a row whose status merely advanced holds
+ * the DOM node it already had.
  */
 declare function MissionActivityLane({ activity, startedAt, nowMs }: MissionActivityLaneProps): react.JSX.Element | null;
 interface AgentActivityPanelProps {

package/dist/web-react/index.js

@@ -131,7 +131,7 @@ import {
   withoutRecordGridCreated,
   withoutRecordGridRemoved,
   withoutRecordGridUpdate
-} from "../chunk-7HY4LX7O.js";
+} from "../chunk-CXPWUCXC.js";
 import "../chunk-FBVLEGEG.js";
 import {
   EvidenceLineageTable,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tangle-network/agent-app",
-  "version": "0.45.50",
+  "version": "0.45.51",
   "packageManager": "pnpm@11.17.0",
   "description": "Build agent applications with typed chat, tools, sandboxes, integrations, billing, and evaluation.",
   "keywords": [