feat: move desktop runtime diagnostics out of the primary UI #103
Description
Context
As an end user, I need the Katra desktop shell to focus on the product experience rather than developer diagnostics, so the app feels intentional and approachable on first open.
Acceptance Criteria
- Runtime and database connection details are removed from the main user-facing shell.
- The primary app surface no longer depends on visible developer diagnostics to explain the product.
- Equivalent diagnostic information remains available through developer-oriented logs or a non-primary debug surface.
- Electron or application logs capture the runtime/connection details needed for debugging local issues.
- This issue is coordinated with the MVP shell work so the user-facing landing experience stays clean.
Notes
This issue does not remove diagnostics entirely. It relocates them to a more appropriate developer-focused surface so the app can present a better first impression without making debugging harder.
Out of Scope
- a full developer tools panel implementation unless needed for parity with the existing visible diagnostics