`otelite service install` creates the correct launchd plist (macOS) or systemd user unit (Linux) but stops there — it then prints manual `launchctl load` / `systemctl enable` instructions and exits. The user has to copy-paste those commands themselves before the service is actually running or registered for boot-time auto-start.
Expected behaviour: after `otelite service install` completes, the service is loaded and enabled — i.e. it will start on the next login/boot and is already active. A matching `otelite service uninstall` command should stop, disable, and remove the unit file.
This also surfaces a gap in the `ServiceCommands` enum: there is no `Uninstall` subcommand, so there is no supported way to undo an install other than manually removing the plist/unit file and running `launchctl unload` or `systemctl disable`.
`otelite service install` creates the correct launchd plist (macOS) or systemd user unit (Linux) but stops there — it then prints manual `launchctl load` / `systemctl enable` instructions and exits. The user has to copy-paste those commands themselves before the service is actually running or registered for boot-time auto-start.
Expected behaviour: after `otelite service install` completes, the service is loaded and enabled — i.e. it will start on the next login/boot and is already active. A matching `otelite service uninstall` command should stop, disable, and remove the unit file.
This also surfaces a gap in the `ServiceCommands` enum: there is no `Uninstall` subcommand, so there is no supported way to undo an install other than manually removing the plist/unit file and running `launchctl unload` or `systemctl disable`.