v0.8.0 — Rename to acrossai-pro

Rebrand — acrossai-ai-connectors → acrossai-pro

The plugin is renamed to AcrossAI Pro. Directory becomes acrossai-pro/, main file becomes acrossai-pro.php. The Freemius product ID (34763) is unchanged, so existing licenses continue to authenticate and updates flow through the same channel. See docs/plannings/011-rename-to-acrossai-pro.md.

Breaking changes (hard break — no BC shims ship)

• Admin bookmark URLs move: ?page=acrossai-ai-connectors-account → ?page=acrossai-pro-account. Old bookmarks 404.
• The six public plugin-local filters/actions (acrossai_ai_connectors_load, _profiles, _loaded, _cimd_enabled, _cimd_trusted_publishers, _ownership_taken) rename to acrossai_pro_*. Old names are never fired again — third-party integrations must update to the new names or their callbacks silently stop running.
• PHP namespace root renames from AcrossAI_AI_Connectors\ to AcrossAI_Pro\. No class_alias() bridge — third-party code with hard imports of the old namespace will fatal on class-not-found until updated.
• Plugin constants rename from ACROSSAI_AI_CONNECTORS_* to ACROSSAI_PRO_*. Text domain renames from acrossai-ai-connectors to acrossai-pro.

Data loss on upgrade (no migration ships with this release)

• The four OAuth tables rename at the source level from wp_acrossai_mcp_oauth_* to wp_acrossai_pro_mcp_oauth_*. On upgrade, BerlinDB creates fresh empty tables under the new names; the pre-0.8.0 populated tables sit orphaned and are NOT auto-dropped. All existing DCR client registrations, OAuth access tokens, and refresh tokens become inaccessible — every connected assistant must re-authorize.
• Plugin-local options (acrossai_aic_*) and server-scoped settings (_acrossai_aic_*) similarly rename to the acrossai_pro_* / _acrossai_pro_* prefix at the source level. Per-server "enabled connectors" toggles, approved-user allowlists, and the "delete data on uninstall" opt-in all reset to defaults on upgrade.
• Operators who want a clean row set should manually DROP the legacy wp_acrossai_mcp_oauth_* tables and DELETE FROM wp_options WHERE option_name LIKE 'acrossai_aic_%' OR option_name LIKE 'acrossai_mcp_%' after confirming the plugin is running healthily.

Preserved (no action needed)

• The /wp-json/acrossai-mcp-manager/v1/* REST namespace and endpoints.
• The acrossai_mcp_manager_oauth_cleanup cron hook and all cross-plugin hooks under acrossai_mcp_manager_*.
• Existing Freemius license and update channel (same product ID).

Known follow-up — mcp-manager release required

• acrossai-mcp-manager (unchanged sibling) probes class_exists('\AcrossAI_AI_Connectors\Includes\Connectors\ConnectorProfileRegistry') to detect us. Without a class_alias() bridge on our side, that probe returns false and mcp-manager's AI Connectors tab shows no connectors — Claude/Grok/ChatGPT/Gemini won't appear on the tab until an mcp-manager release switches the probe FQCN to the AcrossAI_Pro\... namespace.
• Similarly, mcp-manager's "install AI Connectors" promo tab and addon installer key off the pre-rename folder path acrossai-ai-connectors, so both promo surfaces will keep showing even when acrossai-pro is active until the same mcp-manager release updates the sibling-slug detection.