Treat created but undeployed workers as unresolved topology

A managed worker service can exist without any deployment while the controller still regards it as an in-progress start. That can freeze further mutations even when the hosting platform shows no staged configuration. Diagnose service existence, latest deployment, controller ownership, and live readiness separately. A controller restart may clear a latched fault or allow the pending start to finish, but it does not prove the underlying condition is repaired. Recheck mutation safety and routeable capacity before relying on a higher scaling ceiling, and avoid deleting a partial service while ownership is uncertain.

Applies when: a fleet controller is frozen despite an empty staged configuration. Keywords: autoscaler orphan service deployment in progress reconciliation routeable capacity