M53: record OneDrive production acceptance

2026-08-22 00:00:45 +02:00
parent 2036e8b4ec
commit b0706989db
1 changed files with 7 additions and 2 deletions
@@ -13,8 +13,13 @@
  `mobilityops-20260821T202052Z.dump` and a disposable PostgreSQL restore drill at Alembic
  `4f2b9c8d7e61` with restored counts `2 users / 50 vehicles / 254 bookings / 239 audit
  events`. The off-site worker is healthy and writes to `onedrive:FleetOps/backups`.
- Exact next action: commit and push M52, deploy that exact revision, and reconfirm the
-  off-site worker plus public application readiness after promotion.
+- Committed and pushed M52 as `2036e8b4ec09b58f21202863cea4c2422f003e35`, then
+  promoted that exact checksum-verified archive. Two API and two web replicas serve behind
+  the healthy stable gateway; public and loopback readiness both report `ready/database
+  up`, and Alembic remains `4f2b9c8d7e61 (head)`. The rebuilt revision-labelled off-site
+  worker is healthy and completed another verified OneDrive round trip.
+- Exact next action: none for the requested synthetic-demo scope; retain the ITWorx OAuth
+  grant while off-site backups are desired and monitor the existing health marker.

 ## M51 — zero-error production rollout evidence (2026-08-21)