Unclear Nothing has been read yet about how the tengu_plugin_enabled_cli gate affects this on any account.
What
Telemetry events for installing, uninstalling, updating, disabling, and enabling a plugin (tengu_plugin_installed_cli, tengu_plugin_uninstalled_cli, tengu_plugin_updated_cli, tengu_plugin_disabled_cli, tengu_plugin_enabled_cli) now call a new async helper, hbe(), that tries to confirm the plugin actually exists in the marketplace catalog before logging. If that lookup fails, the event falls back to logging the plugin as third-party and redacts its name. This replaces the old synchronous lookup, and the enable-failure handler now also receives directory context as an extra argument.
Why
Confirming a plugin against the real marketplace catalog before logging telemetry gives more accurate install/usage data and avoids leaking or mislabeling names of plugins that aren't actually in the catalog.
Nothing has been read yet about how the `tengu_plugin_enabled_cli` gate affects this on any account.