3.9 KiB
3.9 KiB
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 inapp/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.
Source landed on main as 7f88f14a; ancestry checked after commit. Unrelated
untracked .claude/ remains untouched (the installer therefore labels the server
build dirty).
./install --web-port 8083: built and installed the Docker web bundle and native server. Port 8082 belongs to an unrelated scratch server and was not disturbed. No pipeline definitions or versions were created or changed.- The old server/ntfy were managed by separate legacy LaunchAgents, not the
installer supervisor. After checking no executing runs or active chats, the
legacy server/ntfy agents were disabled/unloaded (their plist files retained),
and
net.a-wan.pipelinesnow supervises server/ntfy/web on 8080/8090/8083. Server ping identifies commit7f88f14a; the original OpenCode endpoint and existing database/artifacts are retained. The legacy web agent remains running so existing public URLs do not change. - Installation/config/binary/SQLite rollback material:
~/.local/share/pipelines/backups/navigation-20261024-014504/. - Copied the installed web bundle to the existing preview's root using a rename
swap. Rollback:
app/build/web-before-native-navigation-1792802826/. - Authenticated JS byte hashes match the installed bundle at localhost ports
8083, 8095, 8098 and the existing tailnet HTTPS ports 8443 and 8096. All five
still reject unauthenticated bundle requests. JS SHA256:
49915ab0084e9b6437db2e8151e07397d187ab064a23687664cbf09ea7410a9e. - Reran all 12 browser checks against the Docker-built installed bundle through
isolated fixtures; captures/results:
app/build/navigation-deployed-evidence/. ./install --apkbegan the Docker APK build. The tool invocation timed out after 120 seconds but left its container building. Waiting for that exact container found a later Gradle daemon failure and confirmed Docker OOM event. No APK from that failed build was published. Docker build-only memory limits are corrected in49b92ee0; publication proceeds with the combined follow-up release tracked inchat-stage-debug-queue.md.