feat(apollo-react): add task breakpoints to case-management StageNode [MST-12196]

[alfredo-mruiz]

Description

Adds a task-level breakpoint marker to the case-management StageNode (MST-12196).

Each task (sequential, ad hoc, event-driven) can show a breakpoint: a solid red dot at the top-left corner of the task card, matching the Flow/BPMN canvas breakpoint (DebugBreakpoint) — 14px, canvas error color, no border or animation. The marker is display-only: it renders only when the task has a breakpoint set and never intercepts pointer events (pointer-events-none).

Following Flow's interaction design, breakpoints are added/removed exclusively through the task's right-click / task menu (no hover affordance, no click-on-dot), so task and stage hover states stay uncluttered.

Pause is independent of the marker: when the run is paused on a task, the card shows its amber Paused border and pause status icon (driven by the task's execution status); the breakpoint dot itself does not change.

Public API (additive): the only shipped contract is StageTaskExecution.breakpoint?: boolean, which drives the marker. Add/remove is wired by the consumer through the existing task context-menu callback (getTaskContextMenuItems). No new StageNode props are introduced.

When the marker shows

flowchart LR
    MENU["right-click / task menu<br/>Add or Remove breakpoint"] --> APP["consumer updates<br/>execution.taskStatus[id].breakpoint"]
    APP --> BP["execution.taskStatus[id].breakpoint === true"]
    BP --> DOT["solid red dot<br/>(sequential / ad hoc / event-driven)"]

Loading

Demo

apollo-ui-cm-breakpoint.mov

Storybook: Components/Nodes/StageNode → three breakpoint stories:

• Interactive (click or right-click) — full lifecycle in one stage (a passed+solid task, a paused+pulsing task, and idle tasks to hover/add/remove).
• Across task types — sequential, ad hoc, and event-driven.
• Restricted (canBreakpoint predicate) — only allowed tasks show the affordance/menu.

Risks of rolling out

• Low. Additive and opt-in: a stage that passes no breakpoint data renders exactly as before.
• No feature flags added or removed; no API removed (only StageTaskExecution.breakpoint added).
• The marker is pointer-events-none, so it cannot block clicks/drags on the task card.

Feature flag

• If this introduces a new feature flag, make sure first to create it in Gitops and specify the flag in alpha, staging and prod

No new feature flag introduced.

Tests

• I validated theme and locale
• I added unit tests
• I added component tests
• I added Playwright E2E tests
• I manually tested my changes or added other kinds of tests (Please add details below)

Details:

• Unit: TaskBreakpointDot.test.tsx — renders only when a breakpoint is set, is pointer-events-none, and is static (no animation).
• Component: StageNode.test.tsx covers the ad hoc and event-driven paths; DraggableTask.test.tsx covers the sequential path.
• Manual: exercised the three Storybook stories.

[github-actions]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (PT)
apollo-design	🟢 Ready	Preview, Logs	Jul 19, 2026, 08:54:14 PM
apollo-docs	🟢 Ready	Preview, Logs	Jul 19, 2026, 08:54:14 PM
apollo-landing	🟢 Ready	Preview, Logs	Jul 19, 2026, 08:54:14 PM
apollo-vertex	🟢 Ready	Preview, Logs	Jul 19, 2026, 08:54:14 PM

[github-actions]

Dependency License Review

• ✅ 1950 package(s) scanned
• ✅ No license issues found
• ⚠️ 2 package(s) excluded (see details below)

License distribution

License	Packages
MIT	1720
ISC	89
Apache-2.0	55
BSD-3-Clause	27
BSD-2-Clause	23
BlueOak-1.0.0	8
MPL-2.0	4
MIT-0	3
CC0-1.0	3
MIT OR Apache-2.0	2
(MIT OR Apache-2.0)	2
Unlicense	2
LGPL-3.0-or-later	1
Python-2.0	1
CC-BY-4.0	1
(MPL-2.0 OR Apache-2.0)	1
Unknown	1
Artistic-2.0	1
(WTFPL OR MIT)	1
(BSD-2-Clause OR MIT OR Apache-2.0)	1
CC-BY-3.0	1
0BSD	1
(MIT OR CC0-1.0)	1
MIT AND ISC	1

Excluded packages

Package	Version	License	Reason
@img/sharp-libvips-linux-x64	1.2.4	LGPL-3.0-or-later	LGPL pre-built binary, not linked
khroma	2.1.0	Unknown	MIT per GitHub repo, missing license field in package.json

[Copilot]

Pull request overview

Adds task-level breakpoint visualization and interaction to the case-management StageNode in apollo-react, enabling consumers to show/toggle per-task breakpoints (click + optional right-click menu wiring) across sequential, ad hoc, and event-driven tasks.

Changes:

• Introduces TaskBreakpointDot (ghost/set/paused-pulse states) and wires it into all StageNode task renderers.
• Adds additive API surface: StageTaskExecution.breakpoint?: boolean, StageNodeBaseProps.onToggleTaskBreakpoint?, and StageNodeBaseProps.canBreakpoint?, plus resolveTaskBreakpointToggle helper.
• Adds unit/component tests and Storybook stories covering breakpoint rendering and interaction.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/apollo-react/src/canvas/components/StageNode/TaskBreakpointDot.tsx	New breakpoint marker component (display-only + interactive modes) with hover/focus ghost, active dot, and paused pulse.
packages/apollo-react/src/canvas/components/StageNode/TaskBreakpointDot.test.tsx	Unit tests for marker rendering, labeling, click toggling, blur behavior, and pulse gating.
packages/apollo-react/src/canvas/components/StageNode/StageNodeTaskUtilities.ts	Adds resolveTaskBreakpointToggle helper to centralize per-task eligibility logic (handler present, not placeholder, passes predicate).
packages/apollo-react/src/canvas/components/StageNode/StageNodeSequentialTaskGroups.tsx	Passes resolved breakpoint toggle handler into sequential task rendering.
packages/apollo-react/src/canvas/components/StageNode/StageNodeEventDrivenTaskGroups.tsx	Passes resolved breakpoint toggle handler into event-driven task rendering.
packages/apollo-react/src/canvas/components/StageNode/StageNodeAdhocTaskGroups.tsx	Passes resolved breakpoint toggle handler into ad hoc task rendering.
packages/apollo-react/src/canvas/components/StageNode/StageNode.utils.test.ts	Adds unit coverage for resolveTaskBreakpointToggle.
packages/apollo-react/src/canvas/components/StageNode/StageNode.types.ts	Extends public types with breakpoint execution flag and optional breakpoint toggle/predicate props.
packages/apollo-react/src/canvas/components/StageNode/StageNode.test.tsx	Component tests ensuring breakpoint marker presence for ad hoc + event-driven tasks when armed, and absence when unarmed.
packages/apollo-react/src/canvas/components/StageNode/StageNode.stories.tsx	Adds interactive breakpoint stories/playground demonstrating lifecycle and task-type coverage.
packages/apollo-react/src/canvas/components/StageNode/EventDrivenTask.tsx	Renders TaskBreakpointDot within event-driven task cards and adds group class for hover/focus styling.
packages/apollo-react/src/canvas/components/StageNode/DraggableTask.types.ts	Adds onToggleBreakpoint prop to support interactive breakpoint toggling in draggable tasks.
packages/apollo-react/src/canvas/components/StageNode/DraggableTask.tsx	Renders TaskBreakpointDot within draggable task cards and adds group class for hover/focus styling.
packages/apollo-react/src/canvas/components/StageNode/AdhocTask.tsx	Renders TaskBreakpointDot within ad hoc task cards and adds group class for hover/focus styling.

[github-actions]

📊 Coverage + size by package

Per-package coverage and bundle size on this PR. New-line coverage = of the source lines this PR adds or changes, the % hit by tests.

Package	Coverage	New-line coverage	Packed (gzip)	Unpacked	vs main
@uipath/apollo-core	9.0%	—	43.82 MB	57.31 MB	±0
@uipath/apollo-react	37.2%	8.5% (4/47)	7.38 MB	28.15 MB	+1.1 KB
@uipath/apollo-wind	41.0%	—	397.5 KB	2.58 MB	−7 B
@uipath/ap-chat	85.8%	—	43.43 MB	55.92 MB	±0

_{"Coverage" is each package's own coverage.include scope (e.g. apollo-core instruments only scripts/). "Packed"/"Unpacked" come from npm pack --dry-run and only cover built packages — "—" means not measured this run (package not affected / not built). "vs main" is the packed (gzipped) delta against the last successful main build (the package-sizes artifact from the Release workflow); "—" there means no main baseline was available this run. The baseline is main's latest build, not this PR's exact merge-base, so it includes any drift since the branch diverged. Packages with no vitest config are omitted.}

[github-actions]

📦 Dev Packages

Package	Status	Updated (PT)
@uipath/apollo-react@4.65.2-pr917.ba5f86e	🟢 Published	Jul 19, 2026, 08:52:47 PM

[Copilot]

Pull request overview

Copilot reviewed 14 out of 14 changed files in this pull request and generated no new comments.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

packages/apollo-react/src/canvas/components/StageNode/TaskBreakpointDot.tsx:19

• The PR description states that the breakpoint dot is interactive (ghost on hover/focus, click-to-toggle, pulsing when paused) and mentions new StageNode APIs (onToggleTaskBreakpoint, canBreakpoint, resolveTaskBreakpointToggle). In the current implementation, the dot is explicitly display-only (pointer-events-none), renders only when active is true, and has no paused/ghost/toggle behavior (and there are no references to those new APIs in the StageNode directory). Please either update the PR description to match the shipped behavior, or implement the described interactive/pulsing behavior and APIs before merging so consumers aren’t misled about the contract.

 * animation. Like Flow, the marker does not change when the run is paused on the
 * task. The paused state is conveyed separately by the card's amber border and
 * the pause status icon, both driven by the task's execution status.
 *
 * Display only. Breakpoints are added and removed through the task's right-click