hanzoai 8.5.755 → 8.5.889

package/dist/api/account-api.d.ts

@@ -107,8 +107,8 @@ export declare const AccountApiAxiosParamCreator: (configuration?: Configuration
      */
     postAccountKeys: (accountKeyIn: AccountKeyIn, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-     * @summary Creates the caller\'s organization.
+     * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+     * @summary Creates an organization and makes the caller its owner.
      * @param {AccountOnboardReq} accountOnboardReq
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
@@ -200,8 +200,8 @@ export declare const AccountApiFp: (configuration?: Configuration) => {
      */
     postAccountKeys(accountKeyIn: AccountKeyIn, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<AccountApiKey>>;
     /**
-     * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-     * @summary Creates the caller\'s organization.
+     * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+     * @summary Creates an organization and makes the caller its owner.
      * @param {AccountOnboardReq} accountOnboardReq
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
@@ -290,8 +290,8 @@ export declare const AccountApiFactory: (configuration?: Configuration, basePath
      */
     postAccountKeys(requestParameters: AccountApiPostAccountKeysRequest, options?: RawAxiosRequestConfig): AxiosPromise<AccountApiKey>;
     /**
-     * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-     * @summary Creates the caller\'s organization.
+     * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+     * @summary Creates an organization and makes the caller its owner.
      * @param {AccountApiPostAccountOrgsRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
@@ -501,8 +501,8 @@ export declare class AccountApi extends BaseAPI {
      */
     postAccountKeys(requestParameters: AccountApiPostAccountKeysRequest, options?: RawAxiosRequestConfig): Promise<globalAxios.AxiosResponse<AccountApiKey, any, {}>>;
     /**
-     * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-     * @summary Creates the caller\'s organization.
+     * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+     * @summary Creates an organization and makes the caller its owner.
      * @param {AccountApiPostAccountOrgsRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}

package/dist/api/account-api.js

@@ -349,8 +349,8 @@ const AccountApiAxiosParamCreator = function (configuration) {
             };
         },
         /**
-         * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-         * @summary Creates the caller\'s organization.
+         * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+         * @summary Creates an organization and makes the caller its owner.
          * @param {AccountOnboardReq} accountOnboardReq
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
@@ -521,8 +521,8 @@ const AccountApiFp = function (configuration) {
             return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
         /**
-         * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-         * @summary Creates the caller\'s organization.
+         * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+         * @summary Creates an organization and makes the caller its owner.
          * @param {AccountOnboardReq} accountOnboardReq
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
@@ -640,8 +640,8 @@ const AccountApiFactory = function (configuration, basePath, axios) {
             return localVarFp.postAccountKeys(requestParameters.accountKeyIn, options).then((request) => request(axios, basePath));
         },
         /**
-         * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-         * @summary Creates the caller\'s organization.
+         * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+         * @summary Creates an organization and makes the caller its owner.
          * @param {AccountApiPostAccountOrgsRequest} requestParameters Request parameters.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
@@ -766,8 +766,8 @@ class AccountApi extends base_1.BaseAPI {
         return (0, exports.AccountApiFp)(this.configuration).postAccountKeys(requestParameters.accountKeyIn, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Creates the caller\'s organization. Two flows, keyed on whether the caller already has a home org (mirrors app/onboard/route.ts):    - FIRST-RUN (no home org): create + MOVE the user in as admin, so their next     JWT carries the new owner and the cloud scopes everything to it. This is the     path a fresh OAuth sign-up takes, from the sign-up application\'s org.   - ADDITIONAL (owner set): create the org but do NOT move the user — a move     changes their IAM owner (stripping a SuperAdmin\'s status + orphaning their     current org). They reach the new org via the OrgSwitcher, which re-scopes     X-Org-Id without touching IAM membership. A personal-org request from someone     who already has an org is meaningless → 409.
-     * @summary Creates the caller\'s organization.
+     * Creates an organization and makes the caller its owner.  The caller\'s own account is not touched: who they are, the org their account lives in and how they sign in are the same before and after. The new org is a separate organization they belong to by membership, carried in the signed `orgs` claim of their next token, and reached by selecting it (X-Org-Id, the org switcher). Teammates join it the same way. The org starts at a zero balance, and its default API key is minted for the creator and returned once.  Moving the creator into the org instead re-keyed their identity to \"<org>/<name>\", and sign-in, which resolves an address in the signup org, then found nobody: the person was offered a second account for their own address.
+     * @summary Creates an organization and makes the caller its owner.
      * @param {AccountApiPostAccountOrgsRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}