INSTALL.md an Setup-Menü und FMM003 anpassen

Ersetzt die veralteten Installationsschritte (manuelles Eintragen von
WLAN_SENSOR/TommiG1-Entity-IDs in einstellungen.py) durch eine Anleitung
für das neue Setup-Menü in der App und die aktuellen FMM003-Feldnamen
(ZUENDUNG_SENSOR, STANDORT_TRACKER, BATTERIE_SENSOR). AGENTS.md entsprechend
nachgeführt.

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

AGENTS.md

@@ -149,15 +149,6 @@ capacitor/iframe/browser (`umgebung.ts`), types + entity table (`types.ts`), fac
 - `homeassistant/README.md:99`, `INSTALL.md:204`, and the header comment
   `audi-dashboard-app.js:13-15` claim the statistics view shows sample numbers — **false**;
   `vStat()` computes real values from `TRIPS`/`FILLS`.
-- `INSTALL.md` step 4 names variables that no longer exist (`DOORS_SENSOR`, `WINDOWS_SENSOR`,
-  `LOCK_ENTITY`, `BATTERY_VOLTAGE_SENSOR`) — actual names: `TUER_SENSOREN`/`FENSTER_SENSOREN`/
-  `TUERSCHLOSS_SENSOREN`/`BATTERIE_SENSOR`.
-- **(worse than drift, since 2026-08-12)** `INSTALL.md` step 4 and its troubleshooting table
-  still walk through configuring `WLAN_SENSOR` and the `TommiG1/HA_VAG-EU-Data-Act` entities
-  (`KM_SENSOR`, `TANK_SENSOR`, etc.) — both are gone (see section B). A fresh install following
-  this doc today would configure settings that no longer exist and skip `ZUENDUNG_SENSOR`/
-  `STANDORT_TRACKER`, which now actually matter. Needs a real rewrite, not a find-replace — not
-  done yet, flagging so it isn't mistaken for accurate.
 - `homeassistant/README.md:110` mentions the removed 97% full-tank rule (removal documented in
   `belegverarbeitung.py:18-20`); the README file list omits 5 pyscript files.
 - Obsolete comment `belegverarbeitung.py:41` ("TODO: Datei ablegen" — file has long existed).
@@ -272,9 +263,12 @@ capacitor/iframe/browser (`umgebung.ts`), types + entity table (`types.ts`), fac
       Übersicht correctly shows "Status unbekannt" and em-dash placeholders for the now-blank VAG
       fields instead of crashing (that container itself has no `device_tracker.testzone_fmm003`
       registered, so Standort still shows "Kein GPS-Signal" there — expected, the real HA instance
-      has it). **Follow-up still needed:** `INSTALL.md` step 4 and its troubleshooting table still
-      document the old WLAN/TommiG1 entity list — now actively wrong, not just stale (see
-      Documentation drift below).
+      has it). `INSTALL.md` step 4 and its troubleshooting table have since been rewritten
+      (2026-08-12) to point at the Setup menu instead of manual `einstellungen.py` edits, and to
+      use the current FMM003 field names (`ZUENDUNG_SENSOR`/`STANDORT_TRACKER`/`BATTERIE_SENSOR`)
+      instead of `WLAN_SENSOR`/TommiG1 — not live-tested against a real install (INSTALL.md itself
+      was never run end-to-end in this project, per its own opening note), but consistent with the
+      actual code.
 
 ### C) Maintain the existing HA panel (low priority — being replaced)
 
@@ -345,8 +339,9 @@ capacitor/iframe/browser (`umgebung.ts`), types + entity table (`types.ts`), fac
       the whole popup partially see-through against the app content behind it. Fixed by switching
       to `--tile-deckend` (Design's own opaque-surface token, already used by `.standortmenu` for
       the same reason), with `var(--canvas)` as a defensive fallback.
-- [ ] Fix documentation drift (statistics claim, INSTALL variable names, README gaps, obsolete
-      TODO comment) — text-only changes
+- [ ] Fix remaining documentation drift (statistics claim, README gaps, obsolete TODO comment) —
+      text-only changes; INSTALL.md's WLAN/TommiG1 drift and stale variable names were fixed
+      2026-08-12 (see section B)
 - [ ] Harden `profil_lesen()` against missing/corrupt `fahrzeugprofil.json`
 - [ ] Decide whether the 3 audit leftovers get fixed here or only in DataMetric360
 - [ ] Optional: persist the RAM-only states (trip start, fuel low-water-mark) — deliberately