Jens/MobilityOps
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

M31: cover both knowledge provider title contracts
MobilityOps acceptance / backend (push) Canceled after 0s
Details
MobilityOps acceptance / frontend (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
NuklearRabbit
2026-08-10 21:10:48 +02:00
parent cb7edb0b84
commit eecfcb4b79
2 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PROJECT_STATE.md
+3
View File
@@ -2719,6 +2719,9 @@ evidence yet."
localized knowledge regressions **3 passed**; complete Playwright **152 passed in 5.4 localized knowledge regressions **3 passed**; complete Playwright **152 passed in 5.4
minutes**; full and production npm audits report zero vulnerabilities. In-app visual minutes**; full and production npm audits report zero vulnerabilities. In-app visual
inspection confirmed the new action dimensions and presentation. 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, - 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 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. MCP Hub tool-call audit record, and complete production browser/acceptance evidence.
frontend/e2e/fleet-ops-correction.spec.ts
+4 -4
View File
@@ -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", () => { 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", lang: "nl-BE",
question: "Wat moet ik doen wanneer een voertuig beschadigd terugkomt?", question: "Wat moet ik doen wanneer een voertuig beschadigd terugkomt?",
sourceHint: /zichtbare of gemelde schade/i, sourceHint: /zichtbare of gemelde schade/i,
sourceTitle: "Procedure schadeafhandeling", sourceTitle: /Procedure schadeafhandeling|Schade bij voertuigretour/i,
}, },
{ {
lang: "en-GB", lang: "en-GB",
question: "What should I do when a vehicle returns with damage?", question: "What should I do when a vehicle returns with damage?",
sourceHint: /visible or reported damage/i, sourceHint: /visible or reported damage/i,
sourceTitle: "Damage handling procedure", sourceTitle: /Damage handling procedure|Vehicle return damage/i,
}, },
{ {
lang: "fr-BE", lang: "fr-BE",
question: "Que dois-je faire lorsqu'un véhicule revient endommagé ?", question: "Que dois-je faire lorsqu'un véhicule revient endommagé ?",
sourceHint: /dommages visibles ou signalés/i, 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,
}, },
]; ];