companion-app: catch up six days of panel drift before the native build

The phone-app codebase (companion-app/) hadn't been touched since
2026-08-11 - every panel fix and feature since then (HIG audit rounds,
receipt upload, trip editing, Inspektion forecast, ...) existed only in
the HA panel. Found while auditing what's needed for a real iPhone
build; user decision was to port everything now rather than ship a
stale app.

Six real, verified gaps (not blind copies of panel CSS/markup, which
doesn't transfer to the @audi-dash/ui component set):

- Battery voltage cutoff was still 13.2V, not the panel's 12.8V fix.
- Dead wlan_name field (WLAN trip detection was fully removed from the
  backend 2026-08-12) - removed from the adapter and the settings screen
  instead of leaving a form field that silently does nothing.
- No Inspektion forecast - added inspektionPrognose() alongside the
  existing oelwechselPrognose(), sharing a refactored core.
- Arbeitsweg pill used the design-system's "work" variant, which is
  documented as recoloring to red - stopped passing it, same fix as the
  panel.
- Trip creation only took Beginn/Ende/Art; extended with Startort/
  Zielort/Kilometerstand/Distanz via a new shared FahrtFelder.tsx.
- FahrtDetail.tsx was read-only - added an edit mode using the same
  shared fields, backed by a new DataMetricApi.fahrtAktualisieren()
  calling the backend service built earlier this session.

Explicitly checked and found not applicable: price rounding (already
2 decimals here), pull-to-refresh CSS (no native gesture to fix),
the panel's drag/paste receipt dialog (solves a desktop-browser problem
this native app doesn't have - the plain file picker already gets iOS's
native Files integration), and the purely cosmetic panel CSS fixes.

npm install run at the repo root (node_modules was incomplete/stale),
package-lock.json reflects the real dependency tree. Verified with
npm run typecheck (clean), npm run test (95/95, up from 90 - added
interaction tests for the new form and inspektionPrognose), and
npm run build (succeeds).

Co-Authored-By: Claude Opus 5 <[email protected]>

companion-app/src/api/index.ts

@@ -33,6 +33,21 @@ export interface TankvorgangFelder {
   kraftstoff?: string | null;
 }
 
+/** Eingabefelder für Fahrten - Namen wie beim Backend (fahrterkennung.py:
+    audi_dashboard_fahrt_manuell_anlegen/audi_dashboard_fahrt_aktualisieren).
+    Alles außer den Zeitpunkten ist optional: leer bleibt es liegen, bis das
+    Kilometerstand-Screening (§7.2) oder eine spätere Bearbeitung es füllt. */
+export interface FahrtFelder {
+  ts_start?: string;
+  ts_end?: string;
+  art?: "privat" | "arbeitsweg";
+  start_ort?: string | null;
+  ziel_ort?: string | null;
+  odo_start?: number | null;
+  odo_end?: number | null;
+  distanz?: number | null;
+}
+
 /** Bündelt die drei Bausteine und bildet die Fachvorgänge ab, die das alte
     Dashboard über hass.callService erledigt hat. */
 export class DataMetricApi {
@@ -94,15 +109,26 @@ export class DataMetricApi {
   }
 
   /** Legt eine Fahrt von Hand an — für Fahrten ohne automatische Erkennung. */
-  fahrtAnlegen(tsStart: string, tsEnde: string, art: "privat" | "arbeitsweg"): Promise<unknown> {
+  fahrtAnlegen(felder: FahrtFelder): Promise<unknown> {
     return this.warteschlange.einreihen(
       "pyscript",
       "audi_dashboard_fahrt_manuell_anlegen",
-      { ts_start: tsStart, ts_end: tsEnde, art },
+      { ...felder },
       "Fahrt eintragen",
     );
   }
 
+  /** Bearbeitet eine bestehende Fahrt, gleich ob automatisch erkannt oder von
+      Hand angelegt. */
+  fahrtAktualisieren(tripId: string, felder: FahrtFelder): Promise<unknown> {
+    return this.warteschlange.einreihen(
+      "pyscript",
+      "audi_dashboard_fahrt_aktualisieren",
+      { trip_id: tripId, ...felder },
+      "Fahrt ändern",
+    );
+  }
+
   fahrtLoeschen(tripId: string): Promise<unknown> {
     return this.warteschlange.einreihen(
       "pyscript",