M51: record zero-error rollout acceptance

2026-08-21 22:33:41 +02:00
parent cea0825d60
commit 51b0ade7e7
2 changed files with 21 additions and 0 deletions
@@ -1,5 +1,22 @@
 # Project state

+## M51 — zero-error production rollout evidence (2026-08-21)
+
+- The rejected M49 candidate proved rollback isolation: production remained on M48 and
+  **500/500** external probes succeeded. M50 revision
+  `cea0825d6094e2981452fd179dd5d9f8724766d0` then promoted successfully from archive
+  SHA-256 `6148de2ea7966d1527b28d769048b4b6cf8a7cfc699f2e5cb568e7504efc4693`.
+- The established gateway stayed online throughout M50 promotion: **700/700** external
+  probes passed with zero interruption. Exactly two M50 API and two M50 web replicas serve
+  behind it; no rejected M49 candidate remains. Database, backup, Prometheus, Alertmanager,
+  Grafana and gateway all remain healthy.
+- Post-promotion live acceptance passed **4/4** in Chromium/Firefox, including the grounded
+  production knowledge path. The 360-request authenticated read gate again had zero errors
+  at concurrency 18, p95 **116.4 ms** and max **144.6 ms**.
+- Exact next action: commit/push this evidence-only M51 revision, deploy it through the same
+  verified gateway path, confirm exact revision/readiness and tag `v1.1.0-poc`. OneDrive is
+  fully prepared but remains disabled until the owner completes Microsoft OAuth once.
+
 ## M50 — preserve web/API compatibility alias during rollout (2026-08-21)

 - The first steady-gateway M49 rollout correctly kept M48 serving when both candidate web