3 Commits

Include renames

Author	SHA1	Message	Date
NuklearRabbit	81e3fd63bd	M54: harden operations and demo resilience	2026-08-24 03:31:03 +02:00
NuklearRabbitandClaude Sonnet 5	4faac24b5a	fix: localize dashboard evidence, explain blocked vehicles, clarify pending odometers ... Three content defects found by a live reviewer: - Dashboard attention subtext was raw, untranslated evidence.summary text, and for 11 of 15 seeded issues that text was literally "Synthetic deterministic seed issue". AttentionItem now exposes evidence_signals (stable code + params, same shape as the issue detail page) instead of a detail string; the frontend renders them through a shared describeEvidenceSignal() used by both the dashboard and the issue detail page. Every previously-placeholder seed row now cites a real, per-rule-type fact (a genuinely crossed service threshold, a genuinely blank field, or a real pair of booking odometer readings) instead of invented prose. - 5 of 7 blocked vehicles had no quality issue at all and one had only a resolved one, so "needs attention" led nowhere. Each now has a real open missing_required_field issue backed by a genuinely blank field (no schema change, no migration -- reuses the existing data-quality pipeline). - Booking odometer fields showing a bare "-" for 25 reserved + 1 active booking now show a localized explanation ("trip hasn't started yet" / "not yet closed"). MO-024's rented-but-service-overdue contradiction was already caught by the vehicle-status evaluator (DQ-SCAN, vehicle.manual_review_required) -- added a regression test rather than new logic. Also fixed a related bug the above exposed: the vehicle entity_snapshot omitted registration_number entirely, so the "provide missing fields" form always showed it blank regardless of the real value. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-05 17:44:32 +02:00
NuklearRabbit	24188d9b10	Initial MobilityOps build pack (docs, contracts, scaffold)	2026-08-01 20:34:43 +02:00