Claim the crate name on crates.io and set up trusted publishing #37

Parent

#30

What to build

Claim the thirdshift name on crates.io with the real 0.1.0, and let the release workflow publish later versions without a stored token. This comes after every 0.1.0 code and docs ticket has merged, because a crates.io version can never be changed once it's published.

1. From an up-to-date main, with the version at 0.1.0: cargo login, then cargo publish.
2. On crates.io, configure this repository's release workflow as the crate's trusted publisher.
3. On GitHub, set the repository's About description to the manifest's description, and clear the homepage link (or keep it as a placeholder) until thirdshift.app is live.

Acceptance criteria

• thirdshift 0.1.0 is on crates.io, built from the same commit that will be tagged v0.1.0.
• The trusted publisher is configured for this repository's release workflow.
• The GitHub About description is set and the homepage link is handled.
• No crates.io token is stored in GitHub.

Blocked by

• Command surface: help, version and argument errors #31
• CI on the supported platforms: Ubuntu 24.04 and macOS 26 #32
• thirdshift update #34
• crates.io packaging and publish job #35
• README for the release, and ADR-0003 #36