1.9 KiB
F2 — Adaptive shell
Manager browser acceptance
The initial capture attempt failed because the fixture served its index with
binary MIME. Corrected the fixture MIME and navigation assertions; the real
Chrome run now passes actual Pipelines → Runs → Chat → Settings → Pipelines
navigation, checking the selected destination body (not only navigation labels).
Captured and inspected at 390×844 and 1280×800:
/private/var/folders/jp/q0qvjyg54fl_c5vhhk1ylz2m0000gn/T/opencode/f2-shell-{phone,phone-runs,phone-settings,desktop}.png.
These show the native Cupertino shell on a macOS browser with explicitly labelled
unimplemented feature bodies. They do not prove feature parity or mobile behavior.
Reproduce from app/ using OPENCODE_ARTIFACT_DIR=<directory> node tool/shell_probe.mjs
after flutter build web. Earlier missing-capture statements below are historical.
Implemented standard adaptive navigation for Pipelines, Runs, Chat and Settings.
Material uses a bottom NavigationBar below 600 logical pixels and a labeled
NavigationRail at wider widths. Cupertino uses the native navigation bar and
tab bar. MyApp chooses Cupertino on iOS/macOS, leaves Material system light/dark
themes active elsewhere, and accepts injectable WidgetBuilder bodies through
AdaptiveShell; unregistered destinations are explicitly marked Not implemented.
Verification
flutter test test/widget_test.dart: passed (narrow/wide, 2x text scale, Cupertino controls and injected destination body).flutter analyze: passed, no issues.- Follow-up verification: widget tests now cover state retention across tab
switches and Cupertino safe-area insets.
flutter build websucceeds. - Browser interaction/capture remains unverified: the local Chrome DevTools probe did not complete, so no rendered evidence is claimed. Mobile targets are unverified.
No API capabilities are asserted or mocked. No dependencies were added.