Tag v0.1.0 and run acceptance on each platform #38

Parent

#30

What to build

Cut the first release and accept it on real machines.

1. Review the release pipeline's configuration and workflow: it controls what gets published under the project's name.
2. Push the v0.1.0 tag and watch the release workflow through to a published GitHub Release (the crates.io job should skip 0.1.0).
3. On each supported platform, install with the curl installer and do a real Run:
   • the Rocky Linux server;
   • an Ubuntu 24.04 machine;
   • the M5 Pro on macOS Tahoe;
   • WSL2 with Ubuntu 24.04, when a Windows machine is available.
4. Run thirdshift update on one of them and confirm it reports being on the latest version.

Acceptance criteria

• The v0.1.0 GitHub Release exists with both binaries, the installer and generated notes.
• The crates.io job skipped the already-published 0.1.0 without failing.
• A real Run succeeded after a curl install on Rocky, Ubuntu and macOS (WSL2 when available).
• thirdshift update reports being on the latest version.

Blocked by

• Release pipeline: binaries, installer and platform smoke tests #33
• Claim the crate name on crates.io and set up trusted publishing #37