Auditor adds nodes to wrong Classify branch

Reproduce the Classify-branch flow using the workflow designer and its node config panel, focusing on the stacked "+" connectors. First check whether the workflow designer API/model can identify a target branch; otherwise verify the upstream connection label after adding a node. Done means downstream nodes consistently attach to the selected branch without user intervention.

Auditor adds nodes to wrong Classify branch consistently

Observed during: mcs-workflows audit (UC4/UC5), 2026-06-20

Problem: When clicking the "+" connector on a Classify node branch to add a downstream node (e.g., Agent), the auditor added the node to the wrong branch twice (Quote Request instead of Supplier Delay). The user had to intervene both times.

Root cause: The "+" buttons for each Classify branch are vertically stacked and close together on the canvas. Coordinate-based clicking is unreliable because:

• Branch order can shift depending on zoom/scroll state
• The click target area is small
• No verification is done after the node is added to confirm correct placement

Suggested fix:

1. After adding a node via "+", verify which branch it connected to by reading the upstream connection label in the node config panel
2. If wrong branch, delete and retry with adjusted coordinates
3. Consider using the workflow designer API/model to specify target branch programmatically rather than coordinate clicking
4. Alternatively, click the branch label text first to highlight/select the branch, then look for the "+" appearing specifically on that branch