Publish signed releases and licensed downloads
Current inspected release: beta17, private Premium preview. Read the current workflow and acceptance limits. Earlier beta references describe the retained feature history, not a newer public/stable stamp.
Upload the canonical resource ZIP once through its ordinary resource workflow. In LMP Release vault, choose that already mapped Downloads resource, version, Stable/Beta channel, changelog and optional minimum core; publish a private immutable snapshot. The vendor vault accepts readable1–64 MB ZIPs. A duplicate product/version cannot overwrite historical bytes.
LMP signs exact scope/version/release ID/filename/SHA256/bytes plus new channel/changelog/minimum-core fields. Withdraw stops delivery but preserves the archive; Republish restores availability. My Licenses → Licensed downloads rechecks account/license/order/expiry/update eligibility on each fetch, rather than trusting the displayed page.
The machine service uses authenticated HTTPS POST check/download with the key in Authorization, never a URL. Actual downloads stream raw ZIP bytes. New manifests use base64url signatures and bare addon scopes. A free public-update policy is explicit and repeatedly checks both resource classification and the archive's commercial:false/root key. Zero-price Premium remains protected. Do not advertise the incompatible156x client as a successful install path; a corrected core must safely review/apply verified files.
