Repository releases now carry an integrity record

Publishing a set of model files is only the beginning of a reliable release. Consumers need to know which revision they received, whether every object is intact, and which runtime contract applies.

Inspect before download#

Repository pages now surface the release revision, file inventory, and integrity metadata together. Teams can review the artifact before moving large weights across the network.

Verification is part of publishing#

Checksums and format metadata are written into the release workflow instead of being added as an afterthought. A failed verification blocks the release from presenting itself as ready.

Durable provenance#

Each release keeps its publisher and source revision attached, making operational review and later reproduction substantially simpler.