28 lines
1.7 KiB
Markdown
28 lines
1.7 KiB
Markdown
# Settings registered in the normal app
|
|
|
|
- `/settings` mounts the landed SettingsScreen with the app-owned client, not a
|
|
second socket. Embedded mode leaves the single native bar to the shell.
|
|
- Destinations are initialized on first visit and kept mounted thereafter; an
|
|
unvisited Settings screen issues no hidden ping or preference read.
|
|
- Session Retry uses the transport's current validated endpoint, including one
|
|
selected in Settings, rather than reverting to the bootstrap server. A native
|
|
missing-endpoint gate can be cleared by a successful Settings configuration.
|
|
- Real CupertinoApp dark-host capture exposed Material fallback text colours.
|
|
Settings now resolves typography/semantic colours from its actual native host.
|
|
The new dark-label regression failed before this correction and passes after.
|
|
No fixed font, palette or component dimensions were added.
|
|
|
|
## Verification
|
|
|
|
- 516 integrated Flutter tests pass; analyzer clean; normal-entry web build pass.
|
|
- Widget coverage mounts real Material and dark Cupertino app composition,
|
|
asserts one bar, no background Settings ping before visiting, shared socket,
|
|
and resolved server build after ping. Endpoint-change Retry has a regression.
|
|
- Extended normal-entry Runs CDP fixture answers real ping and drives Settings
|
|
in both hosts. Probe passes all existing history/drop/reconnect checks plus
|
|
Settings navigation and single-socket checks:20 captures. Both registered
|
|
phone screenshots inspected; dark Cupertino labels are readable after fix.
|
|
- Evidence in approved temp/settings-wired-browser and corresponding logs.
|
|
- Authenticated production-data interaction and Android/iOS remain unverified.
|
|
No real server endpoint/workspace preferences were changed by the fixtures.
|