# Material-only fixture cleanup Removed alternate Cupertino hosts and query switches from the search, saved-server, and artifact-list browser fixtures. Their existing Material routes, callbacks, text scaling, selection state, and retry behavior remain unchanged. Updated the capture-kit documentation to describe the single Material fixture surface. Focused verification: `artifact_visit_list_test.dart` and `artifact_visit_list_semantics_test.dart` passed (14 tests); `tool/analyze.sh` reported clean. No browser capture was run because the fixture chrome host was only simplified, not visually redesigned. ## Review follow-up Removed the remaining `platform=cupertino` branch from the full-app capture fixture and its web/native route helper signatures. The fixture now always constructs the Material app; the shared `PipelinesApp.cupertino` compatibility parameter remains untouched for other callers. Focused verification: the two artifact visit-list tests passed (14 tests), and `tool/analyze.sh` reported clean. The first attempted test command used stale paths and failed to load them; the corrected paths were then run successfully. ## Review follow-up Removed the capture CLI's obsolete `--platform` option and URL forwarding, including the script/example `platform` field. Capture routes now expose only the Material fixture while retaining theme, search, sizing, and fixture params. Focused verification: `artifact_visit_list_test.dart` and `artifact_visit_list_semantics_test.dart` passed (14 tests); `tool/analyze.sh` reported clean. `node tool/capture/capture.mjs --help` no longer lists a platform option, and no platform/Cupertino capture option remains under `tool/capture`.