@babelforce/babelconnect-sdk 0.1.0

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

@@ -0,0 +1,161 @@
+// @generated by protoc-gen-connect-es v1.7.0 with parameter "target=ts"
+// @generated from file babelconnect/v1/babelconnect.proto (package babelconnect.v1, syntax proto3)
+/* 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.
+//
+// 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 mechanically and send Command intents, with no domain logic.
+//
+// Two 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.
+//
+// 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.
+import { Ack, AgentView, AuthenticateRequest, Command, GetStateRequest, HistoryRequest, HistoryResponse, Identity, PhonebookRequest, PhonebookResponse, SendSmsRequest, SmsConversation, SmsThreadRequest, SmsThreadResponse, StateUpdate, SubscribeRequest } from "./babelconnect_pb.js";
+import { MethodKind } from "@bufbuild/protobuf";
+/**
+ * @generated from service babelconnect.v1.Agent
+ */
+export const Agent = {
+    typeName: "babelconnect.v1.Agent",
+    methods: {
+        /**
+         * Authenticate validates the caller's bearer token and returns the resolved
+         * agent identity (id, account, presence).
+         *
+         * @generated from rpc babelconnect.v1.Agent.Authenticate
+         */
+        authenticate: {
+            name: "Authenticate",
+            I: AuthenticateRequest,
+            O: Identity,
+            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.
+         *
+         * @generated from rpc babelconnect.v1.Agent.Subscribe
+         */
+        subscribe: {
+            name: "Subscribe",
+            I: SubscribeRequest,
+            O: StateUpdate,
+            kind: MethodKind.ServerStreaming,
+        },
+        /**
+         * @generated from rpc babelconnect.v1.Agent.Send
+         */
+        send: {
+            name: "Send",
+            I: Command,
+            O: Ack,
+            kind: MethodKind.Unary,
+        },
+        /**
+         * GetHistory returns the agent's past calls (the History tab). A unary query —
+         * history is on-demand reference data, not part of the live AgentView snapshot.
+         *
+         * @generated from rpc babelconnect.v1.Agent.GetHistory
+         */
+        getHistory: {
+            name: "GetHistory",
+            I: HistoryRequest,
+            O: HistoryResponse,
+            kind: MethodKind.Unary,
+        },
+        /**
+         * GetSmsThread returns the messages of one SMS conversation (the chat thread).
+         * A unary query like GetHistory — the live AgentView carries only the
+         * SmsConversation summary; the full thread is fetched on demand. conversation_id
+         * is a query param (it can be a peer phone number when no conversation id is
+         * available), so this stays distinct from the POST /v1/agent/sms send.
+         *
+         * @generated from rpc babelconnect.v1.Agent.GetSmsThread
+         */
+        getSmsThread: {
+            name: "GetSmsThread",
+            I: SmsThreadRequest,
+            O: SmsThreadResponse,
+            kind: MethodKind.Unary,
+        },
+        /**
+         * GetPhonebook returns the agent's dial-from contacts + recent numbers (the
+         * Contacts tab). A unary query like GetHistory: the live AgentView carries a
+         * phonebook snapshot frozen at register (AgentInfo.phonebook); this re-pulls the
+         * merged contacts+recents list on demand (refresh) so a long-running session can
+         * see new contacts. `query` filters by label/number.
+         *
+         * @generated from rpc babelconnect.v1.Agent.GetPhonebook
+         */
+        getPhonebook: {
+            name: "GetPhonebook",
+            I: PhonebookRequest,
+            O: PhonebookResponse,
+            kind: MethodKind.Unary,
+        },
+        /**
+         * GetState returns the agent's current AgentView as a single unary call — the
+         * REST/web "get current state" (the Subscribe stream is the realtime twin). When
+         * no live session backs the caller, the server builds the snapshot on demand
+         * (agent + presence + wrap-up); live call state requires a stream.
+         *
+         * @generated from rpc babelconnect.v1.Agent.GetState
+         */
+        getState: {
+            name: "GetState",
+            I: GetStateRequest,
+            O: AgentView,
+            kind: MethodKind.Unary,
+        },
+        /**
+         * SendSms sends an SMS and returns the (upserted) conversation summary. Exposed
+         * over REST as POST /v1/agent/sms and as the Command.send_sms intent on the
+         * stream — both send the same message.
+         *
+         * @generated from rpc babelconnect.v1.Agent.SendSms
+         */
+        sendSms: {
+            name: "SendSms",
+            I: SendSmsRequest,
+            O: SmsConversation,
+            kind: MethodKind.Unary,
+        },
+    }
+};