M11: implement operational booking lifecycle

This commit is contained in:
NuklearRabbit
2026-08-10 03:06:30 +02:00
parent 3f13912739
commit 4a3c3bd0a9
15 changed files with 516 additions and 7 deletions
+24
View File
@@ -2272,3 +2272,27 @@ evidence yet."
- Evidence: local web build, ruff and mypy clean; deployed Unraid Compose test suite
**195 passed**. API/web/db healthy, deterministic demo seed restored. Live source
revision: `948d5eb6a60a138dcfc539fd9e36f885200190de`.
## Knowledge trust and persistent integration telemetry (2026-08-10)
- RAGcore fallback now refuses unrelated questions, ranks multilingual domain evidence
before answering and returns `insufficient` with no answer when no MobilityOps concept
is present. A live damage question is grounded in `damage-procedure.md`; an unrelated
football question is explicitly insufficient.
- Demo reset preserves operational MCP, n8n and knowledge telemetry while CLI/test reset
remains fully deterministic by default.
- Evidence: deployed Unraid suite **199 passed**; ruff and mypy clean. Committed as
`de15191`, with follow-up deterministic test corrections through `3f13912`.
## Operational booking lifecycle (2026-08-10)
- Added authenticated canonical-customer search, interval-aware vehicle availability,
booking creation and audited cancellation. The web app now provides a localized,
responsive creation flow and cancellation action instead of requiring direct API use.
- Booking creation obtains a PostgreSQL row lock on the selected vehicle before checking
overlap. The concurrent contract test proves two simultaneous requests yield exactly
one reservation and one conflict.
- Evidence: production web build passed; ruff and mypy clean; the modified code passed
the full Unraid Compose suite: **203 passed, 1 warning**.
- Exact next action: implement audited checkout/activation, maintenance capture and
operations-manager user administration, then repeat the complete validation gate.