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-r32-mobile-effect.txt

@@ -0,0 +1,10 @@
+    /* ── when the library landed, for the record ──────────────────────
+       Home gates its landing screen on lib.loaded, so this is the number a
+       launch is actually felt as, and it is the one the phone leg prints.
+       `boot` is a plain object and never a rune, so the write cannot feed
+       the effect back into itself; untrack says so out loud. */
+    $effect(() => {
+        if (!lib.loaded) return;
+        untrack(() => { if (boot.libMs == null) boot.libMs = Math.round(performance.now() - boot.t0); });
+    });
+