The robot comes back on its own after a reboot
After a power cut or a reboot, the services and drivers on the robot now start themselves. Previously someone had to log in remotely and start them by hand, and until they did the robot was simply gone — and from the outside, "did not come back" looks exactly like "the install is broken".
What used to happen
After a G1 was rebooted once, everything on it was still stopped. Someone had to log in remotely and start each piece by hand. Until they did, the robot was simply gone.
The awkward part is that from the outside, "did not come back" looks exactly like "the deployment is broken" — you know it is unresponsive, but not whether to reboot it or reinstall it.
The cause: rebooting happens to leave containers in a particular stopped state, and the restart policy in use would not touch containers in that state.
Now
Every component on the robot — the core, perception, execution, and all 18 device drivers — comes back by itself after a reboot.
The trade-off: something you stopped by hand also comes back after a reboot. On these machines that is the smaller surprise — "should be running and isn't" is both more common and more expensive.