Release and Versioning¶

The release version is explicit in Git history because version is resolved from Git tags through hatch-vcs.

Release rules should explain what kind of change readers need to look for before they trust a version bump.

Operating Rules¶

release notes should state whether contract meaning changed, narrowed, or stayed stable
release notes that mention quantification must say whether the change improves [accuracy], [robustness], [interpretability], or only [implementation]
downstream package owners deserve visible notice when lifecycle or schema rules move
avoid bundling unrelated contract and operational changes together
release-facing scope claims must stay aligned with the repository-wide Current Capability Limits