v0.0.19 — MCP Manager promo callout + main-menu 0.0.29 (Add-ons page card-state rework)

Highlights

New — MCP Manager promo callout on the ability edit form. Section 3 (MCP Exposure) of the Custom Abilities edit page now surfaces a blue-tinted informational callout advertising the sibling acrossai-mcp-manager plugin when it is not installed / active on the current site. The callout renders directly below the existing red "Heads up" warning and offers two actions:

• Install from Add-ons — deep-links to the AcrossAI Add-ons page (admin.php?page=acrossai-addons).
• Learn more — opens https://acrossai.co/mcp-manager/ in a new tab.

When the AcrossAI MCP Manager plugin IS active on the site, the callout is fully suppressed — zero UI on the edit form. Detection uses WordPress core is_plugin_active( 'acrossai-mcp-manager/acrossai-mcp-manager.php' ) inside the admin script enqueue path; the resolved boolean plus the two URLs are injected into the existing window.acrossaiAbilitiesManager localize payload as mcp_manager_active, mcp_manager_addons_url, and mcp_manager_info_url. The callout also degrades gracefully — each action button only renders when its corresponding URL key is non-empty.

Composer dependency bump — acrossai-co/main-menu 0.0.27 → 0.0.29 (two-hop):

• 0.0.28 — refreshed Add-ons page baseline catalogue. The hard-coded list now surfaces three entries: AcrossAI Abilities Manager (wp.org), AcrossAI MCP Manager (wp.org), and AI Connectors (external "Get add-on ↗" link to acrossai.co/ai-connectors/#pricing). AcrossAI Model Manager and Turn Off AI Features are dropped from the hard-coded baseline (still register-able via the acrossai_addons filter). All three baseline cards render the shared AcrossAI SVG logo instead of per-plugin ps.w.org PNG icons — the page now reads as one product surface. Icon fit switched from cover to contain (with 6px padding) so wide/horizontal SVG logos render fully. Grid pinned to a fixed 3-column layout (repeat(3, minmax(0, 1fr))) with responsive fallbacks (2 cols under 1100px, 1 col under 720px). New optional learn_more_url add-on field renders as a "Learn more" text link inside every card action row regardless of source.
• 0.0.29 — reworked the Add-ons card action states so the page reads as a discovery surface, not a plugin manager. Active add-ons now render a non-clickable green "● Running" pill instead of a "Deactivate" button (deactivation stays in Plugins → Installed Plugins where WP admins expect it). Installed non-wordpress.org add-ons now show an in-page Activate button instead of always rendering the external "Get add-on ↗" link — detection is source-agnostic and driven by AddonsInstaller::find_plugin_file(), so a paid/off-directory add-on that the admin uploaded via Plugins → Add New → Upload Plugin can be activated straight from the AcrossAI Add-ons page. The Install code path remains restricted to wordpress.org sources (WP.org guideline #8 — no change). The AI Connectors baseline entry declares install_folder => 'acrossai-ai-connectors' so install detection matches the actual plugin folder even though the registry slug (ai-connectors) differs — canonical example for consumers whose extracted folder ≠ slug.
  Card behaviour matrix:source not installed installed, inactive activewordpress.org Install Activate ● Runninganything else Get add-on ↗ Activate ● Running

Removed

• Admin\Main::filter_out_self_from_addons + its acrossai_addons hook wiring. The pre-0.0.28 baseline did not include the Abilities Manager, so the self-filter existed to compensate for a duplicate entry a consumer had to add. 0.0.28 adds the Abilities Manager to the shared baseline directly, and 0.0.29 renders active add-ons as a non-clickable "● Running" pill — so keeping the card visible is now the desired UX.

No breaking changes

• No ability slug rename.
• No REST endpoint change.
• No option-shape change.
• No new required capability.
• Existing 218 abilities behave identically.
• Safe upgrade from 0.0.18.

Composer

"acrossai-co/main-menu": "0.0.29"

Full Changelog: 0.0.18…0.0.19