Don't use guiding mode if user wants navigation mode (with BRouter)
When navigation mode is commenced with offline BRouter as the data source, but there are no turns (waypoints/ navigation commands) along the way, Locus decides it knows better than the user and enters guiding mode instead of navigation mode.
Note it appears (in my limited testing) this behavior only affects navigation when using BRouter as the navigation data source.
This feature? has caught out many users, myself many times, wasted lots of online discussion, chasing tails, going around in circles.
A workaround for an otherwise problematic track is that one single waypoint/ turn at road junction/ navigation command is required for correct operation. Any point will do! So, my suggestion is simple: if the user wants navigation, then use the navigation mode. Maybe internally, Locus can create a hidden point at the beginning or end of the track to be followed if need be, but the user shouldn't need to know or care about these details.