Problem:
For IF branch flows that go directly from a split to a merge, the builder applies the branch from anchor but loses the branch to anchor. The next describe changes branch anchor output, for example replacing an intended destination side with the default destination.
Expected:
Branch-level @anchor(... true: (...), false: (...)) metadata should preserve both origin and destination sides for split-to-merge shortcut flows.
Impact:
Roundtrip output drifts for visually meaningful branch anchors.
Proposed fix:
Pass the branch anchor as both origin and destination anchor when constructing split-to-merge shortcut flows.
Problem:
For IF branch flows that go directly from a split to a merge, the builder applies the branch
fromanchor but loses the branchtoanchor. The next describe changes branch anchor output, for example replacing an intended destination side with the default destination.Expected:
Branch-level
@anchor(... true: (...), false: (...))metadata should preserve both origin and destination sides for split-to-merge shortcut flows.Impact:
Roundtrip output drifts for visually meaningful branch anchors.
Proposed fix:
Pass the branch anchor as both origin and destination anchor when constructing split-to-merge shortcut flows.