Remove Cupertino UI branches from shared primitives

Keep the existing Material rendering, semantics, and interaction paths while removing obsolete Cupertino imports, alternate widgets, and dynamic-color dependencies. Record focused verification and remaining fixture limitations for final integration.
This commit is contained in:
2026-11-11 20:05:58 +00:00
parent 3f05421e8b
commit 5c80f75211
19 changed files with 78 additions and 210 deletions
@@ -0,0 +1,17 @@
# Material cleanup: shared UI primitives
- Removed live Cupertino rendering from glass pills, resize grips, segmented
overflow, segmented press feedback, segmented pieces, floating tab buttons,
and destination labels. Existing `cupertino` compatibility arguments remain
where other lanes still pass them, but they no longer select a renderer.
- Replaced run status dynamic colors with `ColorScheme` roles and updated every
production caller. The status helper keeps an optional scheme for pure tests.
- Focused verification: `tool/memwatch/full.sh` over the seven named Material
and status/graph tests: 47 passed, 0 failed, peak 1555 MB.
- `tool/analyze.sh`: clean, 0 errors/warnings/infos.
- A broader exploratory run including `floating_bar_geometry_test.dart` failed
only in its obsolete CupertinoApp variants because those fixtures do not
provide MaterialLocalizations after the app became Material-only. Those
alternate-host cases remain for the manager's consolidated test cleanup.
- No browser capture was performed; these changes preserve existing Material
geometry and interaction paths rather than redesigning visuals.