David Anthony

feat(apollo-wind): add lockable value field

feat(apollo-react): add standalone and VS Code canvas templates

feat(apollo-wind): add reusable variable picker

feat(storybook): add system-wide introduction landing page and unify getting started docs - Add root-level Introduction/Overview landing page with three package cards (Apollo Wind, Apollo React, Apollo Core) linking to their getting started stories - Add Apollo Core Introduction/Getting Started story (Overview, Quick Start, Tokens tabs) - Move all Apollo Core token stories into a Theme/ subfolder for sidebar consistency - Restructure Apollo Wind getting started to match Apollo React Canvas format: Overview, Quick Start (with Add to existing project / Run locally path switcher), and Components tabs - Update Apollo React Canvas getting started with the same path switcher pattern - Remove github.com/UiPath/apollo-ui inline links from both getting started pages - Remove React and Core package cards from Wind getting started (covered by landing page) - Remove all em dash characters ( — ) from story copy across all documentation pages - Add no-em-dash rule to CLAUDE.md for authoring consistency Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

fix(apollo-react): edge labels lose their background and can render under crossing lines Two bugs in CanvasEdge/SequenceEdge labels, plus a new Storybook reference page documenting label behavior across themes and edge cases. Bug 1 — line renders over the label: EdgeLabel rendered as a raw foreignObject inside its own edge's <g>, so it competed in the same per-edge z-index/DOM-order stack as every other edge's stroke. An unselected edge crossing near a label could paint its line over that label. Fixed by portaling the label through xyflow's EdgeLabelRenderer instead (the pattern StageEdge/EdgeToolbar already use), which always paints after every edge's own <svg>, regardless of z-index or array order. Bug 2 — label background can render fully transparent: `background: var(--canvas-background)` had no fallback value. That variable only resolves under a themed ancestor (body.light/.future-*/.vertex/.canvas per canvas/styles/variables.css); a host that mounts the canvas without one (e.g. a shadow-DOM host) got a transparent label with illegible text over the line. Added a `--color-background` fallback to both EdgeLabel.tsx and StageEdge.tsx's StageEdgeLabel. New: Components/Edges/EdgeLabels Storybook page Consolidates label documentation that was previously scattered (and, in one spot, stale — SequenceEdge.stories.tsx's old EdgeLabels story still claimed labels render via "SVG foreignObject") into one dedicated reference page: - Orientation, Diff States: baseline label behavior - Crossing Labeled Edges: regression coverage for Bug 1 - Themes: the same label across all 9 canvas themes side by side - Missing Theme Fallback: reproduces Bug 2's scenario directly (simulates an unthemed ancestor via CSS custom-property `initial`), and documents the one remaining gap the fallback doesn't cover (no themed ancestor at all, background still transparent) - Overflow: long label text and short-edge crowding (known, undocumented limitations, not fixed here) - Execution Status, Bent Path, Read Only: label composes correctly with execution-status coloring, multi-segment waypoint routing, and readonly mode Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

feat(apollo-wind): add DAP component patterns page

feat(apollo-wind): add Core/HC editor themes and expand Code Editors patterns page - Adds apolloCoreDark/Light/HC Monaco and CodeMirror theme exports - Expands Code Editors patterns page with Monaco/CodeMirror dedicated pages and full/compact/input tab variants - Code Editors pages (Overview, Monaco, CodeMirror, Themes) now respond to the Storybook theme toolbar: page chrome follows the selected theme while individual editor cards on the Themes page remain pinned to their own themes - Fixes biome format issue in code-editors.stories.tsx - Bumps audit overrides: dompurify >=3.4.9, js-yaml >=4.1.2, markdown-it >=14.1.2, @babel/core >=7.29.1 to resolve new CVEs Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(apollo-react): add Input/Output panel prototype with three concept variants Three side-by-side concepts for design review of the node property panel's input/output experience. Each concept explores a different UX approach for browsing, filtering, and copying output references. - Concept 1: Schema/JSON tabs with Referenced/All fields filter and inline editing - Concept 2: Compact header with node identity + Referenced toggle, tree + JSON tabs, inline editing with copy affordance (recommended) - Concept 3: Full node identity row, Schema/Types/JSON tabs, filter icon on search Shared additions across concepts: - Expandable/collapsible tree grouped by top-level node - Inline value editing on leaf fields (click to edit, Enter/Escape to confirm) - Input/Output mode toggle per concept panel - Pro/con notes card below each panel with recommendation callout on Concept 2 - NodePropertyPanel: headerExtra slot for compact controls in the title bar Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

feat(storybook): split node patterns into focused stories

feat(apollo-react): add alignment guide variant pages for coworker review Extend AlignmentGuideLine with kind (edge/center) and matchedNodeIds so variants can distinguish match types and know which nodes a line corresponds to, without changing the baseline's visual behavior. Add five comparison sub-pages under Components/Canvas/AlignmentGuides, each a self-contained fork so the "decided" hook/overlay API stays stable while these are exploratory: - Center vs Edge Styling: distinct color/dash for center-only matches - Spacing Labels: px gap label alongside the guide line - Highlighted Match: ring highlight on the node(s) a line matches - Magnetic Snap: position snaps onto the guide instead of just showing it - Threshold Playground: live slider to compare match distance/feel