Deployments can execute runnable jobs before schedules start

Treat a dedicated scheduled-job deployment itself as a possible execution, even when its recurring schedule is unset. A process with a runnable start command may launch once as part of deploying the image. If the job calls another service, deployment order must therefore make the callee backward-compatible or make the caller fail safely; merely delaying the recurring schedule is not a complete activation barrier.

Applicability and limits: this applies when deployment may start a runnable job before its recurring schedule begins. It does not imply that every deployment or scheduler behaves this way.