@oxy.so/contracts 4.15.0 → 4.17.0

package/dist/types/username.d.ts

@@ -100,56 +100,7 @@
  */
 import { z } from 'zod';
 import type { AccountKind } from './accountGraph';
-/** Shortest storable handle. `oxy` sets the floor. */
-export declare const USERNAME_MIN_LENGTH = 3;
-/** Longest storable handle, and the `maxLength` an input field should carry. */
-export declare const USERNAME_MAX_LENGTH = 30;
-/** The 400 / inline-validation copy for every path that rejects a handle. */
-export declare const USERNAME_INVALID_MESSAGE: string;
-/**
- * Exact-match handles nobody may newly claim, regardless of account kind.
- *
- * This is NOT a namespace tightening like the bot suffix — it is a list of
- * names withheld from `users_lower_username_key` before anybody asks for
- * them. Compared against the same normalization the unique index applies
- * (`lower(btrim(username))`), so `Admin`, ` ADMIN ` and `admin` are the one
- * name this list means.
- *
- * `oxy`, `mention`, `homiio`, `clarity`, `faircoin`, `astro` and `mercaria`
- * are deliberately NOT here: each already has an `organization`/`project`
- * row, so the unique index already refuses a second one, and `oxy` is the
- * name `USERNAME_MIN_LENGTH` is pinned against in
- * `__tests__/username.test.ts` — listing it would make
- * `usernameSchema.safeParse('oxy')` fail and falsify that comment. A brand
- * with no account of its own yet (measured 2026-09-18: Alia, Allo, TNP,
- * Kaana, Bloom) has no row to protect it, so it is listed until one exists.
- */
-export declare const RESERVED_USERNAMES: ReadonlySet<string>;
-/** The 400 / inline-validation copy for a handle on {@link RESERVED_USERNAMES}. */
-export declare const RESERVED_USERNAME_MESSAGE = "This username is reserved and cannot be registered";
-/** The 400 / inline-validation copy for a handle that is only digits. */
-export declare const NUMERIC_USERNAME_MESSAGE = "Username cannot be only numbers";
-/**
- * Alphanumeric runs joined by single separators, as a SOURCE string.
- *
- * A string rather than a literal because the OpenAPI docblocks that publish this
- * rule (`POST /auth/register`, `PUT /users/:userId`) must quote it verbatim, and
- * `usernamePolicySingleSource.test.ts` compares them against THIS constant. A
- * published `pattern:` that drifts from the enforced rule is a lie told to every
- * client that generates from the spec, and it is exactly the kind of copy nobody
- * notices going stale.
- *
- * Deliberately NOT re-exported from the package barrel: it exists for the
- * schema below and for that one gate. Anything validating a username uses
- * {@link usernameSchema}, so there is no second way to ask the question.
- *
- * Written as an unambiguous alternation rather than a lookahead: every character
- * belongs to exactly one branch, so matching is linear and there is no
- * backtracking to bound. It also carries no `\p{…}` property escape, which
- * mobile Hermes throws on at runtime — this module is reachable from every React
- * Native consumer.
- */
-export declare const USERNAME_PATTERN_SOURCE = "^[A-Za-z0-9]+(?:[-_][A-Za-z0-9]+)*$";
+export { USERNAME_MIN_LENGTH, USERNAME_MAX_LENGTH, USERNAME_INVALID_MESSAGE, RESERVED_USERNAMES, RESERVED_USERNAME_MESSAGE, NUMERIC_USERNAME_MESSAGE, USERNAME_PATTERN_SOURCE, stripDisallowedUsernameCharacters, BOT_USERNAME_SUFFIX, BOT_USERNAME_INVALID_MESSAGE, applyBotUsernameSuffix, } from './client/username';
 /**
  * The one username policy, as a schema.
  *
@@ -168,34 +119,6 @@ export declare const usernameSchema: z.ZodEffects<z.ZodEffects<z.ZodEffects<z.Zo
  * server's 400 cannot disagree.
  */
 export declare function isValidUsername(candidate: string): boolean;
