v1.1.0: rename provider id to ultimate-ai-connector-anthropic-max + fix render clobber

This commit makes two coordinated changes that have to ship together:

1. RENAME the AI Client provider id from 'anthropic-max' to
   'ultimate-ai-connector-anthropic-max', and the JS registerConnector()
   slug from 'ai-provider-for-anthropic-max/connector' to the same
   'ultimate-ai-connector-anthropic-max'. This:

   - Matches the naming convention used by the sister plugins
     (ultimate-ai-connector-webllm, ultimate-ai-connector-compatible-endpoints).
   - Claims the 'ultimate-ai-connector-' namespace properly so a future
     third-party 'anthropic-max' plugin can't collide with this one.
   - Causes the WP Connectors page to render ONE card instead of two —
     previously a hidden duplicate auto-registered ApiKeyConnector card
     existed alongside the custom-rendered card because the slugs differed.

   This is a BREAKING change for any caller that hardcoded the old
   provider id (e.g. AiClient::defaultRegistry()->getProvider('anthropic-max')).
   Stored OAuth tokens, REST endpoint URLs, option keys, transient prefixes,
   plugin folder name, text domain, and css class are unchanged.

2. WORKAROUND for WP core's registerDefaultConnectors() clobbering custom
   renders. The rename in (1) makes the slugs match, which exposes this
   plugin to the same race the other Ultimate-Multisite connector plugins
   hit: WP core's routes/connectors-home/content module runs
   registerDefaultConnectors() inside an async dynamic import, after our
   top-level registerConnector() has already populated the store, and the
   reducer's spread overwrites our custom render with the generic
   ApiKeyConnector. Re-assert the registration on five ticks (sync +
   microtask + setTimeout 0/50/250/1000ms) so we always end up last.

The proper upstream fix is in WordPress/gutenberg#77116. Once that ships
in a Gutenberg release, the 5-tick workaround can be removed; the rename
is permanent.

CSS class on the rendered card also updated from
`connector-item--anthropic-max` to `connector-item--ultimate-ai-connector-anthropic-max`
to match the new slug and the convention used by the sister plugins.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: superdav42

js/connector.jsx

