Standort-Kachel: Live-Fahrzeugposition auf der Übersicht

Neue Kachel oberhalb von "Zuletzt" mit echter Leaflet-Mini-Karte,
öffnet per Klick eine Vollbild-Standortansicht (Kartendarstellung
wählen, auf Fahrzeug/User zentrieren, beide zeigen) mit einem
ausziehbaren myAudi-Stil-Menü: Distanz zum Gerät, Adresse (Reverse-
Geocoding via Nominatim), fährt/steht/Letzter-Parkplatz-Status,
Tankfüllstand/Reichweite, Route- und Teilen-Aktionen.

Backend: STANDORT_TRACKER-Einstellung (device_tracker-Entity) plus
_standort()-Veröffentlichung, bewusst leer gelassen bis eine echte
GPS-Quelle (FMM003/flespi) angebunden ist - Kachel zeigt bis dahin
"kein GPS-Signal". Verifiziert in audi_ha_test mit einer manuell
gesetzten Test-Position.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

AGENTS.md

@@ -253,6 +253,29 @@ capacitor/iframe/browser (`umgebung.ts`), types + entity table (`types.ts`), fac
       viewport-anchored, not parent-relative) inside `@container (min-width:860px)`. Verified live at
       both narrow (mobile tab bar, full content) and wide (1144px container, grid side-nav,
       navigation clicks, settings back-arrow) — screenshots taken, no regressions found.
+- [x] Standort-Kachel (live vehicle GPS position on the Übersicht, above "Zuletzt") — done
+      2026-08-12. New tile with a real (non-fake) Leaflet mini-map, opens a fullscreen "Standort"
+      route on tap; fullscreen has 4 floating controls (map style, center-on-vehicle,
+      center-on-user, fit-both) and a draggable myAudi-style bottom sheet (peek/expand/close by
+      drag or tap, opens on vehicle-marker click) showing distance-to-user, address (client-side
+      reverse geocoding via the public Nominatim API — same "public API, no key, low single-
+      vehicle volume" reasoning as the existing Leaflet-CDN gap below), fährt/steht/"Letzter
+      Parkplatz" state, fuel/range, and Route (Google Maps deep link) / Teilen (Web Share API)
+      actions. Backend: new `STANDORT_TRACKER` entity-ID setting in `einstellungen.py` (device_
+      tracker with lat/lon attributes), published via a new `_standort()` helper in
+      `frontend_veroeffentlichung.py` — **left empty/unconfigured**, no live vehicle GPS source
+      exists yet (same FMM003/flespi gap as section B); the tile shows "Kein GPS-Signal vom
+      Fahrzeug" until that's wired up. Verified end-to-end in `audi_ha_test` with a manually
+      created `device_tracker.test_fahrzeug` test entity (tile, fullscreen map, and menu all
+      confirmed rendering/populating correctly); the device's own location (browser Geolocation
+      API) and the Route/Teilen deep links work independently of the vehicle-GPS gap. Pushed to
+      the Claude Design project (`c28a8d4d-ec4e-4178-9e49-ab5b90c02097`, "DataMetric360 Board")
+      for visual refinement — the JS/CSS ship functionally complete but visually plain
+      (placeholder vehicle-marker glyph, default `.aktion`/`.tile` styling); Claude Design's job is
+      polish, not structure. One known rough edge: reverse-geocoded address didn't resolve within
+      a few seconds in the `audi_ha_test` container (no crash, stays on "Adresse wird ermittelt …"
+      indefinitely) — likely just that container's outbound network to Nominatim specifically;
+      unconfirmed whether this reproduces on the real HA instance.
 - [ ] Fix documentation drift (statistics claim, INSTALL variable names, README gaps, obsolete
       TODO comment) — text-only changes
 - [ ] Harden `profil_lesen()` against missing/corrupt `fahrzeugprofil.json`