NuklearRabbitandClaude Sonnet 5
6deb95524d
- Add a single shared, pure vehicle-status evaluator (app/services/vehicle_status.py)
used identically by the data-quality scanner, a new non-mutating status-recommendation
preview endpoint, and a transactional apply endpoint with optimistic-concurrency token
revalidation -- eliminates the old opaque "calculate and apply" action and the unsafe
"maintenance + active booking -> auto rented" shortcut. Frontend
DataQualityIssueDetail.tsx now shows a review/decide/confirm panel with localized
why/evidence/consequence text in nl-BE/en-GB/fr-BE, with an exact "Change status to
<status>" confirm action per the brief.
- Fix MO-016 issue-order dependency: resolving the booking-overlap issue before vs.
after the status-conflict issue now converges on the same final vehicle status,
proven by test_mo_016_status_conflict_recommendation_is_order_independent.
- Make "Fleet Ops" a non-localizable brand constant (frontend/src/product.ts,
backend PRODUCT_NAME) via {{productName}} interpolation everywhere the brand name
appeared in locale prose; add a permanent test guarding against a translation file
ever defining the brand name or an "appName" key again.
- Convert dynamic backend prose to stable message codes + params: return status
reasons, audit field/actor-type labels, automation last_error, and search
section/vehicle/booking/issue results all now carry codes the frontend localizes,
with raw technical text demoted to a "Technical details" disclosure.
- docs/fleet-ops-correction/: gap audit, i18n inventory, and the vehicle-status
decision table documenting the evaluator's rules and safe-status principles.
148 backend tests + Ruff + mypy green; Alembic migration verified upgrade/downgrade;
frontend tsc/build and the i18n-coverage Playwright suite green.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
42 lines
1.9 KiB
JSON
42 lines
1.9 KiB
JSON
{
|
|
"eyebrow": "Assure / Grounded knowledge",
|
|
"title": "Procedure knowledge",
|
|
"description": "Ask operational questions. Answers are shown only when {{provider}} returns sufficient cited evidence.",
|
|
"providerDemo": "the demo knowledge base",
|
|
"providerRagcore": "RAGcore",
|
|
"statusAvailable": "Available",
|
|
"statusUnavailable": "Unavailable",
|
|
"proceduresIndexed": "{{count}} procedures indexed",
|
|
"providerNote": "This demo answers from a small, fixed set of indexed procedures — not a live RAGcore connection. A live RAGcore backend will later take over the same interface without changing how this page works.",
|
|
"askHeading": "Ask a procedure question",
|
|
"askSubheading": "Retrieval → evidence check → grounded answer",
|
|
"questionLabel": "Question",
|
|
"questionPlaceholder": "e.g. What must I do when a vehicle returns with damage?",
|
|
"ask": "Ask",
|
|
"asking": "Asking…",
|
|
"askFailed": "Could not reach the knowledge service.",
|
|
"suggestedLabel": "Try one:",
|
|
"suggestedQuestions": [
|
|
"What must I do when a vehicle returns with damage?",
|
|
"How do I register a vehicle return?",
|
|
"When may a vehicle be made available again?",
|
|
"Who reviews an unusual odometer reading?",
|
|
"Which checks are required before checkout?"
|
|
],
|
|
"emptyTitle": "Evidence before answers",
|
|
"emptyDescription": "Ask about returns, damage, inspections or another indexed procedure. {{productName}} will not invent an answer when evidence is missing.",
|
|
"retrievalFlow": {
|
|
"question": "Question",
|
|
"sources": "Sources",
|
|
"answer": "Answer"
|
|
},
|
|
"questionLabelExchange": "Question",
|
|
"evidenceStates": {
|
|
"grounded": "Grounded in cited procedures",
|
|
"insufficient": "Insufficient evidence",
|
|
"unavailable": "Knowledge service unavailable"
|
|
},
|
|
"unavailableBody": "The knowledge service is currently unreachable. Operational features are unaffected — try again later.",
|
|
"sourceVersion": "v{{version}}"
|
|
}
|