@stapel/workspaces-react 0.12.0 → 0.14.0

package/src/api/generated/schema.ts

@@ -318,9 +318,14 @@ export interface paths {
          * @description ``PATCH <ws>/members/<user_id>/name`` — correct a member's display name.
          *
          *     Writes the CANONICAL name: stapel-profiles' ``Profile.display_name``,
-         *     reached through this module's existing in-process profiles seam
-         *     (``services.set_profile_display_name``), which also publishes
-         *     ``profile.changed`` so every consumer of that name follows.
+         *     through the named write that module publishes
+         *     (``profiles.set_display_name``, called by
+         *     ``services.set_profile_display_name``), which validates against its own
+         *     canon and publishes ``profile.changed`` so every consumer of that name
+         *     follows. Topology-independent: the same call runs in-process in a
+         *     monolith and over the configured route where profiles is its own
+         *     container. Until 0.21.0 it was dotted-path symbol resolution instead,
+         *     and this endpoint simply did not work in a split deployment.
          *
          *     NOT ``WorkspaceMember.display_name_hint``: the hint is a pre-profile
          *     placeholder, copied once at creation and dark from the moment a real
@@ -328,11 +333,11 @@ export interface paths {
          *     produce a correction the roster shows and nothing else in the product
          *     ever does — including, eventually, the roster.
          *
-         *     Where stapel-profiles does not run in this process there is nothing to
-         *     write and no remote operation to call for it (that module publishes no
-         *     write-somebody-else's-name endpoint and no comm Function), so the answer
-         *     is an honest ``error.503.profiles_unavailable`` — never a 200 over a
-         *     write that did not happen.
+         *     Where the write cannot be performed the answer is a 503 that names its
+         *     own cause — ``error.503.profiles_not_configured`` when this deployment
+         *     has neither a provider nor a route (an operator's job, and it will not
+         *     heal on its own), ``error.503.profiles_unavailable`` when the call was
+         *     made and failed — never a 200 over a write that did not happen.
          *
          *     Only an owner may rename an owner — the same hardcoded owner protection
          *     that role changes, removals and password resets carry. Renaming is not

package/src/default/MembersManager.tsx

@@ -15,9 +15,9 @@
  */
 import { useState } from "react";
 import type { ReactElement } from "react";
-import { Button, Card, Input, Modal, Popconfirm, Select, Table, Typography } from "antd";
+import { Button, Card, Empty, Input, Modal, Popconfirm, Select, Table, Typography } from "antd";
 import type { TableProps } from "antd";
-import { useErrorDisplay, useT } from "@stapel/core";
+import { loadedRowsOrEmpty, matchList, useErrorDisplay, useT } from "@stapel/core";
 import { Members } from "../headless/Members.js";
 import { RoleSelect } from "../headless/RoleSelect.js";
 import type { RoleSelectBag } from "../headless/RoleSelect.js";
@@ -54,9 +54,15 @@ export function MembersManager(props: MembersManagerProps): ReactElement {
     <RoleSelect>
       {(rolesBag: RoleSelectBag) => (
         <Members workspaceId={props.workspaceId}>
-          {({ members, isLoading, isError, error, invite, isInviting, updateRole, remove }) => {
+          {({ state, writeError, invite, isInviting, updateRole, remove, refetch }) => {
             const { labelFor } = rolesBag;
-            const roleOptions = rolesBag.roles.map((r) => ({
+            // The registry read is a SEPARATE load from the roster's, and it
+            // gets its own sentence below rather than silently producing an
+            // empty picker — a role menu with nothing in it and a role menu
+            // that could not be fetched look identical to a person.
+            const rolesFailed = rolesBag.state.status === "failed";
+            const rolesLoading = rolesBag.state.status === "loading";
+            const roleOptions = loadedRowsOrEmpty(rolesBag.state).map((r) => ({
               value: r.role,
               label: labelFor(r.role),
             }));
@@ -95,7 +101,7 @@ export function MembersManager(props: MembersManagerProps): ReactElement {
                     <Select<string>
                       value={member.role}
                       style={{ width: 160 }}
-                      loading={rolesBag.isLoading}
+                      loading={rolesLoading}
                       onChange={(next) => updateRole({ userId: member.user_id, role: next })}
                       // A member's CURRENT role may be missing from the
                       // registry options (a deployment removed an overlay
@@ -148,17 +154,64 @@ export function MembersManager(props: MembersManagerProps): ReactElement {
                   )}
                 </div>
 
-                {isError && <ErrorAlert error={errorDisplay(error)} style={{ marginTop: 12 }} />}
+                {/* A write that failed — the roster read has its own arm below. */}
+                {writeError !== null && (
+                  <ErrorAlert error={errorDisplay(writeError)} style={{ marginTop: 12 }} />
+                )}
+                {rolesFailed && (
+                  <ErrorAlert
+                    testId="members-roles-error"
+                    error={{ message: t(WORKSPACES_I18N_KEYS.rolesLoadFailed), detail: undefined }}
+                    style={{ marginTop: 12 }}
+                  />
+                )}
 
-                <Table<Member>
-                  style={{ marginTop: 16 }}
-                  size="small"
-                  loading={isLoading}
-                  rowKey={(member) => member.id}
-                  dataSource={members as Member[]}
-                  columns={columns}
-                  pagination={false}
-                />
+                {matchList(state, {
+                  loading: () => (
+                    <Table<Member>
+                      style={{ marginTop: 16 }}
+                      size="small"
+                      loading
+                      rowKey={(member) => member.id}
+                      dataSource={[]}
+                      columns={columns}
+                      pagination={false}
+                    />
+                  ),
+                  // An antd Table with no rows renders "No data". On a failed
+                  // read that is the empty-state lie with a built-in
+                  // illustration, so the table does not get rendered at all.
+                  failed: (error) => (
+                    <div style={{ marginTop: 16 }} data-testid="members-list-error">
+                      <ErrorAlert error={errorDisplay(error)} />
+                      <Button
+                        style={{ marginTop: 12 }}
+                        onClick={refetch}
+                        data-analytics="none"
+                        data-analytics-reason="local-ui-refetch-after-a-stated-read-failure"
+                      >
+                        {t(WORKSPACES_I18N_KEYS.retry)}
+                      </Button>
+                    </div>
+                  ),
+                  empty: () => (
+                    <Empty
+                      style={{ marginTop: 16 }}
+                      data-testid="members-list-empty"
+                      description={t(WORKSPACES_I18N_KEYS.membersEmpty)}
+                    />
+                  ),
+                  ready: (members) => (
+                    <Table<Member>
+                      style={{ marginTop: 16 }}
+                      size="small"
+                      rowKey={(member) => member.id}
+                      dataSource={[...members]}
+                      columns={columns}
+                      pagination={false}
+                    />
+                  ),
+                })}
 
                 <Modal
                   title={t(WORKSPACES_I18N_KEYS.membersInviteDialogTitle)}
@@ -182,7 +235,7 @@ export function MembersManager(props: MembersManagerProps): ReactElement {
                         value={inviteRole}
                         onChange={setInviteRole}
                         style={{ width: "100%" }}
-                        loading={rolesBag.isLoading}
+                        loading={rolesLoading}
                         options={inviteRoleOptions}
                       />
                     </div>

package/src/default/WorkspaceSettings.tsx

@@ -9,7 +9,14 @@
 import { useEffect, useState } from "react";
 import type { ReactElement } from "react";
 import { Badge, Button, Card, Input, Popconfirm, Spin, Typography } from "antd";
-import { useErrorDisplay, useT } from "@stapel/core";
+import {
+  actionAvailable,
+  actionBlocked,
+  firstBlock,
+  useActionGate,
+  useErrorDisplay,
+  useT,
+} from "@stapel/core";
 import { useWorkspace } from "../model/queries.js";
 import { useUpdateWorkspace, useDeleteWorkspace } from "../model/mutations.js";
 import { WORKSPACES_I18N_KEYS } from "../i18n/keys.js";
@@ -35,6 +42,17 @@ export function WorkspaceSettings(props: WorkspaceSettingsProps): ReactElement {
   const workspace = query.data;
   const [name, setName] = useState("");
 
+  // Two unrelated situations used to share one `disabled={!isOwner ||
+  // !name.trim()}` bit, and a person facing either of them saw the same dead
+  // button. `firstBlock` keeps them two, in the order you would explain them.
+  const isOwner = workspace?.my_role === "owner";
+  const saveGate = useActionGate(
+    firstBlock(
+      isOwner ? actionAvailable() : actionBlocked(WORKSPACES_I18N_KEYS.blockedNotOwner),
+      name.trim() ? actionAvailable() : actionBlocked(WORKSPACES_I18N_KEYS.blockedNameRequired)
+    )
+  );
+
   useEffect(() => {
     if (workspace) setName(workspace.name);
   }, [workspace]);
@@ -66,8 +84,6 @@ export function WorkspaceSettings(props: WorkspaceSettingsProps): ReactElement {
     );
   }
 
-  const isOwner = workspace.my_role === "owner";
-
   return (
     <div data-testid="workspace-settings" style={{ display: "grid", gap: 16 }}>
       <Card>
@@ -79,7 +95,18 @@ export function WorkspaceSettings(props: WorkspaceSettingsProps): ReactElement {
         <div style={{ display: "grid", gap: 12, maxWidth: 480, marginTop: 16 }}>
           <div>
             <Typography.Text>{t(WORKSPACES_I18N_KEYS.fieldName)}</Typography.Text>
-            <Input value={name} onChange={(e) => setName(e.target.value)} disabled={!isOwner} />
+            <Input
+              value={name}
+              onChange={(e) => setName(e.target.value)}
+              disabled={!isOwner}
+            />
+            {!isOwner && (
+              <div>
+                <Typography.Text type="secondary" data-testid="workspace-name-blocked">
+                  {t(WORKSPACES_I18N_KEYS.blockedNotOwner)}
+                </Typography.Text>
+              </div>
+            )}
           </div>
           <div>
             <Typography.Text>{t(WORKSPACES_I18N_KEYS.fieldSlug)}</Typography.Text>
@@ -101,13 +128,22 @@ export function WorkspaceSettings(props: WorkspaceSettingsProps): ReactElement {
           type="primary"
           style={{ marginTop: 16 }}
           loading={updateMutation.isPending}
-          disabled={!isOwner || !name.trim()}
+          disabled={saveGate.disabled}
           onClick={handleSave}
           data-analytics="none"
           data-analytics-reason="business action — host app wraps with its own tracked(); pairs carry no @stapel/analytics runtime dependency by architecture"
         >
           {updateMutation.isPending ? t(WORKSPACES_I18N_KEYS.saving) : t(WORKSPACES_I18N_KEYS.save)}
         </Button>
+        {/* Beside the control, as TEXT: a disabled button receives no pointer
+            events, so a tooltip on it is a reason nobody can read. */}
+        {saveGate.reason !== undefined && (
+          <div style={{ marginTop: 8 }}>
+            <Typography.Text type="secondary" data-testid="workspace-save-blocked">
+              {saveGate.reason}
+            </Typography.Text>
+          </div>
+        )}
       </Card>
 
       {isOwner && (

package/src/headless/Can.tsx

@@ -8,6 +8,14 @@ export interface CanBag {
   /** The underlying read is still in flight (verdict is `false` meanwhile —
    * deny-by-default; render a skeleton off this if flicker matters). */
   readonly isLoading: boolean;
+  /**
+   * The read FAILED, so `allowed: false` means "we could not find out",
+   * not "you may not". Deny-by-default still holds — a capability check that
+   * opened up on an outage would be a security hole — but a skin with
+   * somewhere to put a sentence should say which of the two it is rather than
+   * silently withholding the control.
+   */
+  readonly isUnknown: boolean;
 }
 
 /**
@@ -43,7 +51,11 @@ export function Can(props: {
   const caps = useCapabilities(props.workspaceId);
   const allowed = caps.can(props.capability);
   if (typeof props.children === "function") {
-    return props.children({ allowed, isLoading: caps.isLoading });
+    return props.children({
+      allowed,
+      isLoading: caps.state.status === "loading",
+      isUnknown: caps.state.status === "failed",
+    });
   }
   return allowed ? props.children : (props.fallback ?? null);
 }

package/src/headless/Members.tsx

@@ -1,5 +1,6 @@
 import type { ReactNode } from "react";
-import type { StapelApiError } from "@stapel/core";
+import { loadStateFromQuery, mapLoad } from "@stapel/core";
+import type { LoadState, StapelApiError } from "@stapel/core";
 import type { Member, MemberInvite } from "../api/types.js";
 import { useMembers } from "../model/queries.js";
 import {
@@ -12,18 +13,19 @@ import type { MemberRoleChange } from "../model/mutations.js";
 /** Render-prop bag for {@link Members}. */
 export interface MembersBag {
   /**
-   * The workspace's members once loaded (empty before load). This is one page
-   * (default 100) — the roster's own {@link Member.email}/`search` narrows
-   * further; a full pager is out of scope for this renderless view (bring
-   * your own via `useMembers`' `params` for anchor pagination).
+   * The roster read, as a state a skin cannot flatten — render it with core's
+   * `matchList`. This is one page (default 100); a full pager is out of scope
+   * for this renderless view (bring your own via `useMembers`' `params` for
+   * anchor pagination).
+   *
+   * Separate from {@link writeError} on purpose: "the roster could not be
+   * loaded" and "your invite was rejected" are different sentences, and the
+   * old merged `isError` could only produce one of them.
    */
-  readonly members: readonly Member[];
-  /** The initial member-list load is in flight. */
-  readonly isLoading: boolean;
-  /** The read, an invite, a role change, or a removal failed. */
-  readonly isError: boolean;
-  /** The error, when `isError` (a localizable `StapelApiError`), else null. */
-  readonly error: StapelApiError | null;
+  readonly state: LoadState<readonly Member[]>;
+  /** An invite, a role change, or a removal failed. Never the read — that is
+   * {@link state}. */
+  readonly writeError: StapelApiError | null;
   /** Invite one or more emails at a role. */
   invite(body: MemberInvite): void;
   /** An invite call is in flight. */
@@ -49,7 +51,7 @@ export interface MembersBag {
  *
  * ```tsx
  * <Members workspaceId={id}>
- *   {({ members, invite, updateRole, remove }) => ( ... )}
+ *   {({ state, invite, updateRole, remove }) => ( ... )}
  * </Members>
  * ```
  */
@@ -62,19 +64,9 @@ export function Members(props: {
   const roleMutation = useUpdateMemberRole(props.workspaceId);
   const removeMutation = useRemoveMember(props.workspaceId);
   return props.children({
-    members: query.data?.items ?? [],
-    isLoading: query.isLoading,
-    isError:
-      query.isError ||
-      inviteMutation.isError ||
-      roleMutation.isError ||
-      removeMutation.isError,
-    error:
-      query.error ??
-      inviteMutation.error ??
-      roleMutation.error ??
-      removeMutation.error ??
-      null,
+    state: mapLoad(loadStateFromQuery(query), (page) => page.items),
+    writeError:
+      inviteMutation.error ?? roleMutation.error ?? removeMutation.error ?? null,
     invite: (body) => {
       inviteMutation.mutate(body);
     },

package/src/headless/RoleSelect.tsx

@@ -1,14 +1,16 @@
 import type { ReactNode } from "react";
-import { useI18n } from "@stapel/core";
-import type { StapelApiError } from "@stapel/core";
+import { loadStateFromQuery, useI18n } from "@stapel/core";
+import type { LoadState } from "@stapel/core";
 import type { RoleInfo } from "../api/types.js";
 import { useRoles } from "../model/queries.js";
 
 /** Render-prop bag for {@link RoleSelect}. */
 export interface RoleSelectBag {
   /** The effective registry (GET /roles): builtin four + the deployment's
-   * overlay, rank-descending. Empty while loading. */
-  readonly roles: readonly RoleInfo[];
+   * overlay, rank-descending. A state rather than an array: a role picker
+   * built from `[]` because the registry read FAILED offers no roles at all
+   * and looks exactly like a deployment that defined none. */
+  readonly state: LoadState<readonly RoleInfo[]>;
   /**
    * Display label for a role key: the i18n key `workspaces.role.<key>` when
    * the current locale's merged bundle carries it (the pair ships the builtin
@@ -18,9 +20,6 @@ export interface RoleSelectBag {
    * never render as a dotted i18n key.
    */
   labelFor(role: string): string;
-  readonly isLoading: boolean;
-  readonly isError: boolean;
-  readonly error: StapelApiError | null;
 }
 
 /**
@@ -30,9 +29,16 @@ export interface RoleSelectBag {
  *
  * ```tsx
  * <RoleSelect>
- *   {({ roles, labelFor }) => (
- *     <Select options={roles.map((r) => ({ value: r.role, label: labelFor(r.role) }))} />
- *   )}
+ *   {({ state, labelFor }) =>
+ *     matchList(state, {
+ *       loading: () => <Select loading options={[]} />,
+ *       failed: (error) => <RoleLoadFailed error={error} />,
+ *       empty: () => <Select disabled options={[]} />,
+ *       ready: (roles) => (
+ *         <Select options={roles.map((r) => ({ value: r.role, label: labelFor(r.role) }))} />
+ *       ),
+ *     })
+ *   }
  * </RoleSelect>
  * ```
  *
@@ -49,10 +55,7 @@ export function RoleSelect(props: {
   // must show its raw name, not `workspaces.role.secretary`).
   const bundle = i18n.getBundle();
   return props.children({
-    roles: query.data ?? [],
+    state: loadStateFromQuery(query),
     labelFor: (role) => bundle[`workspaces.role.${role}`] ?? role,
-    isLoading: query.isLoading,
-    isError: query.isError,
-    error: query.error ?? null,
   });
 }

package/src/headless/WorkspaceList.tsx

@@ -1,25 +1,34 @@
 import type { ReactNode } from "react";
-import type { StapelApiError } from "@stapel/core";
+import { loadStateFromQuery, mapLoad } from "@stapel/core";
+import type { LoadState, StapelApiError } from "@stapel/core";
 import type { Workspace, WorkspaceCreate } from "../api/types.js";
 import { useWorkspaces } from "../model/queries.js";
 import { useCreateWorkspace } from "../model/mutations.js";
 
 /** Render-prop bag for {@link WorkspaceList}. */
 export interface WorkspaceListBag {
-  /** The caller's workspaces once loaded (empty before load). */
-  readonly workspaces: readonly Workspace[];
-  /** The initial list load is in flight (no data yet). */
-  readonly isLoading: boolean;
-  /** Either the read or the create failed. */
-  readonly isError: boolean;
-  /** The error, when `isError` (a localizable `StapelApiError`), else null. */
-  readonly error: StapelApiError | null;
+  /**
+   * The read, as a state a skin cannot flatten: `loading` / `ready` with the
+   * rows / `failed` with the error. Render it with core's `matchList`, whose
+   * four arms are all required, so "you have no workspaces" can only be said
+   * about a load that actually succeeded.
+   *
+   * This replaced a `workspaces: readonly Workspace[]` field that was `[]` in
+   * all three cases. On 2026-08-09 the list endpoint answered 404 for hours
+   * and every screen built on that field said the person had no workspaces.
+   * The bag carried `isError` beside it the whole time; nothing forced a skin
+   * to look, so nothing did.
+   */
+  readonly state: LoadState<readonly Workspace[]>;
   /** Create a workspace (owner-seeded). */
   create(body: WorkspaceCreate): void;
   /** A create call is in flight. */
   readonly isCreating: boolean;
   /** The workspace created by the last `create`, else null. */
   readonly created: Workspace | null;
+  /** The CREATE's failure — a write, and therefore a different question from
+   * {@link state}, which is about the read. */
+  readonly createError: StapelApiError | null;
   /** Refetch the list from the server. */
   refetch(): void;
 }
@@ -32,7 +41,14 @@ export interface WorkspaceListBag {
  *
  * ```tsx
  * <WorkspaceList>
- *   {({ workspaces, create }) => ( ... )}
+ *   {({ state, create }) =>
+ *     matchList(state, {
+ *       loading: () => <Spinner />,
+ *       failed: (error) => <ErrorPanel error={error} onRetry={refetch} />,
+ *       empty: () => <FirstWorkspacePrompt onCreate={create} />,
+ *       ready: (workspaces) => <List items={workspaces} />,
+ *     })
+ *   }
  * </WorkspaceList>
  * ```
  */
@@ -42,15 +58,16 @@ export function WorkspaceList(props: {
   const query = useWorkspaces();
   const mutation = useCreateWorkspace();
   return props.children({
-    workspaces: query.data?.workspaces ?? [],
-    isLoading: query.isLoading,
-    isError: query.isError || mutation.isError,
-    error: query.error ?? mutation.error ?? null,
+    // `workspaces` is optional in the wire schema, so a SUCCESSFUL response
+    // may legitimately carry none. That is an empty list, not a failed load —
+    // the distinction this whole field exists for is already made above it.
+    state: mapLoad(loadStateFromQuery(query), (list) => list.workspaces ?? []),
     create: (body) => {
       mutation.mutate(body);
     },
     isCreating: mutation.isPending,
     created: mutation.data ?? null,
+    createError: mutation.error ?? null,
     refetch: () => {
       void query.refetch();
     },

package/src/i18n/es.ts

@@ -0,0 +1,47 @@
+import type { I18nDictionary, I18nEngine } from "@stapel/core";
+import { workspacesI18nBundleEn } from "./keys.js";
+import { workspacesErrorBundleEs } from "./generated/errors.es.gen.js";
+
+export { workspacesErrorBundleEs } from "./generated/errors.es.gen.js";
+
+/**
+ * Spanish bundle for workspaces-react — the pair's `es` locale, shipped as the
+ * `@stapel/workspaces-react/i18n/es` subpath (i18n-shipping.md §2) so the locale is
+ * opt-in: hosts that don't register it never carry these strings (the main
+ * entry does not import this module — gated by size-limit + the tree-shake
+ * purity test).
+ *
+ * COVERAGE IS DECLARED, NOT DISCOVERED. This bundle carries the GENERATED
+ * backend error texts (from stapel-workspaces's `translations/errors.es.json`
+ * catalog — `pnpm gen:errors`), complete over the error registry by
+ * construction: the generator fails on a gap and the Record type fails
+ * compilation on drift. The pair-owned UI keys (`WORKSPACES_I18N_KEYS`) are NOT
+ * translated to Spanish yet and deliberately fall back to their English text
+ * through the en floor that {@link registerWorkspacesI18nEs} registers underneath.
+ * So a Spanish-speaking user reads Spanish error messages and English UI copy —
+ * never a raw key. That state is asserted in `test/i18nEs.test.ts`; whoever
+ * adds hand-written Spanish UI copy flips those assertions deliberately.
+ *
+ * Adding that copy later is additive and host-invisible: this const and the
+ * `./i18n/es` subpath keep their names and shapes when it lands.
+ */
+export const workspacesI18nBundleEs: I18nDictionary = {
+  // Backend error codes — generated es texts (coverage by construction).
+  ...workspacesErrorBundleEs,
+
+  // No hand-written Spanish UI copy yet — see COVERAGE above. Pair-owned keys
+  // resolve through the en floor until it exists.
+};
+
+/**
+ * Register the pair's `es` locale into a core i18n engine (call once at
+ * startup, after {@link registerWorkspacesI18n}). Layers per the merge-priority
+ * convention (i18n-shipping.md §3): the en floor is registered UNDER the es
+ * texts inside the `es` locale, so any key the es bundle does not carry —
+ * today, every pair-owned UI key — degrades to its English text rather than to
+ * a raw key. A host bundle registered after this call overrides both.
+ */
+export function registerWorkspacesI18nEs(engine: I18nEngine): void {
+  engine.registerBundle("es", workspacesI18nBundleEn);
+  engine.registerBundle("es", workspacesI18nBundleEs);
+}

package/src/i18n/generated/errors.es.gen.ts

@@ -0,0 +1,82 @@
+// AUTO-GENERATED by scripts/gen-errors.mjs — do not edit by hand.
+// Source: stapel-auth canonical errors.json (backend codegen artifact).
+// Regenerate: pnpm gen:errors   ·   Drift gate: pnpm gen:errors:check
+// Locale source: backend translations/errors.es.json (locale catalog
+// beside the canonical errors.json — i18n-shipping.md §1).
+import type { WorkspacesErrorCode } from "./errors.gen.js";
+
+/**
+ * `es` texts for every backend error code — complete over the registry by
+ * construction (the generator fails on a gap; the Record type fails compilation
+ * on drift). Import from the pair's `./i18n/es` subpath, NOT the main
+ * entry, so the locale stays out of hosts that don't ship it.
+ */
+export const workspacesErrorBundleEs: Record<WorkspacesErrorCode, string> = {
+  "error.400.already_workspace_member": "El usuario ya es miembro de este espacio de trabajo",
+  "error.400.bad_request": "Solicitud incorrecta",
+  "error.400.captcha_invalid": "La verificación del captcha ha fallado. Inténtalo de nuevo.",
+  "error.400.captcha_required": "Se requiere el token del captcha.",
+  "error.400.display_name_emoji": "El nombre para mostrar no puede contener emojis",
+  "error.400.display_name_forbidden_chars": "El nombre para mostrar contiene caracteres no permitidos",
+  "error.400.display_name_invisible_chars": "El nombre para mostrar contiene caracteres invisibles",
+  "error.400.display_name_too_short": "El nombre para mostrar debe tener al menos 2 caracteres",
+  "error.400.expected_list": "Se esperaba una lista de elementos",
+  "error.400.field.blank": "{field} no puede estar vacío",
+  "error.400.field.does_not_exist": "{field} no existe",
+  "error.400.field.invalid": "{field} no es válido",
+  "error.400.field.invalid_choice": "{field} no es una opción válida",
+  "error.400.field.max_length": "{field} debe tener como máximo {max_length} caracteres",
+  "error.400.field.max_value": "{field} debe ser como máximo {max_value}",
+  "error.400.field.min_length": "{field} debe tener al menos {min_length} caracteres",
+  "error.400.field.min_value": "{field} debe ser como mínimo {min_value}",
+  "error.400.field.null": "{field} no puede ser nulo",
+  "error.400.field.required": "{field} es obligatorio",
+  "error.400.field.unique": "{field} debe ser único",
+  "error.400.invalid_ad_id": "ID de anuncio no válido",
+  "error.400.invalid_provision_username": "Nombre de usuario no válido para una cuenta aprovisionada",
+  "error.400.invalid_role": "Rol no válido",
+  "error.400.invitation_already_used": "La invitación ya se ha utilizado",
+  "error.400.invitation_declined": "La invitación ha sido rechazada",
+  "error.400.invitation_expired": "La invitación ha caducado",
+  "error.400.invitation_revoked": "La invitación ha sido revocada",
+  "error.400.validation_error": "Error de validación",
+  "error.400.verification_failed": "La verificación ha fallado",
+  "error.400.verification_invalid_factor": "Este factor de verificación no está disponible",
+  "error.400.workspace_slug_taken": "El slug del espacio de trabajo ya está en uso",
+  "error.401.unauthorized": "Se requiere autenticación",
+  "error.402.entitlement_required": "El plan del propietario del espacio de trabajo no incluye esta función",
+  "error.402.member_limit_reached": "Se ha alcanzado el límite de miembros del espacio de trabajo ({limit})",
+  "error.402.payment_required": "Se requiere pago",
+  "error.403.forbidden": "No tienes permiso para realizar esta acción",
+  "error.403.forbidden_workspace": "No tienes acceso a este espacio de trabajo",
+  "error.403.last_owner_cannot_be_removed": "El último propietario no se puede eliminar; primero transfiere la propiedad",
+  "error.403.membership_suspended": "Tu pertenencia a este espacio de trabajo está suspendida ({reason})",
+  "error.403.missing_capability": "Tu rol no incluye la capacidad {capability} en este espacio de trabajo",
+  "error.403.network_blocked": "No se permiten solicitudes desde esta red.",
+  "error.403.role_exceeds_inviter_rank": "No puedes conceder un rol superior al tuyo ({role})",
+  "error.403.verification_enrollment_required": "Es necesario registrar un factor de verificación.",
+  "error.403.verification_required": "Se requiere verificación adicional",
+  "error.404.ad_not_found": "Anuncio no encontrado",
+  "error.404.invitation_not_found": "Invitación no encontrada",
+  "error.404.member_not_found": "Miembro no encontrado en este espacio de trabajo",
+  "error.404.not_found": "Recurso solicitado no encontrado",
+  "error.404.verification_challenge_not_found": "Desafío de verificación no encontrado o caducado",
+  "error.404.workspace_not_found": "Espacio de trabajo no encontrado",
+  "error.405.method_not_allowed": "Método no permitido",
+  "error.406.not_acceptable": "No aceptable",
+  "error.408.request_timeout": "Tiempo de espera de la solicitud agotado",
+  "error.409.conflict": "El recurso ya existe",
+  "error.409.email_already_registered": "Ya existe una cuenta con este correo electrónico: inicia sesión en su lugar",
+  "error.410.gone": "El recurso se ha eliminado permanentemente",
+  "error.413.payload_too_large": "El cuerpo de la solicitud es demasiado grande",
+  "error.415.unsupported_media_type": "Tipo de contenido no compatible",
+  "error.422.unprocessable_entity": "Entidad no procesable",
+  "error.423.locked": "El recurso está bloqueado",
+  "error.423.verification_locked": "Demasiados intentos fallidos — verificación bloqueada",
+  "error.429.rate_limit": "Demasiados intentos. Inténtalo de nuevo en {retry_after_minutes} minutos.",
+  "error.429.too_many_requests": "Demasiadas solicitudes. Inténtalo de nuevo más tarde.",
+  "error.500.internal": "Algo salió mal",
+  "error.503.auth_unavailable": "El servicio de autenticación no está disponible; inténtalo de nuevo más tarde",
+  "error.503.profiles_not_configured": "Este despliegue no tiene configurado un servicio de perfiles, por lo que aquí no se puede escribir un nombre para mostrar",
+  "error.503.profiles_unavailable": "El servicio de perfiles no está disponible; inténtalo de nuevo más tarde",
+};

package/src/i18n/generated/errors.gen.ts

@@ -100,6 +100,7 @@ export const WORKSPACES_ERRORS = {
   "error.429.too_many_requests": { status: 429, params: [], remediation: "wait_and_retry", en: "Too many requests. Please try again later." },
   "error.500.internal": { status: 500, params: [], remediation: "contact_support", en: "Something went wrong" },
   "error.503.auth_unavailable": { status: 503, params: [], remediation: "wait_and_retry", en: "The authentication service is unavailable; try again later" },
+  "error.503.profiles_not_configured": { status: 503, params: [], remediation: "contact_support", en: "This deployment has no profiles service configured, so a display name cannot be written here" },
   "error.503.profiles_unavailable": { status: 503, params: [], remediation: "wait_and_retry", en: "The profiles service is unavailable; try again later" },
 } as const;
 
@@ -172,6 +173,7 @@ export const WORKSPACES_ERROR_CODES: readonly WorkspacesErrorCode[] = [
   "error.429.too_many_requests",
   "error.500.internal",
   "error.503.auth_unavailable",
+  "error.503.profiles_not_configured",
   "error.503.profiles_unavailable",
 ];
 
@@ -246,5 +248,6 @@ export const workspacesErrorBundleEn: Record<WorkspacesErrorCode, string> = {
   "error.429.too_many_requests": "Too many requests. Please try again later.",
   "error.500.internal": "Something went wrong",
   "error.503.auth_unavailable": "The authentication service is unavailable; try again later",
+  "error.503.profiles_not_configured": "This deployment has no profiles service configured, so a display name cannot be written here",
   "error.503.profiles_unavailable": "The profiles service is unavailable; try again later",
 };