Start Hypervibe Companion at macOS login

[davejohnson]

What changed

• register the packaged Hypervibe Companion with SMAppService.mainApp on its first launch from Applications
• preserve later user opt-out instead of re-enabling the login item on every launch
• avoid login-item registration entirely for source-tree development builds
• add a Settings toggle with enabled, disabled, approval-required, unavailable, and failure states
• provide a one-click route to macOS Login Items when approval is required
• document installation and lifecycle behavior

Why

Hypervibe Companion is a menu bar status app, but it previously ran only after a person opened it manually. That made its ambient status and project monitoring unavailable after a restart until the app was remembered and relaunched.

The native ServiceManagement registration keeps startup user-scoped and visible in macOS. macOS remains authoritative for the registration and approval status; Hypervibe stores only whether it has attempted the one-time default setup.

User impact

After the first manual launch of an installed, signed Hypervibe app, the companion opens automatically after future sign-ins. Users can disable or restore this from Hypervibe Settings or macOS Login Items. Development builds do not register themselves.

Validation

• 40 macOS tests across 9 suites
• 5 focused login-item policy/controller tests
• production HypervibeCompanion build
• verified production binary linkage to ServiceManagement
• staged-diff and whitespace validation