Guard install-service against cross-repo overwrite
Collapse the old deploy, upgrade, and uninstall verbs into a guarded
install-service / uninstall-service pair so one clone cannot silently
replace another clone's pipx-managed solstone-tmux entrypoint.
Track install ownership with ~/.config/solstone-tmux/.install-source so
a second checkout can detect cross-repo contamination before rewriting
the pipx alias or systemd unit. This mirrors the in-progress
solstone-linux hygiene work and intentionally duplicates the pattern in
this repo's own code.
Keep the UX explicit by removing the install-service --force escape
hatch. Ambiguous states now require manual disambiguation, and make
uninstall becomes a refusal target that points users at
uninstall-service or clean.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>