Setup-Menü: runde Klammern aus Feld-Labels entfernt, Popup verbreitert

- FELDER-Katalog: "(Datum)"/"(Restkilometer)"/"(Liter)"/"(Knopf)"/"(Fahrertür)"
  aus sieben Labels entfernt - die Unterscheidung übernimmt bereits das
  [Einheit]-Label neben der Überschrift (feldEinheitAnzeige()).
- .setup-popup auf max-width:760px verbreitert (eigener Wert, getrennt von
  .sdpopup/.sheet/.beleg-popup), damit lange Rohsensornamen nicht mehr
  umbrechen müssen.

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

AGENTS.md

@@ -4315,6 +4315,35 @@ clean via log; all three fixes re-verified live in the browser (Tanken form scre
 of `-98` and the shrunk `Kilometerstand`/`Getankte Liter` fields; Setup candidate-list device_class check
 above).
 
+**`.10`: the owner's "round collum" report was about something else entirely** - not the ellipsis (already
+fixed and confirmed gone at `.9`), but the parenthetical suffixes on seven Setup field labels
+("Nächster Ölwechsel **(Datum)**", "Tankvolumen **(Liter)**", "Türschloss **(Fahrertür)**", ...) - "remove
+alle words in round collum for Sensors". Stripped the `(...)` suffix from all seven `FELDER` labels in
+`einstellungen.py` (`TANK_LITER_SENSOR`, `REFRESH_BUTTON`, `TUERSCHLOSS_SENSOR`,
+`NAECHSTER_OELWECHSEL_SENSOR`/`OELWECHSEL_STRECKE_SENSOR`, `NAECHSTE_INSPEKTION_SENSOR`/
+`INSPEKTION_STRECKE_SENSOR`). Safe to do without losing the Datum-vs-Restkilometer distinction the
+parenthetical used to carry: the `.7`/`.8` work earlier this same round already added a `[Datum]`/`[km]`
+unit label next to every headline (`feldEinheitAnzeige()`) - that bracket now carries the disambiguation
+the round-bracket suffix used to, so "Nächster Ölwechsel" now shows as two rows differing only by
+`[Datum]` vs `[km]`, same as every other field pair in the catalog.
+
+**Also `.10`: "Make the Popup wider because of the long Name"** - the owner had manually mapped
+`TANK_DISTANZ_SENSOR` to `calculated_distance_covered_after_the_latest_refueling` (55 characters), which
+the `.setup-popup`'s existing desktop cap (`max-width:560px`, from the 2026-08-13 design audit) had too
+little room for even after the `.8` ellipsis fix let it wrap. Widened `.setup-popup` specifically to
+`max-width:760px` in the `@container (min-width:860px)` block (`audi-dashboard-ios.css`) - split out of
+the shared `.sdpopup,.sheet,.beleg-popup,.setup-popup` selector so only Setup (the one popup that shows
+raw, potentially long sensor identifiers) gets the wider cap; the others are unaffected. Verified live at
+a real 1400px viewport (not the browser tool's `desktop` preset, which stays narrow - same lesson noted
+in section N): `getBoundingClientRect()`/`getClientRects()` on the actual rendered hint span confirmed
+the popup measures 760px and the full 55-character name now renders on a single, unclipped line
+(`scrollWidth === clientWidth`, `lineCount: 1`) instead of wrapping or overflowing.
+
+Verified: `py_compile` clean on `einstellungen.py` (inside `audi_ha_test`, `MSYS_NO_PATHCONV=1` needed for
+`docker cp`/`docker exec` on this machine's Git Bash - plain paths were silently mis-translated to a
+Windows path once, worth remembering for future sessions), manifest bumped to `2026.8.28.10`,
+`audi_ha_test` restarted and confirmed clean via log, both fixes confirmed live in the browser as above.
+
 Verified live in `audi_ha_test` at every step (`.6` then `.7`), each time reading the actual rendered Setup
 popup fresh after a real restart (not a stale tab - confirmed via `performance.getEntriesByType('resource')`
 showing the new `?v=` served with a nonzero transfer size each time). Final state (`.7`), all 20 single-value