@zitadel/components 1.0.0-alpha.20 → 1.0.0-alpha.21

package/dist/{index-BPgWdWx7.d.mts → index-Dx8rvpNs.d.mts}

@@ -334,7 +334,7 @@ declare global {
   }
 } //# sourceMappingURL=zl-checkbox.d.ts.map
 //#endregion
-//#region ../api/dist/index-BpCgp2NY.d.mts
+//#region ../api/dist/index-BK4Q468Q.d.mts
 //#region src/generated/model/beginUserPasskeyRegistration201Options.d.ts
 /**
  * Generated by orval v8.10.0 🍺
@@ -3296,6 +3296,42 @@ declare const CreateSession201SessionState: {
   readonly active: "active";
   readonly expired: "expired";
 }; //#endregion
+//#region src/generated/model/createSession201SessionUser.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+/**
+ * A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+property-named, so responses can mix users from different schemas.
+`identifier` and `display` are resolved independently from the user
+schema's `x-identifier` and `x-display` designations, live at read time.
+Clients render `display`, falling back to `identifier`, then `user_id`.
+
+ */
+type CreateSession201SessionUser = {
+  /** @pattern ^user_[a-zA-Z0-9_-]+$ */user_id: string;
+  /** The current value of the schema's designated identifier
+  (`x-identifier`). Absent when the schema designates no identifier or
+  the user carries no value for it.
+   */
+  identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order. Purely presentational, with no source attribution.
+  Absent when the schema designates no display properties or the user
+  carries no values for them.
+   */
+  display?: string;
+}; //#endregion
 //#region src/generated/model/createSession201SessionUserAgent.d.ts
 /**
  * Generated by orval v8.10.0 🍺
@@ -3339,23 +3375,13 @@ type CreateSession201Session = {
   factor has been verified through an `auth_attempt`.
    */
   user_id?: string | null;
-  /** Human-readable name of the authenticated user, resolved from the
-  conventional user-schema properties: `name` when defined, otherwise
-  the given and family name parts joined — `givenName`/`familyName`
-  (the shipped presets' spelling) or `given_name`/`family_name`. Only
-  present on reads that hydrate the user's identity
-  (`GET /sessions/me`) and only when the session has an authenticated
-  user whose schema carries those properties; clients fall back to
-  `email`, then `user_id`.
-   */
-  name?: string;
-  /** Email address of the authenticated user, resolved from the
-  conventional `email` user-schema property. Only present on reads
-  that hydrate the user's identity (`GET /sessions/me`) and only when
-  the session has an authenticated user whose schema carries that
-  property.
+  /** A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+  property-named, so responses can mix users from different schemas.
+  `identifier` and `display` are resolved independently from the user
+  schema's `x-identifier` and `x-display` designations, live at read time.
+  Clients render `display`, falling back to `identifier`, then `user_id`.
    */
-  email?: string;
+  user?: CreateSession201SessionUser;
   /** Verified authentication factors accumulated by this session.
   Each key is a factor type (e.g. `password`, `totp`, `passkey`).
   Each value is a factor event object with at least `verified_at` and
@@ -3706,6 +3732,24 @@ type CreateUser201 = {
    */
   attributes: CreateUser201Attributes;
   metadata: CreateUser201Metadata;
+  /** The current value of the user schema's designated identifier
+  (`x-identifier`), resolved live at read time. Absent when the schema
+  designates no identifier or the user carries no value for it.
+   */
+  readonly identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  readonly identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order, resolved live at read time. Purely presentational.
+  Absent when the schema designates no display properties or the user
+  carries no values for them. Clients render `display`, falling back
+  to `identifier`, then `id`.
+   */
+  readonly display?: string;
   /** The user's team memberships, present only when the request asked for them with
   `expand: ["teams"]` (ADR 059). Absent means it was not requested; `[]`
   means the user has none.
@@ -3946,6 +3990,42 @@ declare const ExchangeHandoff200SessionState: {
   readonly active: "active";
   readonly expired: "expired";
 }; //#endregion
+//#region src/generated/model/exchangeHandoff200SessionUser.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+/**
+ * A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+property-named, so responses can mix users from different schemas.
+`identifier` and `display` are resolved independently from the user
+schema's `x-identifier` and `x-display` designations, live at read time.
+Clients render `display`, falling back to `identifier`, then `user_id`.
+
+ */
+type ExchangeHandoff200SessionUser = {
+  /** @pattern ^user_[a-zA-Z0-9_-]+$ */user_id: string;
+  /** The current value of the schema's designated identifier
+  (`x-identifier`). Absent when the schema designates no identifier or
+  the user carries no value for it.
+   */
+  identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order. Purely presentational, with no source attribution.
+  Absent when the schema designates no display properties or the user
+  carries no values for them.
+   */
+  display?: string;
+}; //#endregion
 //#region src/generated/model/exchangeHandoff200SessionUserAgent.d.ts
 /**
  * Generated by orval v8.10.0 🍺
@@ -3989,23 +4069,13 @@ type ExchangeHandoff200Session = {
   factor has been verified through an `auth_attempt`.
    */
   user_id?: string | null;
