Capture set — 2026-09-05

Screenshots and clips from a full emulator-to-emulator test run against the LIVE stack (api.ridekit.dev), not a seeded localhost. Intended for the app store listings, the docs, and ridekit.dev.

What is here

Known gaps, so nobody ships a bad asset

• rider/00-smoke-launch.png and driver/00-smoke-launch.png are launcher screenshots from a moment when the emulator was thrashing. Delete them.
• The two clips in video/ were recorded during the runs where dispatch was still failing, so they show "No drivers available" rather than a completed trip. They need re-recording now that the socket bug is fixed.
• The admin dispatch queue still carries a demo ride stuck in_progress for 47 days (#b7288340, Ankit Mehta / Juhu Beach). It is visible in admin/04-dispatch.png and admin/20-dispatch-ride-detail.png as "47d 4h" — seeded data that should be cleared or completed before these are used publicly.
• Fares render with paise (₹110.53). Every Indian ride-hailing app rounds to whole rupees on screen. Worth deciding before the store screenshots are cut.
• Destination search is not biased to the rider's city: typing "Bandra" in Mumbai returns Bandra in Bihar and Madhya Pradesh above other local matches (rider/05-search-typeahead.png).

How they were taken

scratchpad/ui.py drives the emulators by element (resource-id / content-desc) rather than by coordinates, so a layout change breaks the run loudly instead of tapping the wrong thing and screenshotting the result. admin-capture.mjs drives the live admin through Playwright, signing in via the real OTP flow and asserting each screen actually rendered — a screen that 404s or throws is a finding, not a picture.