P1: App.xaml.cs (4204 lines) and ConnectionPage.xaml.cs (2840 lines) are unmaintainable god files

Problem

Multiple files have grown far beyond the threshold where they can be safely reviewed or unit-tested in isolation.

• src/OpenClaw.Tray.WinUI/App.xaml.cs — 4,204 lines
• src/OpenClaw.Tray.WinUI/Pages/ConnectionPage.xaml.cs — 2,840 lines

App.xaml.cs currently contains:

• Single-instance mutex logic
• Protocol/deep-link activation
• CLI uninstall handling
• Update check
• Onboarding flow orchestration
• Global hotkey setup
• Tray menu construction
• Gateway event wiring (auth failure, notifications, session commands)
• Voice service lifecycle
• Channel toggle logic

This violates the Single Responsibility Principle and makes it nearly impossible to write unit tests for any individual concern.

Impact

• A bug fix in the tray menu can accidentally break onboarding because they share scope and fields.
• New developers cannot understand the app startup flow without reading 4,000+ lines.
• Code review diffs are too large to reason about.

Suggested fix

Extract cohesive modules into dedicated services or partial classes:

• AppLifecycleService — mutex, single-instance, protocol activation, uninstall
• AppUpdateService — update check, skip logic
• TrayMenuBuilder — menu construction and snapshot handling
• AppGatewayEventRouter — connection status, auth failure, notifications
• AppVoiceLifecycle — voice service, TTS, STT setup
• ConnectionPageViewModel / ConnectionPagePlan — move remaining row-state and plan logic out of the code-behind

Files

• src/OpenClaw.Tray.WinUI/App.xaml.cs
• src/OpenClaw.Tray.WinUI/Pages/ConnectionPage.xaml.cs

Start by reading src/OpenClaw.Tray.WinUI/App.xaml.cs and src/OpenClaw.Tray.WinUI/Pages/ConnectionPage.xaml.cs, then map the responsibilities listed in the issue to cohesive extraction boundaries. Confirm the service or partial-class design with maintainers before changing code. Done means the god-file responsibilities are separated and the resulting concerns can be reviewed and unit-tested in isolation.