Take the version from the release tag alone

[propensive]

A release's version is now declared once, by its tag. There is no furyVersion to bump before tagging, so a tag can no longer disagree with build.mill and fail the release.

• settings.version gives FURY_RELEASE_VERSION when a release or snapshot sets it. Otherwise it gives the patch after the latest release tag reachable from HEAD: 0.7.1 after 0.7.0, which sorts after that release and before whichever follows. Where no release tag is reachable, as in CI's shallow checkout, it gives 0.0.1.
• publishVersion is that version, and buildVersion is that version plus the tree hash outside a release.
• The launcher resolves fury-core at core.publishVersion(). In a release that is the tag's version, which is the coordinate Burdock must externalize against.
• make snapshot takes its base from ./mill show fury.core.publishVersion, so a snapshot after 0.7.0 is 0.7.1-<hex>.
• The release instructions in the Makefile and docs no longer ask for a bump. release.sh already skips its pin check when build.mill declares no version.

A development build's publishLocal also no longer installs jars under a released version, where they could shadow the real release in ~/.ivy2/local.

Verified locally:

• ./mill show fury.core.publishVersion gave the patch after the latest local tag.
• With FURY_RELEASE_VERSION=9.8.7, publishVersion and the launcher's mvnDeps both gave 9.8.7.
• buildVersion gave the next version with the tree hash.

🤖 Generated with Claude Code