polish: rebrand to Fleet Ops, add trilingual i18n, adaptive demo guide, and UX overhaul

Rebrands the product from MobilityOps to Fleet Ops across the UI, backend defaults and
knowledge base, and makes nl-BE/en-GB/fr-BE full first-class languages: i18next with
eager-bundled per-namespace resources, a persisted accessible language switcher (topbar
and mobile drawer), locale-aware date/number formatting, and a coverage test that fails
the build on any missing or empty translation key.

Backend dynamic content (demo scenarios, blocked-reason text, integration status) moves
from fixed English/Dutch prose to stable message codes + params so the frontend can
localize it; the demo knowledge base gains a fully translated NL/EN/FR procedure corpus
(11 documents each) with per-language retrieval and localized evidence-state messages.

The Demo Guide becomes breakpoint-adaptive: a docked rail on extra-wide desktop, a
floating panel that auto-collapses to a persistent, closable progress chip on standard
desktop/tablet, and a collapsed/half/full bottom sheet on mobile -- with scroll+focus+
highlight on "go to this step", Escape handling, and reduced-motion support.

The Data Quality Workbench gets accessible choice-card decisions with a clear primary/
secondary/tertiary action hierarchy; the Automation ledger groups repeated successes and
uses meaningful short refs; the Audit trail groups events by correlation id with human
action labels and readable before/after diffs. Attention Queue, Today's movements,
Vehicles, Bookings and Data Quality rows are fully clickable (stretched-link pattern)
with independent secondary links, keyboard support and mobile touch targets.

Fixes a topbar overflow on mobile caused by the new language switcher (moved into the
mobile drawer at <=960px) and two dangling aria-labelledby references introduced this
session. Updates all affected Playwright specs for the new nl-BE default and the new
Audit/DemoGuide DOM structure, and adds new i18n-coverage, demo-guide-adaptive and
clickable-rows specs. 131 backend tests, Ruff and mypy, and 71 Playwright tests pass.

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

knowledge/procedures/fr-BE/02-vehicle-return.md

@@ -0,0 +1,25 @@
+---
+document_id: vehicle-return-procedure
+title: Procédure de retour du véhicule
+version: "2.0"
+effective_date: 2026-07-01
+department: Opérations de location
+status: active
+---
+# Procédure de retour du véhicule
+
+## 1. Enregistrer le retour
+
+Ouvrez la réservation active et enregistrez le kilométrage final, le niveau de carburant, la propreté, les dommages visibles, les avertissements techniques et les notes pertinentes.
+
+## 2. Valider le relevé
+
+Un relevé de kilométrage inférieur au relevé canonique précédent ne doit jamais remplacer la valeur canonique. Enregistrez l'inspection, créez un problème de qualité des données et demandez une revue humaine.
+
+## 3. Déterminer l'état suivant
+
+Un dommage ou un avertissement technique impose un état bloqué. Un seuil d'entretien atteint impose un entretien. Sinon, le véhicule passe au nettoyage avant de pouvoir devenir disponible.
+
+## 4. Suivi
+
+L'automatisation du retour peut créer un suivi de nettoyage ou d'entretien, mais Fleet Ops reste la source de vérité pour l'état du véhicule.