App 2.32.1: drop the cruise control reads; the recorder becomes general

The 2.32.0 recording (ACC set to 101, 90 and 80 km/h behind another car)
found none of it among 1,194 values: the head unit does not get the ACC
data. Removed the cruise log and the set-speed read (EVHardware is as
before 2.27.3); the finding is under "Signals the car does not provide".
The recorder stays as the Signal recorder, for finding other signals.

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

SPECS.md

@@ -70,6 +70,13 @@ tyre pressures, GPS (lat, lon, elevation, heading) and the is_* flags. It does *
 - **Pack energy (`soe`) and capacity:** not published. The Live dashboard computes energy in pack
   as SOC × usable capacity, from the hidden dashboard constant `usableKwh` (50.8 kWh for the
   51 kWh battery) in `k8s/grafana/dashboards/live.json`.
+- **Adaptive cruise control (set speed, distance to the car ahead, ACC state):** the head unit gets
+  none of it (SWI68, checked 2026-10-25). The `AAD_*` properties of `CarAdvancedAssistedDrivingManager`
+  exist and answer, but stay at their defaults with ACC engaged behind another car
+  (`AAD_EPTCCTRGTSPD` `0x2160A15B` 0.0, `AAD_ACC_OBJ_*` 0.0 / -128.0, modes 0). A signal recording
+  of all 1,194 values while the set speed was 101, 90 and 80 km/h shows none of those numbers
+  (also tried as m/s, mph and ×2/×10/×16/×64) outside the actual speed, and the ACC buttons send
+  no key broadcast. Most likely only the instrument cluster has it.
 
 ## To do
 
@@ -131,6 +138,18 @@ 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-25 — App 2.32.1 (branch `styles-retro-future`): the cruise control work ends. The ACC
+  recording of 2.32.0 (ACC set to 101, 90 and 80 km/h, a car ahead) found nothing: see "Signals
+  the car does not provide". Removed: `CruiseLog` and its section on the Logs tab, and in
+  EVHardware the set-speed read (`getCruiseTargetSpeedRaw`, `EnergySnapshot.cruiseTargetSpeedRaw`),
+  `readAccDebug` and `ReadFailureLog.reason` — EVHardware is again as before 2.27.3. The old log
+  files are deleted on start. The recorder stays as a general tool, renamed **Signal recorder**
+  (`SignalRecorder`, `SignalRecording`, `signal-recording-<time>.txt`). What the recording did
+  show, for later: `0x2140A15A` (`AAD_ELECVEHSYSMD`) flips 3/7 with accelerating and slowing,
+  `0x21409326` is the turn indicator (0 off, 1 and 2 the sides), `0x2140159D` (unnamed) shows
+  values like 300–1425 only while slowing down, `0x2140B970`/`0x2140B97B` are the parking sensors
+  in R. A full capture takes about 5 s on the car. Tests and lint; emulator: the recorder starts,
+  stops and saves under its new name. Not tried on the car.
 - 2026-10-25 — App 2.32.0 (branch `styles-retro-future`): the **ACC recorder** on the Logs tab.
   The 2.31.1 log on the car (a drive with ACC engaged behind another car) showed every assist
   property constant: `cc 0.00`, `ica 0`, `tja 1`, `sas 0`, `sam 0`, `obj 0.00`, `dist 0.00`,