As part of commit 2a85d5d, this function is now gone from the repl example and replaced with a call to `check-for-errors!` on the TrapperkeeperApp, as suggested above.  `check-for-errors!` will cause an exception to be thrown back to the caller only if a shutdown "error" specifically occurred.  If a `request-shutdown` is performed by a service, it isn't considered an *error* and, therefore, doesn't trigger an exception on a call to `check-for-errors!`.  We may want to consider a more general purpose way to get the shutdown reason up at the TrapperkeeperApp level if we find a need to deliver this up to the reloaded repl example.