macOS App Lifecycle Bridge

Define one owner for every AppKit resource and one decision point for every user-visible transition.

Route the Work

1. Inspect the app entry point, delegate/adaptor, SwiftUI scenes, activation-policy changes, windows, panels, hosting, status items, menus, event monitors, reopen, and shutdown paths.
2. Choose a primary lifecycle: SwiftUI scenes with delegate-only integration, or an AppKit coordinator that retains controllers and hosts SwiftUI. Never let both own the same surface or command.
3. Read ownership-and-transitions.md to assign owners and model launch, headless, active/inactive, reopen, close, hide, and termination transitions.
4. Read windows-menus-and-monitors.md when implementing a window, panel, hosting shell, menu/status item, or event monitor.
5. If Xcode MCP is available, run DocumentationSearch; use apple-documentation.md as the dated API index.

Preserve These Invariants