android: the handoff — the pending rounds, the pipeline, and what is unverified

Everything written this session that has not been through the device: rounds 43
to 48 (each patch adversarially verified, 43's transient-notice expectation
fixed), a partial round 49, the pipeline scripts, the Android Auto design and
the icon comparison mock. Also the two harness changes that were never A/B'd —
adaptive waits, which may only shorten a declared wait and never lengthen it,
and a ship that runs the mock walk and the deploy at the same time. The A/B and
its 255-step baseline are in handoff/tools; main stays at what the phone has
actually walked.

handoff/rounds/commit-msg40.txt

@@ -0,0 +1,29 @@
+android: what the device has actually been tested for — the map, and the steps it could close
+
+Most of this port is proven against an object in memory and only some of it
+against the phone, and nobody had written down which was which. Writing it
+down found four phone steps — `library-ambience`, `queue`, `lyrics` and
+`community` — named and screenshotted with no entry in `PHONE_EXPECT` at all,
+and the driver reads a missing key as a pass, so all four had been green since
+the rounds that wrote them; they have assertions now, tolerant of Kyle's own
+library and of nothing else.
+
+Thirty-three more steps move onto the device: everything that can be proven
+there without downloading, joining, sending, signing in or writing to his
+library. The library's shape and its sort (nav state, not config), a local
+track's sheet off a real path, Search's recents out of this WebView's own
+storage, a queue row's sheet opened and not tapped, the walk's own playlist
+with a row removed and put back by Undo — the first round trip that stash has
+made through real SQLite — the import review's Keep switch restored before the
+draft is created, the sleep timer set and put out by the next step, the
+stream-cache chip and the Wi-Fi-only guard read first and restored last, and a
+port the core has to refuse.
+
+ANDROID.md carries the map beside Verifying: what the device walk proves (121
+named steps, up from 88, plus the seven things after the loop that no mock can
+do), what stays mock-only and why — needs `__ssMock`, needs a fresh install,
+needs a viewport the phone walk refuses to set, needs the dev flavour, or
+would download, join, or destroy his data — which six of the new steps are
+conditional on what his own library happens to hold, and what still needs a
+person. No product code in this round: four inserts in the phone half of
+smoke.mjs, one in the doc.