Usage 0.11.10: The "Launch at login" toggle now takes effect instantly

Release notes

FEATURE

The "Launch at login" toggle now takes effect instantly without a reboot

When you toggled "Launch at login" from the menu, the system previously just jotted it down in a config file and waited for your next reboot to actually do anything about it; and turning it off left a zombie background process running. Now, the moment you flip the switch, the system instantly taps macOS on the shoulder to say "start doing this now" or "stop right now", with zero reboots required. It's like telling the building manager to cancel your newspaper delivery: they used to just write it in tomorrow's log while still delivering today's paper, but now they immediately radio the delivery person to stop.

Original changelog

Original changelogThe "Launch at login" toggle now takes effect instantly without a reboot

**"Launch at login" toggle now takes effect immediately, no reboot needed**: `login_item.enable()` / `disable()` now invoke `launchctl bootstrap gui/<uid> <plist>` / `launchctl bootout gui/<uid>/<label>` in addition to writing/removing `~/Library/LaunchAgents/com.lollapalooza.usage.plist`, so launchd learns about the change right away. Previously only the plist file was touched, so the toggle did nothing until the next reboot, and disabling left a KeepAlive orphan process behind. `launchctl` "already bootstrapped" (exit 17) and "not bootstrapped" (exit 113) are treated as success; other failures log a warning without affecting the plist operation (signatures stay `() -> None`).