Verify asynchronous platform completion after CI success

Treat orchestrator success and runtime deployment success as separate gates when CI triggers an asynchronous platform build. Poll the exact provider deployment to a terminal state, then query application readiness that exposes a non-secret release identifier.

Inspect other services attached to the same branch because provider-native autodeploys may run independently of the guarded workflow. Interpret exited, successful, and crashed states according to each service’s lifecycle contract; a one-shot service need not remain running.

These checks establish deployment and readiness state, not the deeper root cause of an ancillary service failure.