M36: deepen operational and mobile UX

PROJECT_STATE.md

@@ -2793,3 +2793,27 @@ evidence yet."
   assertion passed.
 - Exact next action: improve mobile Data Quality operations, technical evidence labels,
   RAG scope clarity and sticky resolution actions.
+
+## M36 — operational UX depth and scalable quality review (2026-08-10)
+
+- Reserved bookings can now be moved through an audited, overlap-safe schedule command.
+  The detail page uses Brussels wall-clock input and explains/rechecks availability.
+- Mobile Data Quality starts with a compact filter trigger, exposes removable active
+  filters, supports select/deselect-visible, aligns checkboxes with record cards and keeps
+  bulk/resolution controls reachable above the mobile navigation. The row link now has one
+  accessible reference instead of duplicate screen-reader text.
+- MCP evidence leads with the friendly ITWorx Hub connector and keeps the raw client
+  identity in technical disclosure. RAGcore statistics explicitly distinguish the current
+  language from the all-language n8n report.
+- Duplicate-customer scanning now blocks on the exact identifiers required to reach its
+  score threshold before running name similarity. This replaces quadratic all-pairs work
+  without changing detection semantics. Booking list hydration also fetches only related
+  customer and vehicle rows.
+- React review confirmed primitive effect dependencies, aborted request handling, semantic
+  controls, keyboard names and no new render waterfalls. Validation: focused booking/data
+  quality API **50 passed**; Ruff/mypy and frontend lint/build passed; focused Playwright
+  booking and mobile quality flows passed. Visual inspection at 390 px and 1440 px found
+  no overflow or console warnings; the only logged error was the intentional anonymous
+  session probe 401.
+- Exact next action: run complete clean backend/frontend acceptance and the full five-minute
+  browser suite, then commit/push, back up and deploy.