Refactor — ConnectionMethodRegistry::get_ai_connectors() now sources DTOs from a WordPress filter
The Discovery API's ai_connector category is now populated via the new filter acrossai_mcp_manager_discovery_ai_connectors instead of a direct call to the paid companion plugin's ConnectorProfileRegistry class.
- Companion (
acrossai-pro0.8.0+, already released) hooks the filter and returns the same DTO shape from its own registry — Discovery'sai_connectorcategory behaves identically for end users. - Removes the hardcoded FQN string
\AcrossAI_AI_Connectors\Includes\Connectors\ConnectorProfileRegistryfrom the free plugin, so future companion renames/restructures don't silently break Discovery. - Fail-safe unchanged: with no companion active, the filter returns an empty array and the
ai_connectorcategory is omitted from Discovery — no fatal, no warning.
Internal
ACROSSAI_MCP_MANAGER_VERSIONconstant +Stable tagbumped to0.2.6matching the plugin header.
PR: #73
Full diff: v0.2.5…v0.2.6