#77 Refresh LaunchServices registration before notification setup

[Anonymous]

Originally created by: kristofferR

Self-heal for the "badges work but no banners" failure: when the bundle id is registered at several LaunchServices paths (typically a still-mounted release DMG alongside the installed copy), usernoted can resolve the id to the wrong copy and requestAuthorizationWithOptions fails silently — Carrier never appears under System Settings → Notifications.

setup_macos_notifications now calls LSRegisterURL(bundleURL, update: true) — the API equivalent of lsregister -f — on the running bundle before requesting authorization, so the freshest record always points at the copy that's actually running. Skipped when not running from an .app bundle (tauri dev); a nonzero status is logged via the path added in [#76].

Verified the exact FFI call standalone against /Applications/Carrier.app (status 0). Gate: cargo fmt / clippy -D warnings / cargo test --lib (60 pass) and bun run check all green.

Ref [#76]

https://claude.ai/code/session_01Y9cdpfYQpJmvFDcFu5VUux

[Anonymous]

Ticket changed by: kristofferR

• status: open --> closed