fix(service): drag transition travel times

[louisgreiner]

Replace #1131

Close #1008

[aiAdrian]

LGTM !

[aiAdrian]

There is a second related bug — if this has not yet been addressed, it should be tracked as a new issue.

I suspect that the same core problem is present: the times are not being calculated separately, or the backward travel time is simply forgotten during docking. This is similar to what happened during undock (and that PR only fixed the undock case).

next_bug.webm

chrome-capture-2026-06-15.webm

This PR can be merged .

[louisgreiner]

I fixed this bug #1132 (comment) in a fixup commit also.

[aiAdrian]

@louisgreiner Thank you for fixing this. Now I have a next issue found - asym.

Test:

netzgrafik.json

Undock looks good - but dock with asym. doesn't work correctyl:

asym_issue.webm

[aiAdrian]

LGTM!

[louisgreiner]

Indeed, the dock transition with asymmetric travel times does not work well :/ I fear there's no easy way to fix this. The expected behavior would be to split 17' into 7.5' - 2' - 7.5'

Anyway, this will be fixed naturally with the collapsed nodes feature