@oxy.so/contracts 4.11.0-oxy-one.0 → 4.11.0

package/dist/esm/recommendations.js

@@ -13,11 +13,7 @@
 import { z } from 'zod';
 import { userNameSchema } from './userResponse.js';
 /** User-type filters a caller may exclude from the recommendation surface. */
-export const recommendationExcludeTypeSchema = z.enum([
-    'federated',
-    'agent',
-    'automated',
-]);
+export const recommendationExcludeTypeSchema = z.enum(['federated', 'agent', 'automated']);
 /**
  * A caller-supplied editorial boost. `userIds` are nudged up (or down, for a
  * negative weight) in the ranking; the optional `reason` is for audit/telemetry
@@ -122,7 +118,9 @@ export const appUserSignalIngestSchema = z
     endorsements: z.array(appEndorsementInputSchema).max(500).optional(),
     interests: z.array(appInterestInputSchema).max(500).optional(),
 })
-    .refine((value) => (value.endorsements?.length ?? 0) > 0 || (value.interests?.length ?? 0) > 0, { message: 'At least one of endorsements or interests must be non-empty' });
+    .refine((value) => (value.endorsements?.length ?? 0) > 0 || (value.interests?.length ?? 0) > 0, {
+    message: 'At least one of endorsements or interests must be non-empty',
+});
 /**
  * The directed interaction types a consuming app may report between two users.
  * Each type carries a server-side default weight (see the API's

package/dist/esm/reputation.js

@@ -24,8 +24,8 @@
  *  - **The balance has two views, and the union is the contract.** See
  *    {@link ReputationBalanceView} — the compile-time assertions below are what
  *    stop the private view's fields becoming reachable on a stranger's balance.
- *  - **The closed value sets live here, not beside the mongoose models.** The
- *    API's model enums and the SDK's unions are the same `as const` tuple, so a
+ *  - **The closed value sets live here, not beside the database schema.** The
+ *    API's column enums and the SDK's unions are the same `as const` tuple, so a
  *    seventh category cannot be added on one side only.
  *
  * The response entities are declared as explicit `interface`s with their runtime
@@ -74,10 +74,7 @@ export const reputationCategorySchema = z.enum(REPUTATION_CATEGORIES);
  *                only by policy-driven code, never by a person); the pair nets
  *                to zero.
  */
-export const REPUTATION_TRANSACTION_STATUSES = [
-    'active',
-    'reversed',
-];
+export const REPUTATION_TRANSACTION_STATUSES = ['active', 'reversed'];
 export const reputationTransactionStatusSchema = z.enum(REPUTATION_TRANSACTION_STATUSES);
 /**
  * Trust tiers, lowest → highest trust, plus the punitive `restricted`.

package/dist/esm/sessionStatus.js

@@ -40,12 +40,7 @@ import { z } from 'zod';
  * `packages/api/src/models/Application.ts` (`first_party` | `third_party` |
  * `internal` | `system`).
  */
