v0.5.2 — Consolidated admin notices

0.5.2 — Consolidated admin notices

Housekeeping release. No functional plugin changes vs 0.5.1.

The two OAuth-operational admin warnings now register through the shared acrossai_notices filter provided by AcrossAI MCP Manager (via the bundled acrossai-co/main-menu package) instead of this plugin's own admin_notices action.

What changes for admins

• "HTTPS is not configured" and "WP-Cron is disabled" warnings now appear in the shared Notices submenu plus a top-of-page dismissible summary, alongside MCP Manager's own dependency warnings.
• Per-user dismissal (fingerprint-based, auto-resets when the notice set changes) instead of persistent re-rendering on every admin page load.
• Capability gating (manage_options) is now enforced by the shared render layer.

What doesn't change

• Firing conditions are identical — HTTPS notice still fires when neither is_ssl() nor FORCE_SSL_ADMIN is set; WP-Cron notice still fires when DISABLE_WP_CRON === true.
• No data migration, no schema change, no re-auth for existing connections.

Under the hood

• IDs are plugin-prefixed (acrossai_ai_connectors_oauth_https_missing, acrossai_ai_connectors_wp_cron_disabled) so main-menu's first-wins dedup keeps them distinct from MCP Manager notices.
• admin/Partials/Notices.php — two render_*_notice() methods replaced by a single register(array $notices): array filter callback.
• includes/Main.php — two add_action('admin_notices', ...) calls swapped for one add_filter('acrossai_notices', ...).

Full changelog: README.txt
Merged: #16