Update the pair and resume a schema upgrade

1. Back up the current database, plugin files and any separately configured private keys or storage. Keep the previous package pair available.
2. On staging, follow the current package instructions: update Free first, then the matching Pro ZIP. Do not uninstall as an update method.
3. Open Logged.ai and inspect any compatibility or schema-upgrade message before continuing normal work.
4. When Schema upgrade is offered, inspect its status and choose Run next upgrade phase. Each submission advances one resumable phase; scheduled work may also resume it when cron runs.
5. After completion, check System status, saved configuration and a small representative workflow on your own site.

A busy message can mean another upgrade is running; retry later rather than bypassing the lock. Preserve the recorded error if a phase cannot complete. Do not delete tables, reset checkpoints or repeatedly reinstall to hide the failure.

Schema changes are additive and checkpointed in the implementation, but a code rollback is not a database restore. Activity missed while an incompatible phase is pending cannot be reconstructed. Recovery must keep code compatible with the current data.

These instructions describe the 0.1.1-dev Studio v7 pair. Public release and paid update delivery are not yet available. Do not assume a paid updater is connected because a Pro connection or updates screen exists.