-export const applicationTypeSchema = z.enum([
-    'first_party',
-    'third_party',
-    'internal',
-    'system',
-]);
+export const applicationTypeSchema = z.enum(['first_party', 'third_party', 'internal', 'system']);
 /**
  * The display-safe public identity of a requesting application, exactly as
  * `serializePublicApplication` emits it. Returned by the API inside

package/dist/esm/signIn.js

@@ -119,7 +119,9 @@ export const emailSignInCodeSchema = z
     const code = normalizeEmailSignInCode(value);
     return (new RegExp(`^\\d{${EMAIL_CODE_LENGTH}}$`).test(code) ||
         new RegExp(`^[${EMAIL_SIGNIN_LONG_CODE_ALPHABET}]{${EMAIL_SIGNIN_LONG_CODE_LENGTH}}$`).test(code));
-}, { message: `code must be ${EMAIL_CODE_LENGTH} digits or the ${EMAIL_SIGNIN_LONG_CODE_LENGTH}-character code from the email` });
+}, {
+    message: `code must be ${EMAIL_CODE_LENGTH} digits or the ${EMAIL_SIGNIN_LONG_CODE_LENGTH}-character code from the email`,
+});
 /** `POST /auth/signin/email/confirm` — the code from the email. */
 export const emailSignInConfirmRequestSchema = z
     .object({
@@ -194,7 +196,13 @@ export function isSecondFactorRequired(result) {
  * What a re-verification email code confirms. The code is bound to it: a code
  * asked for one change never authorises another, and the email names it.
  */
-export const REAUTH_ACTIONS = ['change_password', 'totp', 'link_commons', 'delete_account', 'credentials_manage'];
+export const REAUTH_ACTIONS = [
+    'change_password',
+    'totp',
+    'link_commons',
+    'delete_account',
+    'credentials_manage',
+];
 /** `POST /users/me/reauth/email` */
 export const reauthEmailStartRequestSchema = z.object({ action: z.enum(REAUTH_ACTIONS) }).strict();
 /**
@@ -254,14 +262,19 @@ export const totpEnrollResponseSchema = z.object({
 /** `POST /users/me/totp/confirm` — the first code from the authenticator turns it on. */
 export const totpConfirmRequestSchema = z
     .object({
-    code: z.string().trim().regex(new RegExp(`^\\d{${TOTP_DIGITS}}$`)),
+    code: z
+        .string()
+        .trim()
+        .regex(new RegExp(`^\\d{${TOTP_DIGITS}}$`)),
     reauth: reauthProofSchema,
 })
     .strict();
 /** `POST /users/me/totp/disable` and `POST /users/me/totp/backup-codes` */
 export const totpReauthRequestSchema = z.object({ reauth: reauthProofSchema }).strict();
 export const totpBackupCodesResponseSchema = z.object({
-    backupCodes: z.array(z.string().regex(/^[a-z2-9]{5}-[a-z2-9]{5}$/)).length(TOTP_BACKUP_CODE_COUNT),
+    backupCodes: z
+        .array(z.string().regex(/^[a-z2-9]{5}-[a-z2-9]{5}$/))
+        .length(TOTP_BACKUP_CODE_COUNT),
 });
 /**
  * Stable error codes (`error.code` in the API error body). Clients map these

package/dist/esm/transparency.js

@@ -20,7 +20,9 @@ import { z } from 'zod';
  * verification failure at a distance.
  */
 /** A SHA-256 digest in the exact form the protocol emits: 64 lowercase hex chars. */
-const hexDigestSchema = z.string().regex(/^[0-9a-f]{64}$/, 'Expected a 64-char lowercase hex digest');
+const hexDigestSchema = z
+    .string()
+    .regex(/^[0-9a-f]{64}$/, 'Expected a 64-char lowercase hex digest');
 /**
  * One signer's endorsement of a checkpoint's signed fields.
  *

package/dist/esm/updates.js

@@ -11,7 +11,7 @@
  * CLI, the console hook) validates its INPUT against the same definitions, so
  * producer and consumers cannot drift.
  *
- * Domain model (mirrors the Mongoose models in `@oxy.so/api`):
+ * Domain model (mirrors the update tables in `@oxy.so/api`):
  *  - A `channel` (e.g. `production`, `preview`, `pr-123`) is a named release
  *    track for one application.
  *  - An `update` is one published bundle for a single `(channel, runtimeVersion,
@@ -153,9 +153,7 @@ export const createUpdateRequestSchema = z.object({
      * `expoClient` (the public expo config) so `Constants.expoConfig` resolves
      * after an OTA update; MAY carry other third-party config.
      */
-    extra: z
-        .object({ expoClient: z.record(z.string(), z.unknown()) })
-        .catchall(z.unknown()),
+    extra: z.object({ expoClient: z.record(z.string(), z.unknown()) }).catchall(z.unknown()),
     /** String→string metadata dict; filtered client-side via manifest filters. */
     metadata: z.record(z.string(), z.string()).optional(),
     /** Initial rollout percentage (default 100 — full rollout). */

package/dist/esm/userResponse.js

@@ -1,5 +1,18 @@
 /** Canonical profile/theme preset identities accepted by Oxy writes. */
-export const USER_PROFILE_COLOR_PRESETS = ['teal', 'blue', 'green', 'amber', 'red', 'purple', 'pink', 'sky', 'orange', 'mint', 'mono', 'oxy'];
+export const USER_PROFILE_COLOR_PRESETS = [
+    'teal',
+    'blue',
+    'green',
+    'amber',
+    'red',
+    'purple',
+    'pink',
+    'sky',
+    'orange',
+    'mint',
+    'mono',
+    'oxy',
+];
 /**
  * Canonical API user-response contracts.
  *
@@ -22,10 +35,10 @@ export const USER_PROFILE_COLOR_PRESETS = ['teal', 'blue', 'green', 'amber', 're
  *    Emits `id` (NOT `_id`), forwards `username` verbatim (may be absent), and
  *    emits `name` as the structured `{ first, last, full, displayName }`
  *    subdocument.
- *  - `packages/api/src/models/User.ts` — `NameSchema` (`first`/`last` default
- *    `''`; `full` and `displayName` are Mongoose VIRTUALS. Formatted API
- *    responses compose both fields, while raw-document responses may omit the
- *    virtuals if the query did not materialise them.
+ *  - `packages/api/src/db/schema/users.ts` — the stored name (`first`/`last`);
+ *    `full` and `displayName` have no column of their own. Formatted API
+ *    responses compose both fields, while raw-document responses may omit
+ *    them.
  *
  * Platform-agnostic — zod only, no react/react-native/expo. ESM-safe (no
  * `require()`).
@@ -122,7 +135,7 @@ export const dateOfBirthSchema = z
  */
 export const userResponseSchema = z
     .object({
-    /** MongoDB ObjectId as a string. Present on `formatUserResponse` output. */
+    /** The user id as a string. Present on `formatUserResponse` output. */
     id: z.string().optional(),
     /** Raw-document id (e.g. `GET /users/me`). Present when `id` is not. */
     _id: z.string().optional(),
@@ -222,7 +235,14 @@ export const userResponseSchema = z
      * `GET /session/user/:sessionId`) and absent until the user sets it.
      */
     themePreference: themePreferenceSchema.optional(),
-    personalization: z.object({ mentionMono: z.object({ allowed: z.boolean(), expiresAt: z.string().datetime().nullable() }).strict() }).strict().optional(),
+    personalization: z
+        .object({
+        mentionMono: z
+            .object({ allowed: z.boolean(), expiresAt: z.string().datetime().nullable() })
+            .strict(),
+    })
+        .strict()
+        .optional(),
 })
     .passthrough();
 export const userProfileUpdateSchema = z

package/dist/esm/username.js

@@ -210,7 +210,9 @@ export const usernameSchema = z
     .regex(USERNAME_PATTERN, USERNAME_INVALID_MESSAGE)
     .refine((username) => !/^[0-9]+$/.test(username), NUMERIC_USERNAME_MESSAGE)
     .refine((username) => !RESERVED_USERNAMES.has(username.toLowerCase()), RESERVED_USERNAME_MESSAGE)
-    .refine((username) => !username.split(/[-_]/).some((segment) => RESERVED_USERNAME_SEGMENTS.has(segment.toLowerCase())), RESERVED_USERNAME_MESSAGE);
+    .refine((username) => !username
+    .split(/[-_]/)
+    .some((segment) => RESERVED_USERNAME_SEGMENTS.has(segment.toLowerCase())), RESERVED_USERNAME_MESSAGE);
 /**
  * Whether a candidate handle is storable — the boolean form, for input surfaces
  * that show a message as somebody types rather than throwing.