Grafana: map zooms to the route; plain hyphens in titles

- "Where the car was" fits the route again: in Grafana's fit view the
  zoom value is the maximum zoom, and 6 held it at country level. Now
  15 with 10 % padding. Checked by rendering the Live dashboard with a
  simulated 10 km drive.
- Dashboard titles use "-" instead of an em dash: "MG4 - Live",
  "MG4 - Consumption", "MG4 - Charging".
- SPECS.md: Grafana keeps its state in SQLite on its PVC, which is why
  it runs as one replica with Recreate; high availability needs
  PostgreSQL or MySQL first.

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

SPECS.md

@@ -56,6 +56,13 @@ car ──live telemetry───▶ car.k8s.stinnesbeck.com (Go) ──▶ ABRP
       (`ALLOWED_HOSTS`). For git.stinnesbeck.com it needs the host on the allowlist, and the
       response parsing checked against that server's releases API. Release assets must be named
       `NilsMG4-unstable-<version>.apk` with a `.sha256` sidecar (`build-car` writes both).
+- [ ] **Grafana high availability needs another database.** Grafana keeps its own state (users,
+      sessions, preferences, provisioned-dashboard records, alerting state) in SQLite at
+      `/var/lib/grafana/grafana.db` on the `grafana-data` PVC. That is fine for one replica, and is
+      why `k8s/grafana.yaml` uses `replicas: 1` and the `Recreate` strategy: only one Grafana may
+      write the file. To run more than one replica, first move Grafana to PostgreSQL or MySQL
+      (`GF_DATABASE_TYPE`, `GF_DATABASE_HOST`, …); the replicas then share that database instead
+      of a volume. The car data itself is in InfluxDB and unaffected.
 - [ ] **Telemetry queue survives restarts.** Unsent live samples are kept in memory only.
 - [ ] **Translate the rest.** The docs (`CHANGELOG.md`, `OTA.md`'s
       message table, comments in `mise.toml`/`app/build.gradle`) are still Turkish or French.