M32: record production integration acceptance
This commit is contained in:
@@ -2725,3 +2725,28 @@ evidence yet."
|
||||
- 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.
|
||||
|
||||
## M32 — M31 production acceptance and integration proof (2026-08-10)
|
||||
|
||||
- Pushed M31 to Gitea `master`, deployed the committed runtime, and refreshed the exact
|
||||
server source marker to `eecfcb4b79a3dd0d36d5b85580e09b9b0432e479`. The verified
|
||||
pre-deployment custom-format backup is
|
||||
`backups/postgres/mobilityops-20260810T185833Z.dump`; its SHA-256 and
|
||||
`pg_restore --list` both passed. Alembic remains `b913a72e8c14 (head)`.
|
||||
- Live RAGcore exact lookups report **11/11 verified active published documents** for
|
||||
each of NL/EN/FR. The Knowledge Hub visibly separates that index proof from the 33/0
|
||||
n8n sync report and labels the provider operational.
|
||||
- A real production MCP Hub `mobilityops.operations.summary` call reached Fleet Ops under
|
||||
the tenant-bound Hub client identity. The final short-lived demo bearer returned HTTP
|
||||
200 with JSON and HTTP 401 after immediate revocation; Fleet Ops now reports MCP Hub
|
||||
operational and retains three real verification audit events.
|
||||
- Complete live Playwright acceptance passed **152/152 in 4.7 minutes** after the focused
|
||||
three-language RAG title/evidence matrix passed 3/3. Final in-app visual inspection
|
||||
confirmed the compact dashboard attention action, the four-fact RAG evidence strip and
|
||||
the operational MCP card. Post-deployment API logs contain no traceback or critical
|
||||
error.
|
||||
- The final reset restored **2 users / 180 customers / 50 vehicles / 254 bookings / 75
|
||||
inspections / 40 maintenance records / 33 quality issues / 20 workflow runs**, with
|
||||
all five scenarios ready; the last action after reset was the read-only Hub proof.
|
||||
- Exact next action: none for the requested scope; keep the public synthetic demo online
|
||||
and monitor its existing health, backup and integration evidence surfaces.
|
||||
|
||||
Reference in New Issue
Block a user