[lmcorbalan]

Summary

Closes #133

v0.1.0 is published and carries canton-token-forge-0.0.1.dar, so the two sentences in SPEC.md saying this project has no downstream users are no longer true. This is the last acceptance criterion on #133, deliberately held until after the tag existed: making the edit earlier would have merged a false claim.

Changes

• SPEC.md ### Size and status and the section 12 **Pre-release.** bullet: the package version stays 0.0.1, and the build is now described as published at v0.1.0 for downstream repositories to pin, with the tag's decoupling from the package version stated rather than left to be inferred from two different numbers side by side. "No migration story" and "no compatibility guarantees" both still hold and are kept.

No other file changes, and no behaviour changes.

Acceptance criteria

• A release exists at v0.1.0 carrying the DAR, package version still 0.0.1
• The tag points at 2c12669, where both checks are green
• The tag push was separately confirmed by the owner
• Rehearsed first: a dispatched run, then v0.1.0-rc1 whose asset was downloaded and compiled against, then both the rc release and its tag deleted
• The asset is byte-reproducible; the body records the sha256 and package-id
• A consumer needs only the asset, SDK 3.4.11 and LF 2.1
• SPEC.md no longer says there are no downstream users

Test plan

Automated tests

None added: a prose-only change to a document no suite reads. The release path itself ran green three times (dispatch 33446018447, rc 33506656591, tag 33508259874).

Manual verification

• The asset downloaded from the published release hashes to 147835e775e523f78c784996c43500c57e1ed97bcab97c97df6515b65f9332da, identical to the release body and to the reproducibility print of both the dispatched and the tag run: three independent builds, same bytes
• The rc run exercised the three steps a dispatch cannot reach: the refusal of a tag main does not reach, release-notes.sh's tag guard with ALLOW_UNTAGGED empty, and the publish
• The rc asset compiled as the only data-dependency of consumer-smoke, the first time anything compiled against the uploaded bytes rather than .daml/dist
• git ls-remote --tags returns refs/tags/v0.1.0 alone, so the rc tag is gone

Breaking changes

None.

Checklist

• Self-reviewed my own diff
• Tests added or updated
• Docs updated (if applicable)
• No unrelated changes bundled in

Screenshots

None.