From eecfcb4b79a3dd0d36d5b85580e09b9b0432e479 Mon Sep 17 00:00:00 2001
From: NuklearRabbit <145918611+NuklearRabbit@users.noreply.github.com>
Date: Mon, 10 Aug 2026 21:10:48 +0200
Subject: [PATCH] M31: cover both knowledge provider title contracts

---
 PROJECT_STATE.md                          | 3 +++
 frontend/e2e/fleet-ops-correction.spec.ts | 8 ++++----
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/PROJECT_STATE.md b/PROJECT_STATE.md
index fde98b8..550e0a6 100644
--- a/PROJECT_STATE.md
+++ b/PROJECT_STATE.md
@@ -2719,6 +2719,9 @@ evidence yet."
   localized knowledge regressions **3 passed**; complete Playwright **152 passed in 5.4
   minutes**; full and production npm audits report zero vulnerabilities. In-app visual
   inspection confirmed the new action dimensions and presentation.
+- Production RAGcore presents curated localized citation titles while the deterministic
+  provider presents the Markdown frontmatter title. Acceptance now permits both explicit
+  provider contracts while still requiring the language-specific evidence excerpt.
 - Exact next action: commit and push M31, create and verify a live database backup,
   redeploy the committed archive, then verify live RAG inventory, create a real post-reset
   MCP Hub tool-call audit record, and complete production browser/acceptance evidence.
diff --git a/frontend/e2e/fleet-ops-correction.spec.ts b/frontend/e2e/fleet-ops-correction.spec.ts
index 500c333..02d08ee 100644
--- a/frontend/e2e/fleet-ops-correction.spec.ts
+++ b/frontend/e2e/fleet-ops-correction.spec.ts
@@ -233,24 +233,24 @@ test.describe("MO-016 status conflict is order-independent", () => {
 });
 
 test.describe("knowledge base is grounded in the operator's own language", () => {
-  const cases: { lang: string; question: string; sourceHint: RegExp; sourceTitle: string }[] = [
+  const cases: { lang: string; question: string; sourceHint: RegExp; sourceTitle: RegExp }[] = [
     {
       lang: "nl-BE",
       question: "Wat moet ik doen wanneer een voertuig beschadigd terugkomt?",
       sourceHint: /zichtbare of gemelde schade/i,
-      sourceTitle: "Procedure schadeafhandeling",
+      sourceTitle: /Procedure schadeafhandeling|Schade bij voertuigretour/i,
     },
     {
       lang: "en-GB",
       question: "What should I do when a vehicle returns with damage?",
       sourceHint: /visible or reported damage/i,
-      sourceTitle: "Damage handling procedure",
+      sourceTitle: /Damage handling procedure|Vehicle return damage/i,
     },
     {
       lang: "fr-BE",
       question: "Que dois-je faire lorsqu'un véhicule revient endommagé ?",
       sourceHint: /dommages visibles ou signalés/i,
-      sourceTitle: "Procédure de gestion des dommages",
+      sourceTitle: /Procédure de gestion des dommages|Dommages au retour du véhicule/i,
     },
   ];