Native updates and the public integration kit
Use the native core Updates workflow for Forovanta customers. The integration kit is public client code/instructions only, not the private issuing add-on, a core installer or a runtime licence-enforcement system.
Descriptor and trust
An add-on update service declares protocol lmp-updates-v1, the approved HTTPS vendor endpoint and its bare add-on key as scope. A theme uses theme:key inside its native XML descriptor. A route query such as ?addon=license-manager-pro&view=lmp-updates is legitimate; credentials do not belong in it.
A package cannot approve its own endpoint/public key. The board owner separately approves origin and pinned Ed25519 identity after verifying the fingerprint through an authenticated vendor channel. Premium uses entitlement; keyless access needs explicit free enrollment.
Standalone SDK boundary
The public PHP client requires PHP8.1+, sodium and cURL. It checks a signed offer and stages verified downloaded bytes at a supplied private path. It keeps TLS certificate/hostname validation on, does not follow endpoint redirects and sends credentials in Authorization, not URL parameters. Raw ZIP is the download response, not a JSON/base64 file envelope.
It does not install packages, choose trust, decide native compatibility/Premium status or implement domain activation. Use the native installer gates after verification. Do not ship development CA/signing keys to customers. Core licensed update workflow.
