@oxyhq/contracts 0.13.0 → 0.13.1

package/dist/esm/deviceSession.js

@@ -47,3 +47,25 @@ export const deviceTokenMintResponseSchema = z.object({
     nextDeviceSecret: z.string(),
     state: deviceSessionStateSchema,
 });
+/* -------------------------------------------------------------------------- */
+/*  Hub ticket — server-side cross-origin device credential sync               */
+/* -------------------------------------------------------------------------- */
+/** Request body for `POST /session/device/hub-ticket`. */
+export const deviceHubTicketIssueRequestSchema = z.object({
+    returnOrigin: z.string().min(1),
+});
+/** Response from `POST /session/device/hub-ticket`. */
+export const deviceHubTicketIssueResponseSchema = z.object({
+    ticket: z.string().min(1),
+    expiresIn: z.number().int().positive(),
+});
+/** Request body for `POST /session/device/redeem-ticket`. */
+export const deviceHubTicketRedeemRequestSchema = z.object({
+    ticket: z.string().min(1),
+    returnOrigin: z.string().min(1),
+});
+/** Response from `POST /session/device/redeem-ticket`. */
+export const deviceHubTicketRedeemResponseSchema = z.object({
+    deviceId: z.string().min(1),
+    deviceSecret: z.string().min(1),
+});

package/dist/esm/index.js

@@ -2,7 +2,7 @@
  * @oxyhq/contracts — single source of truth for API request/response contracts.
  *
  * Zod schemas plus their inferred types, shared by the backend (`@oxyhq/api`)
- * and the client SDKs (`@oxyhq/core`, `@oxyhq/auth`, `@oxyhq/services`). The
+ * and the client SDKs (`@oxyhq/core`, `@oxyhq/services`). The
  * producer validates its output and every consumer validates its input against
  * exactly the same definitions, so the wire shape cannot drift.
  *
@@ -19,9 +19,6 @@ export {
 applicationTypeSchema, publicApplicationSchema, sessionStatusSchema, } from './sessionStatus.js';
 export { 
 // Schemas
-fedcmTokenPayloadSchema, } from './fedcmToken.js';
-export { 
-// Schemas
 recommendationExcludeTypeSchema, recommendationBoostSchema, recommendationSignalWeightsSchema, recommendationRequestSchema, recommendationCountSchema, recommendationItemSchema, recommendationResponseSchema, appEndorsementInputSchema, appInterestInputSchema, appUserSignalIngestSchema, appAffinityEventTypeSchema, appAffinityEventSchema, appAffinityEventsIngestSchema, } from './recommendations.js';
 export { 
 // Schemas
@@ -40,7 +37,7 @@ credentialRecordSchema, verifiableCredentialResponseSchema, credentialIssueResul
 export { 
 // Schemas
 linkPreviewSchema, linkPreviewBatchRequestSchema, linkPreviewBatchResponseSchema, linkPreviewResponseSchema, } from './links.js';
-export { sessionAccountSchema, deviceSessionStateSchema, activeTokenSchema, deviceSessionSyncSchema, deviceTokenMintRequestSchema, deviceTokenMintResponseSchema, } from './deviceSession.js';
+export { sessionAccountSchema, deviceSessionStateSchema, activeTokenSchema, deviceSessionSyncSchema, deviceTokenMintRequestSchema, deviceTokenMintResponseSchema, deviceHubTicketIssueRequestSchema, deviceHubTicketIssueResponseSchema, deviceHubTicketRedeemRequestSchema, deviceHubTicketRedeemResponseSchema, } from './deviceSession.js';
 export { 
 // Schemas
 loginResultSchema, } from './deviceBoot.js';

package/dist/esm/userResponse.js

@@ -11,7 +11,7 @@
  *
  * This package (`@oxyhq/contracts`) is the dedicated, zero-dependency home for
  * these contracts so the backend (`@oxyhq/api`) and the client SDKs
- * (`@oxyhq/core`, `@oxyhq/auth`, `@oxyhq/services`) can all depend on it without
+ * (`@oxyhq/core`, `@oxyhq/services`) can all depend on it without
  * the backend having to depend on a client SDK to obtain its schemas.
  *
  * Faithful to the producers: