You'll notice
A publish whose deploy call returns 503 after the slug is known now waits and retries against that slug.
If a deploy commit succeeds but the immediate /deploy/direct response comes back 503 after the slug is already known, the client now waits and retries against that known slug instead of failing the publish outright. The retry is logged via a new deploy_stranded_retried telemetry event.