@babelforce/babelconnect-sdk 0.12.0 → 0.13.0

package/dist/gen/babelconnect/v1/babelconnect_connect.d.ts

@@ -19,28 +19,15 @@ export declare const Agent: {
             readonly kind: MethodKind.Unary;
         };
         /**
-         * Session opens the long-lived control stream. The client sends Command
-         * intents; the server streams StateUpdate (one snapshot on open, then
-         * entity-level patches). UI = f(AgentView).
-         *
-         * Native clients (Go/Dart desktop/mobile over HTTP/2) use this bidi stream.
-         *
-         * @generated from rpc babelconnect.v1.Agent.Session
-         */
-        readonly session: {
-            readonly name: "Session";
-            readonly I: typeof Command;
-            readonly O: typeof StateUpdate;
-            readonly kind: MethodKind.BiDiStreaming;
-        };
-        /**
-         * Subscribe + Send are the browser-friendly split of Session: a browser speaks
-         * gRPC-web, which cannot client-stream, so the bidi Session is impossible there.
-         * Subscribe is the server→client half (the StateUpdate stream); Send is the
-         * client→server half (one Command per unary call). Together they are equivalent
-         * to Session for a single agent — the server keys both to the agent's one state
-         * store. Command rejections still arrive as an Error on the Subscribe stream
-         * (never on Send's reply), exactly as on Session.
+         * Subscribe + Send are the control stream, split into its server→client and
+         * client→server halves — the one shape every client uses (RPC-A4 retired the
+         * earlier bidi `Session` RPC, which needed HTTP/2 end-to-end and couldn't
+         * ride gRPC-web or a plain HTTP/1.1 ingress). Subscribe is the server→client
+         * half (StateUpdate: one snapshot on open, then entity-level patches; UI =
+         * f(AgentView)). Send is the client→server half (one Command per unary
+         * call). Together they key to the agent's one state store. Command
+         * rejections arrive as an Error on the Subscribe stream, never on Send's
+         * reply.
          *
          * @generated from rpc babelconnect.v1.Agent.Subscribe
          */

package/dist/gen/babelconnect/v1/babelconnect_connect.js

@@ -3,30 +3,35 @@
 /* eslint-disable */
 // @ts-nocheck
 // Package babelconnect.v1 is the control protocol between a babelconnect client
-// (the SDK, via Go/Dart/gRPC-web) and babelconnect-server. It carries CONTROL
-// ONLY — media is WebRTC on a separate plane; the server terminates the client's
-// WebRTC leg.
+// (the SDK, via Go/Dart/gRPC-web/Connect) and babelconnect-server. It carries
+// CONTROL ONLY — media is WebRTC on a separate plane; the server terminates the
+// client's WebRTC leg.
 //
 // State lives on the SERVER, not the client. babelconnect-server holds the
 // canonical per-agent AgentView and pushes an initial snapshot + entity-level
-// patches over the Session stream; clients are DUMB RENDERERS — they apply
+// patches over the Subscribe stream; clients are DUMB RENDERERS — they apply
 // patches mechanically and send Command intents, with no domain logic.
 //
-// Two entry points:
+// Three entry points:
 //   - Authenticate: unary handshake → the agent's identity.
-//   - Session:      a long-lived bidi stream. Client → server: Command intents
-//                   (register/place/answer/hangup/mute/...). Server → client:
-//                   StateUpdate (snapshot then patches). The WebRTC offer rides
-//                   on CallState (when RINGING); the client answers via the
-//                   AnswerCall intent — signaling fits the state model, no
-//                   separate event channel.
+//   - Subscribe:    the server→client half — StateUpdate (snapshot then
+//                    patches). The WebRTC offer rides on CallState (when
+//                    RINGING); the client answers via the AnswerCall intent —
+//                    signaling fits the state model, no separate event channel.
+//   - Send:         the client→server half — one Command intent per call
+//                    (register/place/answer/hangup/mute/...). Together with
+//                    Subscribe this is the one blessed shape for every client
+//                    (RPC-A4 retired the earlier bidi `Session` RPC once all
+//                    clients had moved onto this split over the Connect
+//                    protocol).
 //
 // The bearer token travels in gRPC metadata ("authorization: Bearer <token>")
 // on every call; Authenticate additionally returns the resolved identity.
 //
