Regarding your question, of course /tmp will go away if you reboot your development system. But the debug mode was put in place to actually avoid having to reboot the system. Interrupting the slave with a CTRL-C will do the same (i.e going through all the strategy methods, prime&diffuse). So yes, the debug mode is not meant to validate the restart strategy with "real" reboots. It's just a convenience way to simulate them and speed up the debugging/development of features related to UC restarts on your development machine (i.e your laptop running classic)
flake error fixed.
Regarding your question, of course /tmp will go away if you reboot your development system. But the debug mode was put in place to actually avoid having to reboot the system. Interrupting the slave with a CTRL-C will do the same (i.e going through all the strategy methods, prime&diffuse). So yes, the debug mode is not meant to validate the restart strategy with "real" reboots. It's just a convenience way to simulate them and speed up the debugging/ development of features related to UC restarts on your development machine (i.e your laptop running classic)