M20: complete production acceptance
MobilityOps acceptance / backend (push) Canceled after 0s
MobilityOps acceptance / frontend (push) Canceled after 0s

This commit is contained in:
NuklearRabbit
2026-08-10 13:22:55 +02:00
parent 5dda5742e4
commit 509cb95110
2 changed files with 89 additions and 160 deletions
+23
View File
@@ -2480,3 +2480,26 @@ evidence yet."
and mypy are clean.
- Exact next action: commit and deploy this milestone, run complete Playwright and visual
acceptance against Unraid, refresh final evidence, push and verify the live hash.
## M20 — final production acceptance and hand-off (2026-08-10)
- Tightened RAGcore citation identity to title plus named section. Multiple chunks from
the same unsectioned document now render as one source card, while distinct named
sections remain independently citable.
- Stabilized acceptance selectors around persistent business identity instead of table
position: the guided demo filters for the generated MO-024 odometer issue, vehicle
attention checks use semantic reason markers, and reassigned work verifies the exact
captured issue reference after the queue reorders.
- Validation evidence: targeted knowledge **31 passed**; complete isolated PostgreSQL
backend **225 passed, 1 dependency warning**; complete live production Playwright
**145 passed in 4.4 minutes**. The live visual audit covered desktop dashboard, mobile
data-quality, Integration Management and a grounded RAGcore exchange without overlap
or horizontal page overflow.
- Live hand-off: readiness is `ready`; migration is `f43d829ab610 (head)`; API, database
and web containers are healthy. Reset restored all scenarios with the canonical 2 / 180
/ 50 / 254 / 75 / 40 / 33 / 20 entity counts. Central n8n, MCP Hub and RAGcore all
report operational/available; no separate n8n was started.
- Recovery evidence: verified live backup
`/mnt/user/appdata/mobilityops/backups/postgres/mobilityops-20260810T111913Z.dump`.
- Exact next action: none for the locked PoC. Routine operation, monitoring and any scope
expansion require a separate approved milestone.