# Standard back navigation ## Source and verification - Restored Flutter's Android predictive-back transition in both themes. The custom Android slide omitted Flutter's gesture observer; real-app composition tests proved gesture start was not handled before restoring the native builder. - Removed the Android exit-confirmation dialog and direct SystemNavigator.pop workaround. Back at a list root falls through to the platform. - Kept detail-route ownership until PageRoute.completed. Previously push's returned future cleared ownership at pop start; an owner rebuild during the reverse animation could push another page or notify listeners during build. - Regressions cover Pipelines/Runs/Chat: actual system-back dispatch, dialog first, canceled and committed predictive gestures, list restoration and platform exit. A separate lifecycle regression rebuilds the owner during an ordinary pop and a committed gesture. Existing deep-link, wide-screen and browser route tests pass. - `FLUTTER=/Users/alan/development/flutter/bin/flutter sh tool/check_full.sh`: clean analysis, all 1,744 tests pass. - `flutter build web -o build/navigation_web`: pass. - `node tool/detail_navigation_probe.mjs build/navigation_web build/navigation-evidence`: 12 checks, 9 captures; real Chrome at 390x844 exercises list selection, browser Back/Forward, toolbar Back and repeated opening/closing for all three features. Captures and result.json are in `app/build/navigation-evidence/`. The chat fixture explicitly lacks chat_shells; its visible unavailable message is fixture evidence, not a navigation failure. - Android device behavior is unverified. Gesture coverage dispatches Flutter's actual flutter/backgesture platform messages in widget tests, not on a device. ## Delivery The user explicitly approved overriding the app's no-deploy/no-APK rules for the requested web/server installation and APK publication, without device tests. Deployment results are recorded after running the installers.