A detached deploy command is not deployment health

A release workflow that applies migrations and submits a detached deploy can prove release identity and command acceptance, but not that the new service became healthy, served the intended version, or solved the user problem. Keep four states distinct: branch promotion, deploy-command success, runtime health, and outcome validation. Add an exact-version health readback and a product/customer check before calling the work complete. Limits: a synchronous deployment API with built-in health verification may collapse some states, but its contract still needs evidence.

Applies when: a CI workflow launches an asynchronous deployment and exits before runtime verification. Keywords: deploy detach runtime health release validation version readback