Release v2.1.0 · renatobo/bono_arm_api

New Features

ARMember is now a declared dependency. When neither ARMember nor ARMember Lite is active the plugin grants none of its capabilities, so it has no reachable API surface on a site that cannot serve one. The capabilities are granted automatically on the first admin page load after ARMember is activated. Activation itself is deliberately not blocked, because that would break WP-CLI, provisioning scripts, and the official Plugin Check, all of which activate a plugin standalone.
An admin notice now appears when ARMember is deactivated while this plugin is already active, which is the case the activation check cannot cover on its own.

Dependency detection accepts either distribution: the premium ARMember (armember) or ARMember Lite (armember-membership). Detection uses the directory constant each copy defines at the top of its main plugin file, so it resolves during the activation request rather than depending on an ARMember function that may not be registered yet.
README.md and readme.txt now state that either copy satisfies the requirement.

Existing installs are unaffected on update. The dependency check withholds capabilities and renders a notice; it does not deactivate anything and does not revoke capabilities that were already granted. Sites already running the plugin alongside ARMember see no change. Sites where ARMember is missing keep the existing behavior of returning Service Unavailable from the endpoints, now with a visible admin notice explaining why.
The Requires Plugins: header is deliberately not used. WordPress resolves that header's WordPress.org slugs against installed plugin directories and requires every listed slug to be active. Because the premium and Lite copies live in different directories and only Lite is on WordPress.org, declaring either slug would make WordPress deactivate this plugin on every site running the other copy. The check is performed at runtime instead.