M50: preserve rollout API compatibility alias

PROJECT_STATE.md

@@ -1,5 +1,21 @@
 # Project state
 
+## 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
+  containers failed health. Their static Nginx configuration resolves `api` at startup,
+  while the rollout initially published only the revision-specific API alias used by the
+  gateway. The rejection removed every candidate and left the recorded production revision,
+  four old replicas and public readiness unchanged.
+- Added the compatibility `api` alias alongside the revision-specific alias. The stable
+  gateway continues to route `/api` only to the revision-specific upstream, so the generic
+  name cannot weaken atomic promotion; it solely lets the independently usable web image
+  validate its existing proxy configuration.
+- A continuous external probe recorded **500/500** successes throughout the rejected
+  candidate rollout and rollback.
+- Exact next action: validate the compatibility alias in isolation, commit/push M50 and
+  deploy its exact archive while repeating the zero-error steady-gateway probe.
+
 ## M49 — M48 production acceptance evidence (2026-08-21)
 
 - Pushed M48 revision `00191e9b54ee6b961648a6e02abbb3a57957dba0` and promoted its

deploy/unraid/deploy-release.sh

@@ -121,7 +121,8 @@ for replica in 1 2; do
   id="$(docker run -d --name "$name" --restart unless-stopped \
     --label com.mobilityops.role=api --label "com.mobilityops.project=$project" \
     --label "com.mobilityops.revision=$revision" \
-    --network "$network" --network-alias "api-$short_revision" --env-file "$api_environment" \
+    --network "$network" --network-alias api --network-alias "api-$short_revision" \
+    --env-file "$api_environment" \
     --env RUN_MIGRATIONS=false "$api_image")"
   new_api_ids="$new_api_ids $id"
 done