apollo-ui — Engineering Performance

fix(apollo-wind): quality pass across the component library A single change covering the apollo-wind audit: exports, test coverage, accessibility, design tokens, API consistency and dependency hygiene. Coverage gate: - vitest only enforces limits nested under coverage.thresholds, so the previous top-level keys were silently ignored and the gate never ran; nest them with a ratcheting floor (lines 60, functions 63, branches 54, statements 58) and exclude the Storybook-only src/templates demos from the metric - raise testTimeout and hookTimeout to 20s so wall-clock variance on shared CI runners cannot fail correct tests - new suites for src/components/custom (14 components), the untested ui components (chart, drawer, editable-cell, button-group, command, datetime-picker), the layout row/column/grid primitives, and form-designer, form-plugins, form-state-viewer and schema-viewer, each file including a jest-axe check Exports: - chart and drawer were implemented but unreachable from both the ui barrel and the package root; add them along with portal-container, lockable-value-field and variable-picker - give src/foundation an index barrel; the ./foundation subpath is held back for now, because the token surface is not ready for consumption Accessibility: - name the icon-only controls that had tooltip-only labels: panel-flow rail nav, form-designer section and field move/delete buttons, the section accordion chevron, the Always required checkbox and the rule-builder selects - associate the field-renderer and flow-properties-simple select triggers with their field labels Tokens and consistency: - unify the dialog, alert-dialog, sheet and drawer overlays on the theme-aware bg-curtain scrim token, whose alpha is restored in the preceding apollo-core commit - stats-card moves its per-render variant map into cva variants; avatar gains a cva size variant - forward refs from combobox, date-picker, date-range-picker, datetime-picker, file-upload and tree-view - adopt the shadcn v4 data-slot convention across all ~70 ui components, which also fixes calendar selectors that never matched Dependencies: - de-duplicate tailwindcss, @tailwindcss/postcss and autoprefixer, each of which was declared in both dependencies and devDependencies; all three stay in dependencies, because dist/tailwind.css ships a bare `@import "tailwindcss"` that Tailwind resolves from the installed package's own directory, and postcss.config.export.js imports the other two at consumer runtime. Installing @uipath/apollo-wind alone must be sufficient, so tailwindcss is a dependency and not a peer. Cleanup: - fix the biome templates exclusion, which never matched src/templates - delete the empty src/components/UiPath directory; the deprecated fontFamily.sans alias is kept a while longer for existing templates Storybook: - stories added for previously undocumented ui and custom components - derive the component gallery's story-ID prefix from the gallery's own story ID, so its links resolve both standalone and composed - drop the quick start's `npx shadcn@latest add` step Claude-Session: https://claude.ai/code/session_015n5YBa3rwBSxCUjkGNRKbG Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

feat(apollo-react): port over agents canvas [AG-330] (#4) * feat: port over agents canvas [AG-330] more minor code cleanup Run prettier Fix edges Fix typecheck and lint Fix format * fix: move constants, panning component, and conditional edge component * fix: use NodeContextMenu component and add todo for removing NodeBoundaryIconsContainer * chore: export agent canvas in build and add test coverage script * fix: add missing newline to icons index.ts --------- Co-authored-by: snuziale <6452957+snuziale@users.noreply.github.com>

feat(apollo-react): add unified CanvasEdge with waypoint editing and pluggable routing Introduce CanvasEdge, a single canvas edge component whose behaviors compose via data flags (enableEditing, enableExecution, enableToolbar), and refactor SequenceEdge into a thin backward-compatible preset (routing: 'handle' + execution + toolbar). - Orthogonal waypoint routing with draggable segments, insert/remove waypoints, grid snapping, and node-drag rebalancing - Shared primitives (EdgePath, EdgeArrow, EdgeLabel, handles) and hooks extracted from the old SequenceEdge monolith - Pluggable EdgeRouter contract with useGraphRouter orchestration (fingerprint-based store subscription; manual waypoints win) - Support React Flow's animated edge flag (no dasharray override) - Stories: editing, handle routing, controlled mode, pluggable router, and execution states; unit tests for geometry and waypoint math Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

feat(apollo-react): copy edge toolbar changes from uix [MST-5311]

feat(apollo-react): support auto expansion of loop container [MST-9193]

feat(apollo-react): add loop node [MST-8596]

feat(apollo-react): support category nesting and constraint filtering

feat(apollo-core): add core and playground

feat(apollo-react): chat service, messageRenderers, markdown, attachments render

feat(apollo-react): add line jumps to crossing canvas edges Waypoint-routed edges can now hop over the edges they cross, so criss-crossing lines read as passing over rather than joining. Opt in per edge with `data.enableLineJumps`. Edges publish their polylines to a shared `EdgeCrossingsStore`, which derives every crossing once per commit and hands each edge back only its own jumps. At a crossing it is the horizontal segment that arcs, which keeps the notch pattern stable while nodes are dragged. Jumps are derived from the vertices and only ever change the path string, so publishing cannot re-trigger the computation that produced it. A crossing counts only where it clears both segments' ends, so a T-junction or a shared handle reads as a junction rather than a crossing. The clearance widens to the border radius at a bend, where the rendered line curves off the ideal corner and an arc would sit beside the stroke rather than over it. `createRoundedPath` grows an optional `jumps` argument that replaces a stretch of a straight run with a semicircular arc. Jumps that would eat into a rounded corner, or that sit closer together than one arc width, are dropped so a densely crossed stretch degrades to fewer notches instead of a scalloped line. A registration that repeats positions the store already holds is dropped. That is what a re-render hands over while a drag rebuilds its waypoints, and without the guard every notification would schedule a second whole-graph pass that could only reproduce the jumps it just published. `EdgePath`, `EdgeArrow` and `EdgeLabel` are memoized so an edge notified about a crossing elsewhere on its path does not reconcile its arrow and label as well. `EdgeCrossingsProvider` defers to an ancestor store, so mounting one over a `BaseCanvas` cannot split a canvas across two registries. The story is built as a documentation page rather than a bare canvas, since the rules are subtle enough that a caption did not explain them: an annotated diagram of a single jump, cards for the interiority rule and for the guards that suppress an arc, and a rule table covering all eight outcomes including the mixed opt-in case. That page rests on shared chrome extracted from BaseNode's Shapes and Execution States stories, which had each grown a private copy of it: - StoryPage: themed root, title and lede, plus StorySection and StoryCollapsibleSection for the blocks below the preview - StoryPreview: framed 90vw canvas with an expand overlay. The children are live in one branch at a time, so toggling remounts the canvas - StorySpecTable: generic over the row type, with per-column cell variants Waypoint routing only: handle-routed edges produce a path string with no vertices to intersect. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C3Toj3SHbt75zwJ9ufqojS