-  /** Human-readable name of the authenticated user, resolved from the
-  conventional user-schema properties: `name` when defined, otherwise
-  the given and family name parts joined — `givenName`/`familyName`
-  (the shipped presets' spelling) or `given_name`/`family_name`. Only
-  present on reads that hydrate the user's identity
-  (`GET /sessions/me`) and only when the session has an authenticated
-  user whose schema carries those properties; clients fall back to
-  `email`, then `user_id`.
+  /** A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+  property-named, so responses can mix users from different schemas.
+  `identifier` and `display` are resolved independently from the user
+  schema's `x-identifier` and `x-display` designations, live at read time.
+  Clients render `display`, falling back to `identifier`, then `user_id`.
    */
-  name?: string;
-  /** Email address of the authenticated user, resolved from the
-  conventional `email` user-schema property. Only present on reads
-  that hydrate the user's identity (`GET /sessions/me`) and only when
-  the session has an authenticated user whose schema carries that
-  property.
-   */
-  email?: string;
+  user?: ExchangeHandoff200SessionUser;
   /** Verified authentication factors accumulated by this session.
   Each key is a factor type (e.g. `password`, `totp`, `passkey`).
   Each value is a factor event object with at least `verified_at` and
@@ -7189,6 +7259,42 @@ declare const GetMySession200State: {
   readonly active: "active";
   readonly expired: "expired";
 }; //#endregion
+//#region src/generated/model/getMySession200User.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+/**
+ * A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+property-named, so responses can mix users from different schemas.
+`identifier` and `display` are resolved independently from the user
+schema's `x-identifier` and `x-display` designations, live at read time.
+Clients render `display`, falling back to `identifier`, then `user_id`.
+
+ */
+type GetMySession200User = {
+  /** @pattern ^user_[a-zA-Z0-9_-]+$ */user_id: string;
+  /** The current value of the schema's designated identifier
+  (`x-identifier`). Absent when the schema designates no identifier or
+  the user carries no value for it.
+   */
+  identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order. Purely presentational, with no source attribution.
+  Absent when the schema designates no display properties or the user
+  carries no values for them.
+   */
+  display?: string;
+}; //#endregion
 //#region src/generated/model/getMySession200UserAgent.d.ts
 /**
  * Generated by orval v8.10.0 🍺
@@ -7232,23 +7338,13 @@ type GetMySession200 = {
   factor has been verified through an `auth_attempt`.
    */
   user_id?: string | null;
-  /** Human-readable name of the authenticated user, resolved from the
-  conventional user-schema properties: `name` when defined, otherwise
-  the given and family name parts joined — `givenName`/`familyName`
-  (the shipped presets' spelling) or `given_name`/`family_name`. Only
-  present on reads that hydrate the user's identity
-  (`GET /sessions/me`) and only when the session has an authenticated
-  user whose schema carries those properties; clients fall back to
-  `email`, then `user_id`.
+  /** A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+  property-named, so responses can mix users from different schemas.
+  `identifier` and `display` are resolved independently from the user
+  schema's `x-identifier` and `x-display` designations, live at read time.
+  Clients render `display`, falling back to `identifier`, then `user_id`.
    */
-  name?: string;
-  /** Email address of the authenticated user, resolved from the
-  conventional `email` user-schema property. Only present on reads
-  that hydrate the user's identity (`GET /sessions/me`) and only when
-  the session has an authenticated user whose schema carries that
-  property.
-   */
-  email?: string;
+  user?: GetMySession200User;
   /** Verified authentication factors accumulated by this session.
   Each key is a factor type (e.g. `password`, `totp`, `passkey`).
   Each value is a factor event object with at least `verified_at` and
@@ -7452,6 +7548,24 @@ type GetMyUser200 = {
    */
   attributes: GetMyUser200Attributes;
   metadata: GetMyUser200Metadata;
