style: drop the duplicated and speculative navigation commentary

The reason interceptBack exists was written twice, at the call site and
where the parameter is defined. Kept the one next to the definition.

AppRoutes named :feature:<name>:api as the eventual home for the route
types. Those modules do not exist and may not be called that; a comment
that describes a plan rather than the code ages into a wrong one.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MdKgoKZbL5K1wsn1WsES26
This commit is contained in:
Moe Hamade 2026-08-26 00:32:12 +03:00
parent c7d551e2af
commit eb8c2e7446

View File

@ -10,10 +10,6 @@ import com.bitchat.android.onboarding.OnboardingState
* results and adapter state changes rather than by the user navigating, and the
* app has never supported going back from one step to the previous one. Giving
* each step its own entry would invent a history that does not exist.
*
* These live in :app because both destinations still need collaborators the
* Activity owns. They move to :feature:<name>:api as those features become
* modules.
*/
data object OnboardingRoute : NavKey