M43: record production deployment evidence
MobilityOps acceptance / backend (push) Failing after 15s
MobilityOps acceptance / frontend (push) Successful in 25s
MobilityOps acceptance / e2e (push) Skipped

This commit is contained in:
NuklearRabbit
2026-08-21 17:25:04 +02:00
parent 0045778dbb
commit 9e4fca5708
+31
View File
@@ -1,5 +1,36 @@
# Project state
## M43 — publish and redeploy review remediation (2026-08-21)
- Published M41 hardening commit `24dcb3494c522fadf536fa9d6826450227aeff4e`
and M42 RAGcore calibration commit `0045778dbbd2255f8ed35e7be22978a4d4497341`
to `origin/master`; fetch/revision checks matched before and after deployment.
- Created and verified the pre-deployment PostgreSQL backup
`backups/postgres/mobilityops-20260821T150738Z.dump`. The M41 deployment archive
verified at SHA-256 `5b1868b5f2d8800a3a8678bea8c55f58d35605c54234eb26b022560bbca8ebfb`;
the M42 hotfix archive verified at
`dbbaf19678aba15dc52e10186c9c784ca748a236819a5c543d597a92c87792a9`.
- Production now records M42's exact source revision, uses
`https://fleetops.itworx.tech` with Secure session cookies, returns HTTPS 200 with HSTS
and redirects HTTP to HTTPS. API, web, PostgreSQL and backup are healthy; Alembic is
`4f2b9c8d7e61 (head)`; Grafana and Prometheus stayed running. The API runtime contains
neither tests nor pytest and the post-deploy API/web critical-error scan is clean.
- Exported all 30 central n8n workflows before import to
`.deploy/n8n-backups/pre-m41-20260821T171139Z.json` (SHA-256
`9622a1345607624f4254f87ad219fc9e93de98981b93f029f946cfb3e97bd746`).
Re-imported, published and restarted the four Fleet Ops workflows; n8n is healthy,
all four are `active:true`, and every Fleet Ops callback is HTTPS.
- The full live browser run recorded **92 passed**, **8 failed** and **53 skipped** because
the acceptance suite requests repeated resets while production intentionally enforces
a 60-second reset cooldown (confirmed 429 plus `Retry-After`). Local acceptance remains
**153/153**. A production-compatible isolated five-minute run then exposed the RRF
threshold issue fixed in M42; its final rerun passed live in **13.5 s**.
- Final hand-off: a final audited demo reset returned 200 with all five scenarios ready
and canonical synthetic counts (2 users, 180 customers, 50 vehicles, 254 bookings,
75 inspections, 40 maintenance records, 33 quality issues and 20 workflow runs).
- Exact next action: no implementation or deployment work remains; monitor the next
scheduled n8n heartbeats and normal production telemetry.
## M42 — calibrate grounded RAGcore fallback (2026-08-21)
- The first live five-minute acceptance run exposed a real calibration error in M41's