+  /** The current value of the user schema's designated identifier
+  (`x-identifier`), resolved live at read time. Absent when the schema
+  designates no identifier or the user carries no value for it.
+   */
+  readonly identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  readonly identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order, resolved live at read time. Purely presentational.
+  Absent when the schema designates no display properties or the user
+  carries no values for them. Clients render `display`, falling back
+  to `identifier`, then `id`.
+   */
+  readonly display?: string;
   /** The user's team memberships, present only when the request asked for them with
   `expand: ["teams"]` (ADR 059). Absent means it was not requested; `[]`
   means the user has none.
@@ -7924,6 +8038,42 @@ declare const GetSession200State: {
   readonly active: "active";
   readonly expired: "expired";
 }; //#endregion
+//#region src/generated/model/getSession200User.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+/**
+ * A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+property-named, so responses can mix users from different schemas.
+`identifier` and `display` are resolved independently from the user
+schema's `x-identifier` and `x-display` designations, live at read time.
+Clients render `display`, falling back to `identifier`, then `user_id`.
+
+ */
+type GetSession200User = {
+  /** @pattern ^user_[a-zA-Z0-9_-]+$ */user_id: string;
+  /** The current value of the schema's designated identifier
+  (`x-identifier`). Absent when the schema designates no identifier or
+  the user carries no value for it.
+   */
+  identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order. Purely presentational, with no source attribution.
+  Absent when the schema designates no display properties or the user
+  carries no values for them.
+   */
+  display?: string;
+}; //#endregion
 //#region src/generated/model/getSession200UserAgent.d.ts
 /**
  * Generated by orval v8.10.0 🍺
@@ -7967,23 +8117,13 @@ type GetSession200 = {
   factor has been verified through an `auth_attempt`.
    */
   user_id?: string | null;
-  /** Human-readable name of the authenticated user, resolved from the
-  conventional user-schema properties: `name` when defined, otherwise
-  the given and family name parts joined — `givenName`/`familyName`
-  (the shipped presets' spelling) or `given_name`/`family_name`. Only
-  present on reads that hydrate the user's identity
-  (`GET /sessions/me`) and only when the session has an authenticated
-  user whose schema carries those properties; clients fall back to
-  `email`, then `user_id`.
-   */
-  name?: string;
-  /** Email address of the authenticated user, resolved from the
-  conventional `email` user-schema property. Only present on reads
-  that hydrate the user's identity (`GET /sessions/me`) and only when
-  the session has an authenticated user whose schema carries that
-  property.
+  /** A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+  property-named, so responses can mix users from different schemas.
+  `identifier` and `display` are resolved independently from the user
+  schema's `x-identifier` and `x-display` designations, live at read time.
+  Clients render `display`, falling back to `identifier`, then `user_id`.
    */
-  email?: string;
+  user?: GetSession200User;
   /** Verified authentication factors accumulated by this session.
   Each key is a factor type (e.g. `password`, `totp`, `passkey`).
   Each value is a factor event object with at least `verified_at` and
@@ -8231,6 +8371,24 @@ type GetUserByID200 = {
    */
   attributes: GetUserByID200Attributes;
   metadata: GetUserByID200Metadata;
+  /** The current value of the user schema's designated identifier
+  (`x-identifier`), resolved live at read time. Absent when the schema
+  designates no identifier or the user carries no value for it.
+   */
+  readonly identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  readonly identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order, resolved live at read time. Purely presentational.
+  Absent when the schema designates no display properties or the user
+  carries no values for them. Clients render `display`, falling back
+  to `identifier`, then `id`.
+   */
+  readonly display?: string;
   /** The user's team memberships, present only when the request asked for them with
   `expand: ["teams"]` (ADR 059). Absent means it was not requested; `[]`
   means the user has none.
@@ -11319,6 +11477,42 @@ declare const QuerySessions200SessionsItemState: {
   readonly active: "active";
   readonly expired: "expired";
 }; //#endregion
+//#region src/generated/model/querySessions200SessionsItemUser.d.ts
+/**
+ * Generated by orval v8.10.0 🍺
+ * Do not edit manually.
+ * Zitadel NextGen
+ * This is the next generation of the Zitadel identity platform.
+ * OpenAPI spec version: 0.0.1
+ */
+/**
+ * A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+property-named, so responses can mix users from different schemas.
+`identifier` and `display` are resolved independently from the user
+schema's `x-identifier` and `x-display` designations, live at read time.
+Clients render `display`, falling back to `identifier`, then `user_id`.
+
+ */
+type QuerySessions200SessionsItemUser = {
+  /** @pattern ^user_[a-zA-Z0-9_-]+$ */user_id: string;
+  /** The current value of the schema's designated identifier
+  (`x-identifier`). Absent when the schema designates no identifier or
+  the user carries no value for it.
+   */
+  identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order. Purely presentational, with no source attribution.
+  Absent when the schema designates no display properties or the user
+  carries no values for them.
+   */
+  display?: string;
+}; //#endregion
 //#region src/generated/model/querySessions200SessionsItemUserAgent.d.ts
 /**
  * Generated by orval v8.10.0 🍺
@@ -11362,23 +11556,13 @@ type QuerySessions200SessionsItem = {
   factor has been verified through an `auth_attempt`.
    */
   user_id?: string | null;
