Not everything can be a priority.
Developers have been asking for some time when there is going to be an official navigation/routing solution for Jetpack Compose. The current answer is that the Jetpack Navigation component will fill that role. However, having a native Compose implementation of Navigation is somewhat decoupled from Compose development itself. Or, as Adam Powell put it:
“We don’t consider it blocking for alpha, beta or 1.0, partially because it’s fairly straightforward to create a ComposableFragment and use that with the existing library. We’re focusing on the fundamentals that make such integrations easy to write first.”
This is not to say that navigation/routing is not a concern, just that it is an independent effort from Compose itself and may ship on an independent timeline (though, presumably, after Compose itself ships).