Desktop apps show unhandled runtime errors instead of silently closing

Standalone desktop applications can close without any visible explanation when an unhandled runtime error occurs. This is especially confusing during startup, before the first window appears. The application should display a copyable error message containing the Objo exception and call stack before it exits, while preserving standard-error output for command-line diagnostics.