-  /** Human-readable name of the authenticated user, resolved from the
-  conventional user-schema properties: `name` when defined, otherwise
-  the given and family name parts joined — `givenName`/`familyName`
-  (the shipped presets' spelling) or `given_name`/`family_name`. Only
-  present on reads that hydrate the user's identity
-  (`GET /sessions/me`) and only when the session has an authenticated
-  user whose schema carries those properties; clients fall back to
-  `email`, then `user_id`.
-   */
-  name?: string;
-  /** Email address of the authenticated user, resolved from the
-  conventional `email` user-schema property. Only present on reads
-  that hydrate the user's identity (`GET /sessions/me`) and only when
-  the session has an authenticated user whose schema carries that
-  property.
+  /** A resolved reference to a user (ADR 058 §3). Fields are role-named, not
+  property-named, so responses can mix users from different schemas.
+  `identifier` and `display` are resolved independently from the user
+  schema's `x-identifier` and `x-display` designations, live at read time.
+  Clients render `display`, falling back to `identifier`, then `user_id`.
    */
-  email?: string;
+  user?: QuerySessions200SessionsItemUser;
   /** Verified authentication factors accumulated by this session.
   Each key is a factor type (e.g. `password`, `totp`, `passkey`).
   Each value is a factor event object with at least `verified_at` and
@@ -11974,6 +12158,24 @@ type QueryUsers200UsersItem = {
    */
   attributes: QueryUsers200UsersItemAttributes;
   metadata: QueryUsers200UsersItemMetadata;
+  /** The current value of the user schema's designated identifier
+  (`x-identifier`), resolved live at read time. Absent when the schema
+  designates no identifier or the user carries no value for it.
+   */
+  readonly identifier?: string;
+  /** The schema property `identifier` came from, so clients can reach the
+  property's schema for semantics (a mailto link, a field label)
+  instead of guessing from the value. Present exactly when
+  `identifier` is.
+   */
+  readonly identifier_property?: string;
+  /** The `x-display` rendering — the designated properties' values joined
+  in list order, resolved live at read time. Purely presentational.
+  Absent when the schema designates no display properties or the user
+  carries no values for them. Clients render `display`, falling back
+  to `identifier`, then `id`.
+   */
+  readonly display?: string;
   /** The user's team memberships, present only when the request asked for them with
   `expand: ["teams"]` (ADR 059). Absent means it was not requested; `[]`
   means the user has none.
@@ -14430,7 +14632,7 @@ declare class ZlPasskey extends LitElement {
    */
   startCeremony(): Promise<void>;
   private handleCancelSubmit;
-  render(): typeof nothing | _$lit.TemplateResult<1>;
+  render(): _$lit.TemplateResult<1> | typeof nothing;
   /**
    * `navigator.credentials.get()` — authentication ceremony.
    */
