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/ins-r47-doc-cannot.txt

@@ -0,0 +1,23 @@
+**Everything about how it looks can only be judged from the phone**, and the
+gradient ground adds to that list rather than shortening it.
+`verify-icon.sh` proves the adaptive icon's `<background>` resolves to a
+drawable carrying concept 04's six stops and its geometry; it cannot see a
+pixel. So: the home screen under the launcher's mask, the app
+drawer, recents, another app's share sheet — reading for **banding** on the
+OLED above all, since that is the one thing the vector form cannot dither its
+way out of, then the glow's weight under the Pixel's circle and how the falcon
+sits on a lit ground rather than a flat one — and then Wallpaper & style →
+Themed icons on, which swaps both layers for the monochrome one over a
+background the wallpaper picks: the one slot this ground never reaches, on
+the list so that a round about the background can be seen not to have moved
+it.
+
+**One consequence of this round is reachable without the launcher**, and it
+is the quickest of them to check. `MediaHub.appIcon()` in the media-session
+plugin draws whatever `getApplicationIcon()` returns into a 512 px bitmap and
+hands it to the lock-screen card as its large icon, for every track whose
+cover has not been decoded yet — so the card and the shade carry this ground
+now as well. Play a track with no cover and look at the card. Nothing else in
+the app reads the launcher icon, and the walk never reads the card's icon —
+only its `android.title` and the session's playback state — so no step
+changes meaning either way.