v1.4.1 — update no longer steals the launcher

snare update relinked ~/.local/bin/snare unconditionally, so running it from any checkout — a fork, a git worktree, a throwaway clone — silently pointed the global launcher at that checkout. Delete the clone afterwards and snare is a dangling symlink, with nothing having said so.

Found by doing it, while testing the 1.4.0 remote repointing from a clone in $TMPDIR.

the launcher points at…	before	after
this checkout	relinked, announced	silent, unchanged
a different, working install	silently stolen	left alone and reported
nothing (broken)	relinked	relinked — any working snare is an improvement
anything, with --relink	n/a	relinked on request

The case this existed for still works: move your install and the launcher is left dangling, which is the repair case.

Five regression tests, all driven through SNARE_BIN in a temp directory — a test that relinks the tester's own launcher is the bug itself.

snare update