Twice on 2026-07-06 the master Deploy run finished green while prod kept serving the previous image (dev correct both times):
Recovery both times: gh run rerun converged prod within minutes, so the image is fine and only the prod service update is not taking effect on the first pass (suspect: same-digest-tag race or service update returning before rollout, matrix [dev,prod] sharing one image tag).
Acceptance: a green Deploy run guarantees prod serves the new build - either verify the running container digest/commit as a post-deploy step and fail the job when stale, or force the service update. See web repo's /health commit-assert pattern.
Twice on 2026-07-06 the master Deploy run finished green while prod kept serving the previous image (dev correct both times):
Recovery both times: gh run rerun converged prod within minutes, so the image is fine and only the prod service update is not taking effect on the first pass (suspect: same-digest-tag race or service update returning before rollout, matrix [dev,prod] sharing one image tag).
Acceptance: a green Deploy run guarantees prod serves the new build - either verify the running container digest/commit as a post-deploy step and fail the job when stale, or force the service update. See web repo's /health commit-assert pattern.