-// In addition to gRPC/gRPC-web, the unary RPCs are exposed as a REST+JSON surface
-// via grpc-gateway (the google.api.http annotations below) with an OpenAPI v2 spec
-// — one proto source of truth, two wire surfaces. Streaming stays gRPC/gRPC-web.
+// In addition to gRPC/gRPC-web/Connect, the unary RPCs are exposed as a
+// REST+JSON surface via grpc-gateway (the google.api.http annotations below)
+// with an OpenAPI v2 spec — one proto source of truth, two wire surfaces.
+// Streaming stays gRPC/gRPC-web/Connect.
 import { Ack, AgentView, AuthenticateRequest, Command, GetStateRequest, HistoryRequest, HistoryResponse, Identity, ListCampaignsRequest, ListCampaignsResponse, ListDispositionsRequest, ListDispositionsResponse, PhonebookRequest, PhonebookResponse, SendSmsRequest, SmsConversation, SmsThreadRequest, SmsThreadResponse, StateUpdate, SubscribeRequest, TransferTargetsRequest, TransferTargetsResponse } from "./babelconnect_pb.js";
 import { MethodKind } from "@bufbuild/protobuf";
 /**
@@ -48,28 +53,15 @@ export const Agent = {
             kind: MethodKind.Unary,
         },
         /**
-         * Session opens the long-lived control stream. The client sends Command
-         * intents; the server streams StateUpdate (one snapshot on open, then
-         * entity-level patches). UI = f(AgentView).
-         *
-         * Native clients (Go/Dart desktop/mobile over HTTP/2) use this bidi stream.
-         *
-         * @generated from rpc babelconnect.v1.Agent.Session
-         */
-        session: {
-            name: "Session",
-            I: Command,
-            O: StateUpdate,
-            kind: MethodKind.BiDiStreaming,
-        },
-        /**
-         * Subscribe + Send are the browser-friendly split of Session: a browser speaks
-         * gRPC-web, which cannot client-stream, so the bidi Session is impossible there.
-         * Subscribe is the server→client half (the StateUpdate stream); Send is the
-         * client→server half (one Command per unary call). Together they are equivalent
-         * to Session for a single agent — the server keys both to the agent's one state
-         * store. Command rejections still arrive as an Error on the Subscribe stream
-         * (never on Send's reply), exactly as on Session.
+         * Subscribe + Send are the control stream, split into its server→client and
+         * client→server halves — the one shape every client uses (RPC-A4 retired the
+         * earlier bidi `Session` RPC, which needed HTTP/2 end-to-end and couldn't
+         * ride gRPC-web or a plain HTTP/1.1 ingress). Subscribe is the server→client
+         * half (StateUpdate: one snapshot on open, then entity-level patches; UI =
+         * f(AgentView)). Send is the client→server half (one Command per unary
+         * call). Together they key to the agent's one state store. Command
+         * rejections arrive as an Error on the Subscribe stream, never on Send's
+         * reply.
          *
          * @generated from rpc babelconnect.v1.Agent.Subscribe
          */

package/dist/gen/babelconnect/v1/babelconnect_pb.d.ts

@@ -235,7 +235,7 @@ export declare class SubscribeRequest extends Message<SubscribeRequest> {
 /**
  * Ack is the empty reply to Send. It only confirms the server accepted the
  * command for processing — the resulting state (or an Error) is delivered on the
- * Subscribe stream, the same way Session reports it.
+ * Subscribe stream, never in this reply.
  *
  * @generated from message babelconnect.v1.Ack
  */
@@ -1431,7 +1431,7 @@ export declare class WrapUpStatus extends Message<WrapUpStatus> {
     static equals(a: WrapUpStatus | PlainMessage<WrapUpStatus> | undefined, b: WrapUpStatus | PlainMessage<WrapUpStatus> | undefined): boolean;
 }
 /**
- * StateUpdate is the single server → client message on the Session stream. On
+ * StateUpdate is the single server → client message on the Subscribe stream. On
  * open the client receives a snapshot; thereafter partial patches. `seq` is
  * monotonic across snapshot+patch — a gap means the client should resubscribe
  * for a fresh snapshot. `error` is an out-of-band notice (command rejection /
@@ -1493,7 +1493,7 @@ export declare class StateUpdate extends Message<StateUpdate> {
     static equals(a: StateUpdate | PlainMessage<StateUpdate> | undefined, b: StateUpdate | PlainMessage<StateUpdate> | undefined): boolean;
 }
 /**
- * Keepalive is an empty heartbeat frame sent on the Session/Subscribe streams so
+ * Keepalive is an empty heartbeat frame sent on the Subscribe stream so
  * idle connections through proxies/LBs are not closed as idle. Notably the AWS
  * Classic ELB in front of ingress-nginx (dev/prod EKS) has a 300s connection
  * idle timeout; without these frames a quiet agent's gRPC-web server-stream is

package/dist/gen/babelconnect/v1/babelconnect_pb.js

@@ -323,7 +323,7 @@ export class SubscribeRequest extends Message {
 /**
  * Ack is the empty reply to Send. It only confirms the server accepted the
  * command for processing — the resulting state (or an Error) is delivered on the
- * Subscribe stream, the same way Session reports it.
+ * Subscribe stream, never in this reply.
  *
  * @generated from message babelconnect.v1.Ack
  */
@@ -2009,7 +2009,7 @@ export class WrapUpStatus extends Message {
     }
 }
 /**
- * StateUpdate is the single server → client message on the Session stream. On
+ * StateUpdate is the single server → client message on the Subscribe stream. On
  * open the client receives a snapshot; thereafter partial patches. `seq` is
  * monotonic across snapshot+patch — a gap means the client should resubscribe
  * for a fresh snapshot. `error` is an out-of-band notice (command rejection /
@@ -2056,7 +2056,7 @@ export class StateUpdate extends Message {
     }
 }
 /**
- * Keepalive is an empty heartbeat frame sent on the Session/Subscribe streams so
+ * Keepalive is an empty heartbeat frame sent on the Subscribe stream so
  * idle connections through proxies/LBs are not closed as idle. Notably the AWS
  * Classic ELB in front of ingress-nginx (dev/prod EKS) has a 300s connection
  * idle timeout; without these frames a quiet agent's gRPC-web server-stream is

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const SDK_VERSION = "0.12.0";
+export declare const SDK_VERSION = "0.13.0";

package/dist/version.js

@@ -1,3 +1,3 @@
 // Generated by scripts/gen-version.mjs (npm prebuild) from package.json.
 // Do not edit by hand.
-export const SDK_VERSION = "0.12.0";
+export const SDK_VERSION = "0.13.0";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@babelforce/babelconnect-sdk",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "description": "TypeScript SDK for babelconnect — server-authoritative agent state over gRPC-web, native WebRTC audio, and an embeddable widget (iframe + postMessage) for the Flutter web app.",
   "license": "Apache-2.0",
   "homepage": "https://babelforce.github.io/babelconnect-sdk/",