On the same note, I'm also wondering if `check-for-errors!` is inclusive enough for what we want here.  For example, if a service had called `request-shutdown`, would we also want the reloaded repl to see that somehow -- if not in the form of an exception being thrown then maybe just logged?  Right now, I'm recasting both `shutdown-on-error` and `request-shutdown`s to exceptions but maybe they should be reported differently?

If we think this needs more thought, I'd be okay pulling the reloaded pattern rework out of this PR for now and filing a new ticket.  The pattern with the currently released Trapperkeeper should still work against this new code.  There just wouldn't be the incremental benefit of having an exception thrown for a `shutdown-on-error` and/or `request-shutdown` which had occurred during bootstrapping.