@vellumai/credential-executor 0.10.11-dev.202607220955.d4134f8 → 0.10.11-dev.202607221733.6d056db

package/node_modules/@vellumai/service-contracts/package.json

@@ -10,6 +10,7 @@
     "./client-metadata": "./src/client-metadata.ts",
     "./credential-rpc": "./src/credential-rpc.ts",
     "./ingress": "./src/ingress.ts",
+    "./remote-web-pairing": "./src/remote-web-pairing.ts",
     "./twilio-ingress": "./src/twilio-ingress.ts",
     "./trust-rules": "./src/trust-rules.ts",
     "./handles": "./src/handles.ts",

package/node_modules/@vellumai/service-contracts/src/index.ts

@@ -26,4 +26,5 @@ export * from "./handles.js";
 export * from "./rpc.js";
 export * from "./trust-rules.js";
 export * from "./ingress.js";
+export * from "./remote-web-pairing.js";
 export * from "./twilio-ingress.js";

package/node_modules/@vellumai/service-contracts/src/remote-web-pairing.ts

@@ -0,0 +1,102 @@
+/**
+ * Wire contracts for the remote-web pairing flow — the RFC 8628-style
+ * device-code exchange that connects a browser (or the iOS app) to a
+ * self-hosted assistant over its public ingress URL.
+ *
+ * The gateway routes are the authoritative serving side:
+ *   - `POST /v1/remote-web/pairing-challenge`     mint a challenge
+ *       (`gateway/src/http/routes/remote-web-pairing-challenge.ts`,
+ *        `gateway/src/remote-web/pairing-challenge-store.ts`)
+ *   - `POST /v1/remote-web/pairing-verification`  approve by user code
+ *       (`gateway/src/http/routes/remote-web-pairing-verification.ts`)
+ *   - `POST /v1/remote-web/pairing-token`         poll + exchange device code
+ *       (`gateway/src/http/routes/remote-web-pairing-token.ts`)
+ *
+ * These shapes mirror those handlers' request/response bodies exactly so the
+ * gateway, the `vellum pair` CLI (`cli/src/commands/pair.ts`), and the web SPA
+ * (`clients/web/src/lib/auth/remote-gateway-session.ts`) share one definition
+ * and cannot silently drift.
+ *
+ * Timestamps are ISO-8601 strings — every gateway response serializes them via
+ * `Date#toISOString()`.
+ */
+
+/** `POST /v1/remote-web/pairing-challenge` request body. */
+export interface RemoteWebPairingChallengeRequest {
+  /** Public https base URL the scanning device can reach the assistant at. */
+  publicBaseUrl: string;
+}
+
+/** `POST /v1/remote-web/pairing-challenge` success response body (200). */
+export interface RemoteWebPairingChallengeResponse {
+  /** Opaque secret the paired device exchanges for a token. */
+  deviceCode: string;
+  /** Short human-readable code the host approves out of band. */
+  userCode: string;
+  /** URL the device opens to complete pairing. */
+  verificationUri: string;
+  /** ISO-8601 instant the challenge expires. */
+  expiresAt: string;
+  /** Seconds until the challenge expires. */
+  expiresInSeconds: number;
+  /** Recommended poll interval (seconds) for the token-exchange endpoint. */
+  intervalSeconds: number;
+}
+
+/** `POST /v1/remote-web/pairing-verification` request body. */
+export interface RemoteWebPairingVerificationRequest {
+  /** The `userCode` from the challenge, entered/scanned on the host. */
+  userCode: string;
+}
+
+/**
+ * `POST /v1/remote-web/pairing-verification` success response body (200).
+ *
+ * The gateway maps the `expired` / `invalid` outcomes to error responses, so
+ * the only success shape on the wire is the approved variant.
+ */
+export interface RemoteWebPairingVerificationResponse {
+  status: "approved";
+  verificationUri: string;
+  /** ISO-8601 instant the approved challenge expires. */
+  expiresAt: string;
+}
+
+/** `POST /v1/remote-web/pairing-token` request body. */
+export interface RemoteWebPairingTokenRequest {
+  /** The `deviceCode` from the challenge. */
+  deviceCode: string;
+}
+
+/**
+ * `POST /v1/remote-web/pairing-token` still-pending response body (202) — the
+ * challenge exists but has not been approved yet, so the client keeps polling.
+ */
+export interface RemoteWebPairingTokenPendingResponse {
+  status: "pending";
+  /** ISO-8601 instant the challenge expires. */
+  expiresAt: string;
+  /** Recommended poll interval (seconds) before the next exchange attempt. */
+  intervalSeconds: number;
+}
+
+/**
+ * `POST /v1/remote-web/pairing-token` approved response body (200) — carries
+ * the minted browser session credentials. The refresh token is delivered out
+ * of band as an `HttpOnly` cookie, not in this body.
+ */
+export interface RemoteWebPairingTokenApprovedResponse {
+  status: "approved";
+  accessToken: string;
+  /** ISO-8601 instant the access token expires. */
+  accessTokenExpiresAt: string;
+  /** ISO-8601 instant after which the client should refresh the session. */
+  refreshAfter: string;
+  guardianId: string;
+  assistantId: string;
+}
+
+/** Union of the two terminal `pairing-token` response bodies. */
+export type RemoteWebPairingTokenResponse =
+  | RemoteWebPairingTokenPendingResponse
+  | RemoteWebPairingTokenApprovedResponse;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vellumai/credential-executor",
-  "version": "0.10.11-dev.202607220955.d4134f8",
+  "version": "0.10.11-dev.202607221733.6d056db",
   "license": "MIT",
   "type": "module",
   "exports": {