Publish a matching immutable release archive
Upload the resource package once, then publish that same stored file as an LMP release with the correct product key and version. Before signing, beta17 validates the copied immutable snapshot, not merely the label typed into a form.
- An add-on needs a root addon.json whose package key and version match the mapped product and release.
- A theme needs genuine native forovanta_style XML accepted by the theme reader, with matching key/style_version.
- Wrapper-only manifests, wrong product/version, unsafe paths, case collisions and symlinks are refused. Archive limits include64 MB compressed,256 MB expanded and10,000 entries, plus native theme limits.
- A refusal must leave no release metadata or orphan snapshot. Customer installers still apply their own compatibility and safety rules.
Free/Premium classification follows real package/native theme metadata, not an optional sidecar or a zero selling price. Keyless enrollment is explicit, only for genuinely free resources/packages; private/Pro identities and commercial licence terms are not turned free by a false flag. A licensed refusal must not fall back to keyless.
Earlier signed snapshots are immutable. An older invalid package may need withdrawal and a correctly versioned replacement rather than silently changing the same release bytes. This guide contains no private signing material or product downloads.
