@danxbot/ui 25.1.0 → 25.3.0

package/dist/types/components/Tabs.d.ts

@@ -113,8 +113,21 @@ export interface TabListProps {
     className?: string;
     children: ReactNode;
     variant?: VariantProps<typeof tabs>["variant"];
+    /**
+     * The words for the two scroll buttons a strip that overflows grows on the edge that has more tabs. DX-4973.
+     *
+     * ABSENT MEANS FADE ONLY. A strip wider than its box always fades its content out at the edge that has more (that is the cue, and it
+     * needs no colour: it fades the tabs themselves, not a patch of the surface over them). The buttons are the part a keyboard or a
+     * screen reader can act on, and the library has no default language, so the caller supplies what they say ("Show earlier tabs",
+     * "Show later tabs") rather than the strip speaking English by itself. Pass them wherever a strip can overflow. A button shows
+     * only on the edge that has more.
+     */
+    scrollLabels?: {
+        before: string;
+        after: string;
+    };
 }
-export declare function TabList({ className, children, variant }: TabListProps): import("react").JSX.Element;
+export declare function TabList({ className, children, variant, scrollLabels }: TabListProps): import("react").JSX.Element;
 export interface TabProps extends Omit<BaseTabs.Tab.Props, "className"> {
     className?: string;
     variant?: VariantProps<typeof tabs>["variant"];

package/dist/types/components/chart/ShareBar.d.ts

@@ -1,4 +1,4 @@
-import type { Ref } from "react";
+import { type Ref } from "react";
 export interface ShareBarSegment {
     /** Unique within the bar. */
     id: string;

package/dist/types/components/chart/share-bar-labels.d.ts

@@ -0,0 +1,17 @@
+/** The smallest clear space, in px, left between two direct labels that sit side by side. */
+export declare const LABEL_GAP = 4;
+/** One direct label as laid out. All lengths are px, measured from the bar's LEFT edge (physical, also in RTL). */
+export interface LabelBox {
+    key: string;
+    share: number;
+    /** Offset of the label's centre (its segment's centre) from the bar's left edge. */
+    center: number;
+    /** Width of the printed label. */
+    width: number;
+}
+/**
+ * The keys of the labels that must NOT be drawn: one whose box (`center ± width / 2`) leaves `[0, barWidth]`
+ * (a clipping ancestor would cut it to a wrong number), or that comes within `LABEL_GAP` of a larger-share
+ * label already kept. The larger share wins a contested spot, so the answer does not depend on input order.
+ */
+export declare function labelsToDrop(boxes: readonly LabelBox[], barWidth: number): Set<string>;

package/dist/types/components/stepper/derive.d.ts

@@ -13,7 +13,8 @@ export declare function assertSteps(steps: readonly Step[], current: number): vo
 /**
  * What one step IS, given where the cursor is.
  *
- * PRECEDENCE, and the first rule is the interesting one. `blocked` outranks
+ * PRECEDENCE: failed, blocked, current, complete, unverified, skipped, incomplete, upcoming. DX-4973 puts `failed` first.
+ * The next rule is the interesting one. `blocked` outranks
  * everything, including `complete`, wherever the step sits. Data saying both
  * is contradictory, and when a record contradicts itself the exception is what
  * the reader needs — the same call `ProvenanceBadge` makes when it stays quiet

package/dist/types/components/stepper/types.d.ts

@@ -35,6 +35,18 @@ export interface Step {
      * An empty string throws, for the same reason an empty `blocked` does: the words ARE the spoken state.
      */
     unverified?: string;
+    /**
+     * A check of this step ran and FAILED, and what it said. DX-4973.
+     *
+     * The VALUE is the reason, supplied by the caller ("Asana refused the token", "The bot is not in that channel"): the library cannot
+     * know what a flow checks, and the words are printed in red under the label and spoken as the step's state (so start with what
+     * happened, because no fixed word like "failed" is added). It is the one red marker a step can carry on purpose, distinct from
+     * `blocked` (cannot start yet, amber, and the only one that gates the forward control), `unverified` (done, nothing to test, grey),
+     * `skipped` (left on purpose, grey) and `incomplete` (passed over, red cross). A failed step does NOT gate forward movement by
+     * itself: add `blocked` as well when it must. It outranks every other state, `blocked` and the cursor included, because a failure is
+     * the thing a reader must not miss; it is counted in `StepperProgress.failed` and in neither chip. An empty string throws.
+     */
+    failed?: string;
     /**
      * Why the flow cannot move on from here. Absent means it can.
      *
@@ -56,14 +68,16 @@ export interface Step {
  * What a step IS right now — derived from the steps and the cursor, never
  * stored.
  *
- * Seven, not two, because "finished", "you are here", "done but unproven", "you left it on purpose",
+ * Eight, not two, because "finished", "you are here", "done but unproven", "you left it on purpose",
  * "you missed it", "not reached yet" and "this is what is stopping you" call for
  * different next actions and one absence of action. Collapsing them to a boolean is what
  * produces a rail where a skipped step and an untouched one look identical.
  */
 export type StepStatus = 
+/** Carries `failed` words: a check ran and refused it. Beats every other reading, `blocked` included. Red. DX-4973. */
+"failed"
 /** `complete: true`. */
-"complete"
+ | "complete"
 /** Carries a `blocked` reason. Beats every other reading — see `stepStatus`. */
  | "blocked"
 /** The cursor is on it. */
@@ -91,12 +105,14 @@ export interface StepperProgress {
     /** How many steps are `complete`, anywhere in the flow. */
     complete: number;
     /**
-     * Behind the cursor, not complete and marked neither `skipped` nor `unverified`: the steps missed, the ones the red chip counts. (Renamed in meaning by
+     * Behind the cursor, not complete and marked none of `skipped`, `unverified` or `failed`: the steps missed, the ones the red chip counts. (Renamed in meaning by
      * DX-4963: a step the person skipped on purpose is `acknowledged`, not counted here.)
      */
     skipped: number;
     /** Steps marked `skipped` that are not complete, anywhere in the flow: left on purpose, counted in the neutral chip. DX-4963. */
     acknowledged: number;
+    /** Steps carrying `failed` words, anywhere in the flow. Counted in no chip. DX-4973. */
+    failed: number;
     /** Steps carrying `unverified` words that are not complete, anywhere in the flow: done, with nothing to test. Counted in no chip. DX-4968. */
     unverified: number;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danxbot/ui",
-  "version": "25.1.0",
+  "version": "25.3.0",
   "type": "module",
   "description": "Danxbot — a domain-agnostic React design system with motion as a first-class primitive.",
   "license": "MIT",