Upgrade without discarding identity

Keep signing identity, native object ownership and operator authority continuous across upgrades.

Review the milestone

Read module.xml and the current README before upgrading. Historical claims describe their own versions, not acceptance of 0.7.0-dev. Newer neutral identity support does not migrate retained legacy identities or signing keys. The current milestone does not change the approved activation, BYOT or emergency implementation.

Back up coherently

Back up the PBX configuration and all protected DOMAINTAINS state, plus the operator replay, registry and operation stores using an appropriate consistent snapshot. Retain permissions and ownership. Rehearse restoration on an isolated system without accidentally reusing live carrier authority.

Run controlled acceptance

Test activation, refresh, local unlink and identity preservation on FreePBX 16 and 17. Verify native routes, reload behaviour and real calls separately. Review ownership conflicts rather than silently adopting them. Deployment and production approval remain operator decisions.