App 2.19.3: update log on the Logs tab

Every update and install step, with the platform's own result, kept
across the restart an install causes, so a failed install on the car
can be read off the screen.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LhzAVaUyqcw5PkGjz4mWW6

SPECS.md

@@ -118,6 +118,16 @@ tyre pressures, GPS (lat, lon, elevation, heading) and the is_* flags. It does *
   confirmed car facts, app structure, UI conventions, build/test/ship, documents. It replaces
   upstream's EVABRPUploader text. The test emulator is now in the flake: `nix run .#car-emulator`
   (Android 9 AOSP at 1920×720, 160 dpi; the car build installs as the system user — checked).
+- 2026-10-23 — App 2.19.3: an update log on the Logs tab, above the uploads. A USB install on the
+  car ended in an installer message about a broken package, while the same APK installed through
+  the Bluetooth-settings route; the message was only a toast and logcat, so its exact words are
+  lost. Now every step is kept (last 10, survives the restart an install causes): file found with
+  its size, SHA-256 match, the package manager refusing to parse, a failed installer session with
+  its exception, bytes handed to the installer, the platform's result in its own words, and "Now
+  running <version>" on the first start of a new version. On the emulator, with a FAT image as a
+  removable volume (like the car's stick), the USB install worked silently and the log showed the
+  whole sequence; a truncated APK with a matching hash was refused at the package check, logged.
+  The car's failure is not reproduced or explained yet.
 - 2026-10-23 — App 2.19.2: Settings → "Full screen for CarPlay (experiment)". The Logs tab showed
   CarPlay on the car as `com.allgo.carplay.service/.CarPlayActivity`, an ordinary activity. The
   switch adds that package to `immersive.full` in Android 9's `policy_control` global setting