fix(release): 同步 API 运行 revision

生产发布滚动 API 时写入当前完整 release SHA，避免镜像 digest 已更新但运行 revision 仍指向上一版本。补充发布 helper 静态回归检查。\n\n验证：bash -n、ShellCheck、cluster release helper 测试通过。

deploy/kubernetes/easyai-ai-gateway-cluster-release

@@ -634,7 +634,8 @@ rollout_site() {
       "AI_GATEWAY_DATABASE_CRITICAL_MAX_CONNS=$AI_GATEWAY_DATABASE_CRITICAL_MAX_CONNS" \
       "AI_GATEWAY_DATABASE_RIVER_MAX_CONNS=$AI_GATEWAY_API_DATABASE_RIVER_MAX_CONNS" \
       "AI_GATEWAY_DATABASE_MIN_IDLE_CONNS=$AI_GATEWAY_DATABASE_MIN_IDLE_CONNS" \
-      "AI_GATEWAY_DATABASE_MAX_CONN_IDLE_SECONDS=$AI_GATEWAY_DATABASE_MAX_CONN_IDLE_SECONDS" || return 1
+      "AI_GATEWAY_DATABASE_MAX_CONN_IDLE_SECONDS=$AI_GATEWAY_DATABASE_MAX_CONN_IDLE_SECONDS" \
+      "AI_GATEWAY_REVISION=${ACTIVE_RELEASE_SHA:-}" || return 1
     "${kubectl[@]}" set image "deployment/easyai-api-$site" -n "$NAMESPACE" \
       "api=$api_image" || return 1
     "${kubectl[@]}" rollout status "deployment/easyai-api-$site" \

tests/release/cluster-release-helper-test.sh

@@ -61,6 +61,8 @@ AI_GATEWAY_WORKER_TARGET_OUTSTANDING_PER_REPLICA=48
 AI_GATEWAY_WORKER_CPU_REQUEST_MILLICORES=500
 AI_GATEWAY_WORKER_MEMORY_REQUEST_MIB=512
 
+grep -Fq "\"AI_GATEWAY_REVISION=\${ACTIVE_RELEASE_SHA:-}\"" "$helper"
+
 # activate_manifest invokes this function inside an && condition. A failed
 # rollout must still propagate instead of falling through to a stale Ready Pod.
 if rollout_worker_site hongkong 'registry.example.invalid/api@sha256:deadbeef' && true; then