@@ -509,7 +509,7 @@ function AnthropicMaxConnectorCard( { slug, label, description } ) {
 
 	return (
 		<ConnectorItem
-			className="connector-item--anthropic-max"
+			className="connector-item--ultimate-ai-connector-anthropic-max"
 			icon={ <Logo /> }
 			name={ label }
 			description={ description }
@@ -521,7 +521,11 @@ function AnthropicMaxConnectorCard( { slug, label, description } ) {
 }
 
 // Register the connector card.
-const SLUG = 'ai-provider-for-anthropic-max/connector';
+//
+// SLUG matches the PHP provider id from AnthropicMaxProvider::createProviderMetadata()
+// so the WP core Connectors page renders ONE card instead of two (the
+// auto-discovered server entry + a separately-keyed JS entry).
+const SLUG = 'ultimate-ai-connector-anthropic-max';
 const CONFIG = {
 	label: __( 'Anthropic Max' ),
 	description: __(
@@ -534,14 +538,12 @@ const CONFIG = {
 // `registerDefaultConnectors()` from inside an async dynamic import. By the
 // time it executes, our top-level registerConnector() has already populated
 // the store — and the store reducer spreads new config over existing
-// entries, so the default's `args.render = ApiKeyConnector` can overwrite
-// our custom render. We currently dodge this by using a slug that doesn't
-// collide with the PHP-side provider id, but that's fragile (a future
-// upstream change to slug normalization could break it). The proper fix is
-// in WordPress/gutenberg#77116; until that ships we re-assert our
-// registration on five ticks (sync + microtask + setTimeout 0/50/250/1000ms)
-// as defense in depth so our render always ends up last regardless of
-// dynamic-import resolution order.
+// entries, so the default's `args.render = ApiKeyConnector` would overwrite
+// our custom render. The proper fix is in WordPress/gutenberg#77116; until
+// that ships we re-assert our registration on five ticks (sync + microtask
+// + setTimeout 0/50/250/1000ms) so our render always ends up last regardless
+// of dynamic-import resolution order. Re-registering with the same render
+// reference is idempotent so the redundant calls cost essentially nothing.
 function registerOurs() {
 	registerConnector( SLUG, CONFIG );
 }

package.json

@@ -1,6 +1,6 @@
 {
     "name": "ai-provider-for-anthropic-max",
-    "version": "1.0.1",
+    "version": "1.1.0",
     "private": true,
     "license": "GPL-2.0-or-later",
     "scripts": {

plugin.php

@@ -5,7 +5,7 @@
  * Description: Anthropic provider for the WordPress AI Client using Claude Max OAuth tokens with account pool rotation.
  * Requires at least: 6.9
  * Requires PHP: 7.4
- * Version: 1.0.1
+ * Version: 1.1.0
  * Author: Ultimate Multisite Community
  * Author URI: https://ultimatemultisite.com
  * License: GPL-2.0-or-later
@@ -21,7 +21,7 @@
 	return;
 }
 
-define( 'ANTHROPIC_MAX_AI_PROVIDER_VERSION', '1.0.1' );
+define( 'ANTHROPIC_MAX_AI_PROVIDER_VERSION', '1.1.0' );
 
 // ---------------------------------------------------------------------------
 // PSR-4 autoloader for src/ classes.

readme.txt

@@ -3,7 +3,7 @@ Contributors: superdav42
 Tags: ai, anthropic, claude, oauth, max
 Requires at least: 6.9
 Tested up to: 7.0
-Stable tag: 1.0.1
+Stable tag: 1.1.0
 Requires PHP: 7.4
 License: GPL-2.0-or-later
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
@@ -65,9 +65,11 @@ OAuth tokens are stored in the WordPress options table. Only site administrators
 
 == Changelog ==
 
-= 1.0.1 =
+= 1.1.0 =
 
-* Defensive: re-assert our `registerConnector()` call across multiple ticks (microtask + 0/50/250/1000 ms) so the WP core `registerDefaultConnectors()` auto-register can't clobber the custom card with the generic API-key UI. Today this plugin happens to escape the bug because its JS slug doesn't collide with the PHP-side provider id, but that's fragile. The proper upstream fix is in https://github.com/WordPress/gutenberg/pull/77116 — once that ships in a Gutenberg release, this defense can be removed.
+* **BREAKING**: renamed the AI Client provider id from `anthropic-max` to `ultimate-ai-connector-anthropic-max` for consistency with the sister plugins (`ultimate-ai-connector-webllm`, `ultimate-ai-connector-compatible-endpoints`) and to claim the namespace properly. Code that called `AiClient::defaultRegistry()->getProvider('anthropic-max')` must update the id. Stored OAuth tokens, REST endpoints, and option keys are unchanged so existing setups continue to work.
+* Improved: the JS-side `registerConnector()` slug now matches the PHP provider id, so the WP core Connectors page renders one card instead of two (a previously-hidden duplicate auto-registered card with the generic API-key form is now suppressed).
+* Fix: re-assert our `registerConnector()` call across multiple ticks (microtask + 0/50/250/1000 ms) so the WP core `registerDefaultConnectors()` auto-register can't clobber the custom card with the generic API-key UI. Necessary because matching the slug exposes us to the same race the other Ultimate-Multisite connector plugins hit. The proper upstream fix is in https://github.com/WordPress/gutenberg/pull/77116 — once that ships in a Gutenberg release, this workaround can be removed.
 
 = 1.0.0 =
 

src/Provider/AnthropicMaxProvider.php

@@ -2,8 +2,8 @@
 /**
  * Anthropic Max provider for the WordPress AI Client.
  *
- * Registers as a separate provider ('anthropic-max') so it can coexist
- * with the standard API-key-based Anthropic provider.
+ * Registers as a separate provider ('ultimate-ai-connector-anthropic-max')
+ * so it can coexist with the standard API-key-based Anthropic provider.
  *
  * @since 1.0.0
  *
@@ -77,17 +77,25 @@ protected static function createModel(
     /**
      * Creates the provider metadata.
      *
-     * Uses 'anthropic-max' as the provider ID to avoid conflicts
-     * with the standard API-key-based Anthropic provider.
+     * Uses 'ultimate-ai-connector-anthropic-max' as the provider ID. The
+     * `ultimate-ai-connector-` namespace matches the sister plugins
+     * (`ultimate-ai-connector-webllm`, `ultimate-ai-connector-compatible-endpoints`)
+     * and avoids any future collision with another plugin author who might
+     * register a generic 'anthropic-max' provider id.
      *
-     * @since 1.0.0
+     * @since 1.0.0 As 'anthropic-max'.
+     * @since 1.1.0 Renamed to 'ultimate-ai-connector-anthropic-max' for
+     *              consistency with other Ultimate-Multisite connector plugins
+     *              and to make the JS-side `registerConnector()` slug match
+     *              this id (so the WP core Connectors page renders one card
+     *              instead of two).
      *
      * @return ProviderMetadata
      */
     protected static function createProviderMetadata(): ProviderMetadata
     {
         $args = [
-            'anthropic-max',
+            'ultimate-ai-connector-anthropic-max',
             'Anthropic Max',
             ProviderTypeEnum::cloud(),
             null,