Flight programs should terminate when the command pod or command chip they are running on is deactivated.

Currently if you deactivate a command pod or command chip with a running flight program the program continues running. I think if a command pod/chip is deactivated the flight program should terminate. When a deactivated command pod/chip is reactivated the flight program should restart (even if it previously exited on its own) as if the craft had just launched (i.e. there one running thread per start block), however values stored in variables should be preserved (thus allowing a flight program to have persistent storage between reboots).