When a control repository change is reloaded, the proxy routes in the control repository are not reloaded; proxy routes are only created on presenter launch.

Once we're on Carina and get our continuous deployment process in place, this is probably fine. I'd like to get us to @ktbartholomew's idea of shipping control repository updates the same way we ship code updates and do both automatically as part of a unified CD process. I'll file the issue just in case this bites us again, though.