App 2.7.1: voice-key double press works; floating button removed

The car's key report, from the on-screen key log in 2.7.0:
android.intent.extra.hardkey.keycode = 287 (Integer),
android.intent.extra.hardkey.down (Boolean; one report on press, one on
release) and android.intent.extra.hardkey.longpress (Boolean). 2.7.0
only looked for short names like "keyCode", so it never found the code.
SteeringKeyReport now matches extras by the last part of their name,
case-insensitively, and is Android-free; its tests include the exact
double press logged on the car (releases 279 ms apart). Replayed in the
car's format on the emulator: double press opens the app, single and
long presses do not.

The floating button is removed (class, geometry and test, the overlay
permission, setting, switch and strings): it did not show over the MG4
launcher.

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

SPECS.md

@@ -114,6 +114,10 @@ tyre pressures, GPS (lat, lon, elevation, heading) and the is_* flags. It does *
   INGEST_TOKEN) into git and pushed it. Commit amended and force-pushed; both values regenerated in
   the now gitignored `k8s/secrets.yaml` (since moved to `k8s/secrets/secrets.yaml`, outside
   `kubectl apply -f k8s/`). Filled-in secrets live only there from now on.
+- 2026-10-17 — App 2.7.1: the voice key works. The car's key report, read off the on-screen log:
+  `android.intent.extra.hardkey.keycode` (Integer), `.down` (Boolean, a report per press and per
+  release), `.longpress` (Boolean). 2.7.0 looked only for short names and never found the code.
+  Floating button removed (it did not show over the MG4 launcher).
 - 2026-10-17 — App 2.7.0: a double press of the steering wheel's voice key (code 287) opens the
   app, from the head unit's `com.saic.keyevent.hardkey.report` broadcast. Its extras are not
   documented; the usual names are tried and every report is listed raw on the Logs tab. The