M30: record production recruiter acceptance

PROJECT_STATE.md

@@ -2672,3 +2672,28 @@ evidence yet."
 - Exact next action: commit and push M29, create and verify a live database backup,
   deploy the committed archive to Unraid, then run live health, migration, browser and
   acceptance checks before recording the final production evidence.
+
+## M30 — recruiter polish production acceptance (2026-08-10)
+
+- Pushed M29 to Gitea `master` as `29325b6`, created and verified pre-deployment backup
+  `mobilityops-20260810T161659Z.dump`, and deployed that exact source archive while
+  preserving `.env`, volumes and the existing central n8n. Deployment revision is
+  `29325b6c2775806080dc40e1988634d6ceb300a0`; Alembic is `b913a72e8c14 (head)`.
+- API, web, PostgreSQL, scheduled backup, Prometheus and Grafana are healthy/current.
+  Live readiness is `ready`; post-deployment logs contain no traceback or critical error.
+- The initial production browser run exposed two stale assertions that expected raw
+  RAGcore filenames. Fleet Ops now intentionally presents localized source titles. The
+  tests were tightened around localized titles plus language-specific evidence; the
+  focused live matrix passed 4/4 and the complete live suite then passed **150/150 in
+  4.2 minutes**.
+- Final live visual audit covered login, Highlights and Engineering. Desktop overflow is
+  zero and the 360/390 px layouts are automated. The integration story is evidence-based:
+  n8n operational (4/4 workflows, 19 successful, zero pending/unexpected failures),
+  RAGcore operational (11 managed sources, provider index count honestly unknown), and
+  MCP labelled not connected because the final reset clears recent tool-call evidence.
+- Final reset restored **2 users / 180 customers / 50 vehicles / 254 bookings / 75
+  inspections / 40 maintenance records / 33 quality issues / 20 workflow runs** with
+  all five scenarios ready. Live evidence screenshots and the canonical acceptance
+  summary were refreshed in `artifacts/evidence/`.
+- Exact next action: commit/push this evidence-only hand-off update and refresh the
+  server's source archive/revision marker; no runtime rebuild or database change is needed.