9e218f755a
Remove alternate application hosts, page scaffolds, connection controls and icon metadata while preserving Material routing. Isolate navigation fixtures from native update plugins and retain separate startup-update regressions.
1.3 KiB
1.3 KiB
Material startup and shell cleanup
- Consolidated application startup, onboarding, routing pages, connection states, Search, Templates, Schedules, and the navigation shell onto Material composition on every platform.
- Kept legacy
cupertinoconstructor arguments optional/ignored where callers still pass them; no Cupertino widgets or platform host selection remain in the changed application paths. - Focused watchdog command ran the mirrored application/routing/navigation and
shell tests: 38 passed and 7 failed. The seven failures were teardown
assertions for the pre-existing 15-second
LaunchUpdateCheckertimer inPipelinesApp; no Material cleanup assertion failed. tool/analyze.sh: clean (exit 0).- No rendered capture was performed; this cleanup preserves the existing Material scaffold, bars, connection states, focus, and navigation semantics.
Manager recovery
The navigation and template-wiring fixtures were inadvertently invoking native update plugins. They now explicitly disable updates, while dedicated startup update tests retain and exercise the real update-check behavior.
The focused routing, app, schedules, template-wiring, split-bar, startup-update check and startup-update-flow tests passed: 39 passed, zero failed. No production update behavior was changed to hide the teardown failures.