@alfe.ai/claude-code-host 0.1.3 → 0.1.4

package/dist/index.d.cts

@@ -542,8 +542,11 @@ declare class AgentApiClient {
    * else the driver needs for routing (handle, pdsHost, did, …) is on
    * `providerMetadata`.
    *
-   * Token refresh is delegated to connect (never done in-plugin) via
-   * `POST /agent/connect/{provider}/refresh` — not exposed here.
+   * Token refresh is delegated to connect (never done in-plugin) via the
+   * per-account route `POST /agent/connect/{provider}/accounts/{accountIdentifier}/refresh`
+   * — call `refreshSocialAccount(provider, accountIdentifier)`. (The non-account
+   * `POST /agent/connect/{provider}/refresh` route refreshes the provider's
+   * PRIMARY connection, which is wrong under multi-account Pattern A.)
    */
   getSocialAccounts(provider: string): Promise<{
     provider: string;
@@ -556,6 +559,29 @@ declare class AgentApiClient {
       connectedAt: string;
     }[];
   }>;
+  /**
+   * Pattern A: refresh a specific social Connection by its stable
+   * `accountIdentifier` (for Bluesky: the account DID) via the
+   * provider-generic per-account refresh route. The counterpart to
+   * `getSocialAccounts(provider)`; `@alfe.ai/social-mcp` calls this on a
+   * 401/ExpiredToken from the platform PDS/API, then re-fetches accounts to
+   * pick up the rotated bundle.
+   *
+   * Refresh itself is ALWAYS delegated to connect — the plugin never calls
+   * the platform's own refresh XRPC (e.g. `com.atproto.server.refreshSession`)
+   * because connect owns the encrypted refresh token + rotation persistence
+   * (Bluesky rotates the refreshJwt; a missed rotation kills the connection
+   * after one refresh). The returned `accessToken` is whatever the provider's
+   * `refreshToken` hook re-bundled (for Bluesky: the JSON session bundle with
+   * the fresh `accessJwt`) — callers typically ignore it and re-fetch via
+   * `getSocialAccounts` for a consistent shape.
+   */
+  refreshSocialAccount(provider: string, accountIdentifier: string): Promise<{
+    accountIdentifier: string;
+    accessToken: string;
+    accessTokenExpiresAt: string;
+    expiresAt: string;
+  }>;
   /**
    * @deprecated Returns a single primary credential blob (legacy "pick-the-
    * default-connection" shape). Use `getXeroAccounts()` for the multi-
@@ -791,6 +817,45 @@ declare class AgentApiClient {
     accessTokenExpiresAt: string;
     expiresAt: string;
   }>;
+  /**
+   * @deprecated Returns a single primary credential blob. Use
+   * `getShopifyAccounts()` for the multi-account shape required by Pattern A
+   * (`@alfe.ai/shopify-mcp` keys per-shop on the myshopify domain).
+   */
+  getShopifyCredentials(): Promise<{
+    accessToken: string;
+    shopDomain: string;
+    shopGid: string;
+    shopName: string;
+    apiVersion: string;
+  }>;
+  /**
+   * Pattern A: multi-account credential fetch for Shopify. Returns every
+   * agent-scoped Shopify Connection. One OAuth grant maps to one store, so the
+   * stable per-call selector is the store's myshopify domain (`shopDomain`),
+   * NOT `accountIdentifier` — the connect provider keys `accountIdentifier` on
+   * the immutable shop GID (falling back to the domain), so `shopDomain` is the
+   * value the LLM passes and the plugin routes on.
+   *
+   * Each entry is shaped by the connect provider's `buildCredentialsResponse`:
+   * `{ accessToken, shopDomain, shopGid, shopName, apiVersion }` — offline
+   * Shopify tokens never expire, so there is NO token / expiry field and no
+   * refresh method (unlike Salesforce). The GraphQL Admin API authenticates
+   * purely on `X-Shopify-Access-Token`; no client credentials are on the wire.
+   */
+  getShopifyAccounts(): Promise<{
+    accounts: {
+      connectionId: string;
+      accountIdentifier: string;
+      displayName: string | null;
+      connectedAt: string;
+      accessToken: string;
+      shopDomain: string;
+      shopGid: string;
+      shopName: string;
+      apiVersion: string;
+    }[];
+  }>;
   /**
    * Disconnects one connected Microsoft 365 account for the agent, by its
    * `accountIdentifier`. Hits the generic per-account disconnect route

package/dist/index.d.ts

@@ -542,8 +542,11 @@ declare class AgentApiClient {
    * else the driver needs for routing (handle, pdsHost, did, …) is on
    * `providerMetadata`.
    *
-   * Token refresh is delegated to connect (never done in-plugin) via
-   * `POST /agent/connect/{provider}/refresh` — not exposed here.
+   * Token refresh is delegated to connect (never done in-plugin) via the
+   * per-account route `POST /agent/connect/{provider}/accounts/{accountIdentifier}/refresh`
+   * — call `refreshSocialAccount(provider, accountIdentifier)`. (The non-account
+   * `POST /agent/connect/{provider}/refresh` route refreshes the provider's
+   * PRIMARY connection, which is wrong under multi-account Pattern A.)
    */
   getSocialAccounts(provider: string): Promise<{
     provider: string;
@@ -556,6 +559,29 @@ declare class AgentApiClient {
       connectedAt: string;
     }[];
   }>;
+  /**
+   * Pattern A: refresh a specific social Connection by its stable
+   * `accountIdentifier` (for Bluesky: the account DID) via the
+   * provider-generic per-account refresh route. The counterpart to
+   * `getSocialAccounts(provider)`; `@alfe.ai/social-mcp` calls this on a
+   * 401/ExpiredToken from the platform PDS/API, then re-fetches accounts to
+   * pick up the rotated bundle.
+   *
+   * Refresh itself is ALWAYS delegated to connect — the plugin never calls
+   * the platform's own refresh XRPC (e.g. `com.atproto.server.refreshSession`)
+   * because connect owns the encrypted refresh token + rotation persistence
+   * (Bluesky rotates the refreshJwt; a missed rotation kills the connection
+   * after one refresh). The returned `accessToken` is whatever the provider's
+   * `refreshToken` hook re-bundled (for Bluesky: the JSON session bundle with
+   * the fresh `accessJwt`) — callers typically ignore it and re-fetch via
+   * `getSocialAccounts` for a consistent shape.
+   */
+  refreshSocialAccount(provider: string, accountIdentifier: string): Promise<{
+    accountIdentifier: string;
+    accessToken: string;
+    accessTokenExpiresAt: string;
+    expiresAt: string;
+  }>;
   /**
    * @deprecated Returns a single primary credential blob (legacy "pick-the-
    * default-connection" shape). Use `getXeroAccounts()` for the multi-
@@ -791,6 +817,45 @@ declare class AgentApiClient {
     accessTokenExpiresAt: string;
     expiresAt: string;
   }>;
+  /**
+   * @deprecated Returns a single primary credential blob. Use
+   * `getShopifyAccounts()` for the multi-account shape required by Pattern A
+   * (`@alfe.ai/shopify-mcp` keys per-shop on the myshopify domain).
+   */
+  getShopifyCredentials(): Promise<{
+    accessToken: string;
+    shopDomain: string;
+    shopGid: string;
+    shopName: string;
+    apiVersion: string;
+  }>;
+  /**
+   * Pattern A: multi-account credential fetch for Shopify. Returns every
+   * agent-scoped Shopify Connection. One OAuth grant maps to one store, so the
+   * stable per-call selector is the store's myshopify domain (`shopDomain`),
+   * NOT `accountIdentifier` — the connect provider keys `accountIdentifier` on
+   * the immutable shop GID (falling back to the domain), so `shopDomain` is the
+   * value the LLM passes and the plugin routes on.
+   *
+   * Each entry is shaped by the connect provider's `buildCredentialsResponse`:
+   * `{ accessToken, shopDomain, shopGid, shopName, apiVersion }` — offline
+   * Shopify tokens never expire, so there is NO token / expiry field and no
+   * refresh method (unlike Salesforce). The GraphQL Admin API authenticates
+   * purely on `X-Shopify-Access-Token`; no client credentials are on the wire.
+   */
+  getShopifyAccounts(): Promise<{
+    accounts: {
+      connectionId: string;
+      accountIdentifier: string;
+      displayName: string | null;
+      connectedAt: string;
+      accessToken: string;
+      shopDomain: string;
+      shopGid: string;
+      shopName: string;
+      apiVersion: string;
+    }[];
+  }>;
   /**
    * Disconnects one connected Microsoft 365 account for the agent, by its
    * `accountIdentifier`. Hits the generic per-account disconnect route

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alfe.ai/claude-code-host",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Chat bridge that makes a self-hosted Claude Code agent reachable from Alfe chat on the user's Claude subscription",
   "type": "module",
   "main": "./dist/index.js",
@@ -19,7 +19,7 @@
     "dist"
   ],
   "dependencies": {
-    "@alfe.ai/agent-api-client": "^0.11.1",
+    "@alfe.ai/agent-api-client": "^0.12.0",
     "@alfe.ai/chat": "^0.0.16",
     "@alfe.ai/config": "^0.3.0"
   },