Fix launcher sync triggering on every fresh tarball extraction

Version fingerprint was stat -c '%i:%Y' which includes the inode number.
Re-extracting the same tarball produces new inodes, so the marker never
matched and the 237MB copy to ~/.local/share/fluorine/bin/ ran on every
launch — painful cross-drive (tarball on one disk, home on another).

Switch to '%s:%Y' (size + mtime). Survives re-extraction, still detects
real updates.

Also stage into bin.new/ and rename instead of rm -rf'ing bin/ before
the tar pipe. If the user Ctrl+C's mid-sync (or the copy fails), the
existing install stays intact instead of being left empty.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions