This isn't a deployment issue. It happens because he is using an User Interface in "Operate Mode". In that case, the run mode change is not considered an "edit". This is a bit odd because if you switch to "Edit Mode", you now have a locked sequence with an edit made to it, but that not too bad since you still can't save it without providing the password.
I think the reason it works this way is that you can always change the runmode of steps in the execution window because it is considered a debugging action, like setting a breakpoint. When you do this it is not persisted with the file... just like the setting of a runmode in the file while in operate mode can't be persisted either... without unlocking. It could be considered a bug, .. but it could also be considered a convenience feature, which I think was the intent.
