# Android root double-back exit The latest request replaces the prior single-back exit rule at Home/tab roots. Only native Android Pipelines, Runs (including filtered lists), Chat and Settings roots intercept the first Back, showing the standard transient SnackBar “Press back again to close”. A second Back within two seconds falls through to the platform; no custom exit call or confirmation dialog is introduced. The shell PopScope advertises whether root Back is currently handled, preserving the platform's predictive back-to-home path for the second press. Detail/stage, Search, Templates, Schedules and dialog pops keep their existing navigation. Route changes and newly pushed dialog/detail routes clear the armed window. Web and iOS do not enable this guard. No connection or Settings source changed. ## Evidence - Before implementation: updated narrow/wide regression expectations failed in seven cases because the first root Back called `SystemNavigator.pop`. - Focused navigation suite: 26 passing tests (`app_router_test.dart`, `pipelines_app_test.dart`, `detail_navigation_test.dart`). Includes expiry, navigation/dialog reset, iOS bypass, browser-route updates, detail one-pop, predictive cancellation/commit, and native exit channel assertions. - `flutter test test/application`: 100 passing tests. - `flutter analyze`: no issues. - No APK build, server/deployment changes, ADB or device use. Actual mobile behavior and rendered browser/mobile captures remain unverified.