App 2.27.3: read the cruise control target speed, log it raw

The head unit names a vendor float AAD_EPTCCTRGTSPD (0x2160A15B),
the cruise control target speed by its name. EVHardware reads it raw;
the Logs tab lists each change with time, speed and gear, to establish
the unit and the off value on the car. Emulator only (absent there).

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

SPECS.md

@@ -131,6 +131,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-24 — App 2.27.3 (branch `styles-retro-future`): first step to the cruise control (ACC)
+  set speed. The head unit's `CarAdvancedAssistedDrivingManager` names a vendor float
+  `AAD_EPTCCTRGTSPD` = `0x2160A15B`, by its name the powertrain's cruise control target speed;
+  nothing else in the decompiled SDK looks like a set speed (the other ACC properties are
+  objects ahead: distances, relative speeds). EVHardware reads it raw
+  (`getCruiseTargetSpeedRaw`, `EnergySnapshot.cruiseTargetSpeedRaw`; read-only), and the Logs
+  tab lists every change with time, speed and gear (`CruiseLog`, last 12). Unit and the value
+  while cruise control is off are unknown until read on the car; the dashboards show nothing of
+  it yet. Emulator: the property is absent there, one "unread" line, no crash. Not tried on the
+  car.
 - 2026-10-24 — App 2.27.2 (branch `styles-retro-future`): Terminal can be drawn in the accent
   colour too (text in its light shade, the command line in the accent, plain black; the low
   battery stays amber). Instead of separate "(accent colour)" entries, Retro and Terminal are one