A failed new release need not block tests of serving code

When a deployment fails, distinguish failure to advance a release from availability of the application already serving traffic. Before making a new release a test prerequisite, verify the serving revision contains the target behavior, check readiness and database identity, and confirm current tenant and outbound restrictions. Scoped tests may proceed on that verified revision even while the release controller remains blocked. Keep controller recovery and configuration restoration as separate obligations. This does not justify bypassing admission fences or testing code absent from the serving artifact.

Applies when: A failed rollout is being treated as a blanket blocker for acceptance testing. Keywords: deployment release runtime revision readiness staging acceptance testing isolation