v2.0.3

New Features

• No new features in this maintenance release.

Improvements

• No functional changes to the API, the admin screen, or the endpoints.

Bug Fixes

• uninstall.php now stops before touching stored data when a second copy of the plugin is still installed and active. Options, capabilities, and transients are keyed by name rather than by directory, so two copies in differently named folders share the same records; deleting one previously removed the feature toggles, the schema-version option, and all three capabilities from the copy that was still running.

Upgrade Notes

• Correcting the 2.0.2 notes. Those notes claimed Git Updater renames the extracted directory to match the installed plugin, so 2.0.2 would update in place. That is wrong. Because 2.0.2 changed the packaged folder from bono_arm_api to bono-arm-api, Git Updater installed it as a second plugin and left the original in place and still active.
• If you are running two copies, deactivate the old bono_arm_api one, confirm the new bono-arm-api copy is active, and then remove the old directory. On 2.0.2 remove it over SFTP rather than through the wp-admin Delete link, because the old copy's uninstall routine predates the guard added here and will delete the shared settings and capabilities. From 2.0.3 onward the guard makes the wp-admin route safe.
• If you already deleted the old copy through wp-admin, your feature toggles were reset and must be re-enabled under Settings → Bono API. The capabilities restore themselves on the next page load, because the schema-version check re-runs the activation routine.
• The packaged folder stays bono-arm-api. Renaming it back would fork installs a second time for anyone already on 2.0.2.