Versions and release interpretation
Read package versions and verification boundaries without confusing source with a deployed service.
Independently versioned packages
The manifest catalog records each package's source version and feature flags. There is no single version number that proves every library, registry artifact and live service matches.
Before upgrading
Compare the package manifest, dependency lockfile, compatibility notes and documented feature profile. Check identity/signing, wire formats and persistent store compatibility before reusing state. Read the relevant package reference and rerun your application's integration checks.
What documentation verification means
A docs build verifies the publication pipeline. Source analysis verifies recorded signatures and provenance. Neither proves a deployed peer-to-peer path, a qualified physical runner or a backend release. Loom private proof and Stations-inclusive suites remain subject to their dedicated execution policies.
Release history context is historical. Use the current source and your actual deployed revision for operational decisions.
