@envarai/connect 2026.1110.1 → 2026.1110.2

package/README.md

@@ -28,7 +28,7 @@ For the independent seller-side developer path, start with [EnvarPay](https://gi
 ## Install
 
 ```sh
-npm install --global --ignore-scripts @envarai/connect@2026.1110.1
+npm install --global --ignore-scripts @envarai/connect@2026.1110.2
 envar-connect --version
 ```
 

package/dist/connector/client.d.ts

@@ -23,6 +23,9 @@ export interface ConnectionStatus {
     platform: string;
     revision: number;
     readiness: Record<string, unknown>;
+    protocol_support?: {
+        a2a_relay_v1?: boolean;
+    };
 }
 export declare class EnvarWorkClient {
     readonly origin: string;

package/dist/connector/client.js

@@ -92,6 +92,11 @@ export class EnvarWorkClient {
         return await this.request('/api/v1/agent-connections/current/credential', {}, undefined, 'DELETE');
     }
     async relayHello(cardDigest) {
+        // Older product routers can return 403 for an unknown protocol route.
+        // Negotiate through the existing authenticated connection endpoint first;
+        // never reinterpret a real handshake authorization failure as support.
+        if ((await this.status()).protocol_support?.a2a_relay_v1 !== true)
+            return false;
         try {
             const value = await this.request('/api/v1/connector/a2a-relay/hello', {
                 relay_version: '1', a2a_wire_version: '1.0', runtime_card_digest: cardDigest,

package/docs/a2a-relay.md

@@ -33,3 +33,9 @@ cancellation, durable lookup after native runtime restart, media artifacts and
 streaming remain unverified and disabled. A package version or Card claim alone
 cannot enable these capabilities. Upgrade through the existing connection
 instructions, preserving credentials, native binding, SQLite journal and lock.
+
+Connect 2026.1110.2 reads authenticated connection status first and negotiates
+relay only when the server explicitly advertises `a2a_relay_v1: true`. An older
+server or a paused relay therefore continues Work v1 without a request to an
+unknown route. Actual 401/403 authorization failures remain fatal; they are
+never treated as evidence of protocol compatibility.

package/docs/compatibility.md

@@ -3,7 +3,7 @@
 Install the release documented by this checkout:
 
 ```sh
-npm install --global --ignore-scripts @envarai/connect@2026.1110.1
+npm install --global --ignore-scripts @envarai/connect@2026.1110.2
 envar-connect --version
 ```
 

package/docs/native-connector.md

@@ -18,7 +18,7 @@ Replace `CONTAINER` with your container name. Run `node --version` there. On a l
 Create a private Envar Agent and copy its connection command. The command installs a fixed, bundled package through Envar and selects that exact Agent ID. The official npm package is also available:
 
 ```sh
-npm install --prefix "$HOME/.envarpay/cli" --ignore-scripts --no-audit --no-fund @envarai/connect@2026.1110.1
+npm install --prefix "$HOME/.envarpay/cli" --ignore-scripts --no-audit --no-fund @envarai/connect@2026.1110.2
 "$HOME/.envarpay/cli/node_modules/.bin/envar-connect" connect --agent AGENT_UUID --framework hermes
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@envarai/connect",
-  "version": "2026.1110.1",
+  "version": "2026.1110.2",
   "description": "Connect your own Agent to Envar: tasks, native adapters and recovery",
   "type": "module",
   "license": "MIT",