Sorting more complex route relations completely fails

[skyper]

What steps will reproduce the problem?

1. Have a more complex bus route (Busroute_with_loops.osm.xz​)
2. Open relation editor
3. Sort relation with "Sort PT Route Members Relation Editor"

What is the expected result?

No action at all as the relation is properly sorted and tags are according to the wiki

What happens instead?

Order of stop and platform members is completely messed up and name=* and to=* are offered to change to incorrect values

Please provide any additional information below. Attach a screenshot if possible.

Please, by default, do not change name=* into something which is not documented in the wiki and use the from=* and to=* for sorting instead of changing the values.
For sure, do not mess up the order but stop if there are problems.
Additionally, sort action should result in only one change but atm I get two entries in the command stack.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2021-07-09 02:08:51 +0200 (Fri, 09 Jul 2021)
Revision:17970
Build-Date:2021-07-09 01:31:16
URL:https://josm.openstreetmap.de/svn/trunk

Plugins:
+ pt_assistant (1ff2e15)

[skyper]

proper sorted PTv2 relation

[skyper]

Still a problem.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2023-03-14 22:49:24 +0100 (Tue, 14 Mar 2023)
Revision:18693
Build-Date:2023-03-15 02:30:57
URL:https://josm.openstreetmap.de/svn/trunk

Plugins:
+ pt_assistant (1ff2e15)