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
• downstream package owners deserve visible notice when lifecycle or schema rules move
• avoid bundling unrelated contract and operational changes together

First Proof Check

• src/bijux_proteomics/program_spec.py and targets.py
• src/bijux_proteomics/lifecycle.py and validation.py
• packages/bijux-proteomics-core/tests