@@ -14639,4 +14841,4 @@ declare global {
 } //# sourceMappingURL=zl-select.d.ts.map
 //#endregion
 export { CreateTeam201 as $, ListUserPasskeysParams as $t, CreateFlow201StepChallenge as A, ZlAlert as An, GetReleaseByIdParams as At, CreateGrantParams as B, ListBranding200Item as Bt, CreateBrandingBody as C, ZlCheckbox as Cn, GetHealthDefault as Ct, CreateFlow201BrandingLayout as D, zlCardManifest as Dn, GetProject200 as Dt, CreateFlow201Branding as E, ZlCard as En, GetMyUser200 as Et, CreateFlowBodyPurpose as F, ZlIcon as Fn, GetUserByID200 as Ft, CreateRelease201 as G, ListEventsParams as Gt, CreateProject201 as H, ListEnvironments200 as Ht, CreateFlowDefinition201 as I, zlIconManifest as In, GetUserByIDParams as It, CreateSchema201 as J, ListReleases200 as Jt, CreateReleaseBody as K, ListFlowDefinitions200 as Kt, CreateFlowDefinitionBody as L, InitClaim201 as Lt, CreateFlow201StepGates as M, IconName as Mn, GetSchemaByIdParams as Mt, CreateFlow201StepSsoProvidersItem as N, IconSize as Nn, GetSession200 as Nt, CreateFlow201Step as O, ZlButton as On, GetReadyDefault as Ot, CreateFlowBody as P, IconTone as Pn, GetTeam200 as Pt, CreateSessionBody as Q, ListUserPasskeys200 as Qt, CreateGrant201 as R, IssueChallenge201 as Rt, CreateBranding201 as S, VerifyChallengeProofBody as Sn, GetGrantParams as St, CreateFlow201 as T, zlCheckboxManifest as Tn, GetMySession200 as Tt, CreateProjectBody as U, ListEnvironmentsParams as Ut, CreateHandoff200 as V, ListBrandingParams as Vt, CreateRelease200 as W, ListEvents200 as Wt, CreateSchemaParams as X, ListSchemas200 as Xt, CreateSchemaBody as Y, ListReleasesParams as Yt, CreateSession201 as Z, ListSchemasParams as Zt, BeginUserPasskeyRegistrationBody as _, UpdateFlowDefinition200 as _n, GetEvent200 as _t, ZlPill as a, QueryProjectsBody as an, DeleteGrantParams as at, CreateAuthAttempt201 as b, UpdateTeamBody as bn, GetFlowStep200 as bt, ZlPasskeyErrorDetail as c, QuerySessionsParams as cn, ExchangeHandoffParams as ct, ZlPageShell as d, QueryTeamsParams as dn, GetAuthAttempt200 as dt, ListUserTeams200 as en, CreateTeamBody as et, zlPageShellManifest as f, QueryUsers200 as fn, GetBrandingById200 as ft, BeginUserPasskeyRegistration201 as g, SubmitFlowStepBody as gn, GetEnvironmentByNameParams as gt, zlFieldManifest as h, SubmitFlowStep200 as hn, GetEnvironmentByName200 as ht, zlSelectManifest as i, QueryProjects200 as in, CreateUserParams as it, CreateFlow201StepFieldsItem as j, zlAlertManifest as jn, GetSchemaById200 as jt, CreateFlow201StepActionsItem as k, zlButtonManifest as kn, GetReleaseById200 as kt, ZlPasskeyResultDetail as l, QueryTeams200 as ln, FinishUserPasskeyRegistration201 as lt, ZlFieldType as m, SetUserPasswordBody as mn, GetClaimStatusParams as mt, ZlSelectChangeDetail as n, PatchProject200 as nn, CreateUser201 as nt, zlPillManifest as o, QuerySessions200 as on, ExchangeHandoff200 as ot, ZlField as p, QueryUsersBody as pn, GetClaimStatus200 as pt, CreateReleaseParams as q, ListFlowDefinitionsParams as qt, ZlSelectOption as r, PatchProjectBody as rn, CreateUserBody as rt, ZlPasskey as s, QuerySessionsBody as sn, ExchangeHandoffBody as st, ZlSelect as t, ListUserTeamsParams as tn, CreateTeamParams as tt, zlPasskeyManifest as u, QueryTeamsBody as un, FinishUserPasskeyRegistrationBody as ut, CompleteClaim200 as v, UpdateFlowDefinitionBody as vn, GetEventParams as vt, CreateBrandingParams as w, ZlCheckboxChangeDetail as wn, GetLiveDefault as wt, CreateAuthAttemptBody as x, VerifyChallengeProof200 as xn, GetGrant200 as xt, CompleteClaimBody as y, UpdateTeam200 as yn, GetFlowDefinition200 as yt, CreateGrantBody as z, IssueChallengeBody as zt };
-//# sourceMappingURL=index-BPgWdWx7.d.mts.map
+//# sourceMappingURL=index-Dx8rvpNs.d.mts.map