NuklearRabbitandClaude Sonnet 5
337f8716bb
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>
22 lines
910 B
Markdown
22 lines
910 B
Markdown
---
|
|
document_id: odometer-anomaly-guideline
|
|
title: Directive sur les anomalies de kilométrage
|
|
version: "1.1"
|
|
effective_date: 2026-05-20
|
|
department: Opérations
|
|
status: active
|
|
---
|
|
# Directive sur les anomalies de kilométrage
|
|
|
|
## 1. Relevé inférieur
|
|
|
|
Si un nouveau relevé est inférieur au kilométrage canonique, conservez le relevé soumis comme preuve mais n'abaissez pas la valeur canonique. Vérifiez une inversion de chiffres, une sélection erronée du véhicule ou une erreur d'importation du système source.
|
|
|
|
## 2. Résolution
|
|
|
|
Un Operations Manager peut résoudre le problème après vérification de l'inspection d'origine. Ne corrigez que l'inspection erronée ou le mappage source ; ne réécrivez pas les relevés historiques valides.
|
|
|
|
## 3. Seuil d'escalade
|
|
|
|
Toute diminution inexpliquée ou une hausse unique de plus de 2 500 kilomètres au cours d'une même location nécessite une revue.
|