-/**
- * Drop the characters the policy forbids, for an input field that filters
- * keystrokes.
- *
- * This is a TYPING aid and nothing else — the result still has to pass
- * {@link usernameSchema}, which is what decides. It does not lower-case (case is
- * preserved, see the header) and it cannot repair a name: a value that is too
- * short, edge-separated or doubly-separated comes back unchanged and fails
- * validation with a message, which is the outcome the coercing rules this
- * replaces used to hide.
- */
-export declare function stripDisallowedUsernameCharacters(input: string): string;
-/**
- * The label a bot's handle ends in — the ONE exception the policy carries.
- *
- * Lower-case here because it is what a generator appends; the comparison that
- * enforces it folds case, so `MyBot` satisfies it just as `mybot` does.
- *
- * Deliberately NOT re-exported from the package barrel, for the same reason
- * {@link USERNAME_PATTERN_SOURCE} is not: it exists for the schema and the
- * generator aid below. A consumer that wants to SAY the rule uses
- * {@link BOT_USERNAME_INVALID_MESSAGE}, which already quotes it, and one that
- * wants to APPLY it uses {@link applyBotUsernameSuffix} — so there is no second
- * way to spell the check.
- */
-export declare const BOT_USERNAME_SUFFIX = "bot";
-/** The 400 / inline-validation copy for a bot handle that carries no label. */
-export declare const BOT_USERNAME_INVALID_MESSAGE = "A bot account's username must end in \"bot\"";
 /**
  * The username policy for an account of kind `bot`: everything above, plus a
  * handle that ends in {@link BOT_USERNAME_SUFFIX}.
@@ -268,21 +191,3 @@ export declare const botUsernameSchema: z.ZodEffects<z.ZodEffects<z.ZodEffects<z
  * can act on.
  */
 export declare function usernameSchemaForAccountKind(kind: AccountKind | null | undefined): z.ZodType<string, z.ZodTypeDef, string>;
-/**
- * Label a proposed bot handle, so a generator PROPOSES something the server will
- * accept.
- *
- * Alia builds an agent's handle from its display name; without this it would
- * propose `garden-helper` for a bot and be 400ed on submit, which is the same
- * "suggest, then refuse" defect the minimum length already caused once.
- *
- * It appends and never inserts: a separator is the caller's choice, so
- * `garden-helper` becomes `garden-helperbot` while a caller who typed
- * `garden-helper-` gets `garden-helper-bot`. It truncates to leave room rather
- * than overflowing {@link USERNAME_MAX_LENGTH}.
- *
- * Like {@link stripDisallowedUsernameCharacters} it is an aid, not a decision: it
- * cannot repair a handle the base policy refuses, and the result still has to
- * pass {@link botUsernameSchema}.
- */
-export declare function applyBotUsernameSuffix(candidate: string): string;

package/package.json

@@ -1,10 +1,17 @@
 {
   "name": "@oxy.so/contracts",
-  "version": "4.15.0",
+  "version": "4.17.0",
   "description": "OxyHQ API contracts — single source of truth for request/response Zod schemas and inferred types, shared by the backend and the client SDKs",
   "main": "dist/cjs/index.js",
   "module": "dist/esm/index.js",
   "types": "dist/types/index.d.ts",
+  "typesVersions": {
+    "*": {
+      "client": [
+        "dist/types/client/index.d.ts"
+      ]
+    }
+  },
   "source": "src/index.ts",
   "sideEffects": false,
   "publishConfig": {
@@ -23,6 +30,18 @@
       },
       "default": "./dist/esm/index.js"
     },
+    "./client": {
+      "react-native": "./dist/esm/client/index.js",
+      "import": {
+        "types": "./dist/types/client/index.d.ts",
+        "default": "./dist/esm/client/index.js"
+      },
+      "require": {
+        "types": "./dist/types/client/index.d.ts",
+        "default": "./dist/cjs/client/index.js"
+      },
+      "default": "./dist/esm/client/index.js"
+    },
     "./package.json": "./package.json"
   },
   "files": [