Restore ordinary root launches with query parameters and verify Back intent
This commit is contained in:
@@ -56,3 +56,19 @@ replacement loads it; newer navigation wins afterward. Recreating without a new
|
||||
choice restores the old owner's last accepted chat, not its previous Settings
|
||||
location. Both same-instance fake stores and distinct SharedPreferences store
|
||||
instances sharing one logical key are covered.
|
||||
|
||||
## Manager integration
|
||||
|
||||
Settings category persistence uses the same resolved server scope as tab
|
||||
locations. Explicit Settings Back returns to the preserved pipeline detail,
|
||||
while tapping the Pipelines tab retains Settings. Ordinary root launches with
|
||||
query parameters also restore saved navigation; explicit app paths still win.
|
||||
The integrated browser flow verified Settings/Tools → Chat → Pipelines →
|
||||
Settings/Tools, then reopening `/` restored Settings/Tools again.
|
||||
|
||||
Focused integration checks passed 14 cases (`/tmp/memwatch/out.HMixOA`).
|
||||
An older template workflow assertion was updated to use explicit Back, since
|
||||
selected-tab taps now preserve location. Two centered-tab assertions failed on
|
||||
the unchanged previous release too (`/tmp/memwatch/out.m3tMaL`); they now verify
|
||||
the user-requested left alignment already shipped. No layout code changed for
|
||||
those assertion corrections.
|
||||
|
||||
Reference in New Issue
Block a user