@arbidocs/client 0.3.59 → 0.3.61

package/dist/index.d.cts

@@ -534,6 +534,83 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/user/profile': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        /**
+         * Update Profile
+         * @description Update user's display profile (given_name, family_name, picture).
+         *
+         *     Pass an empty string to clear family_name or picture; null means "leave unchanged".
+         */
+        patch: operations['update_profile'];
+        trace?: never;
+    };
+    '/v1/user/request-email-change': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Request Email Change
+         * @description Send a verification code to the new email address.
+         *
+         *     SSO users cannot change their email here — Auth0 with account linking
+         *     makes the semantics ambiguous (which linked identity? what about social
+         *     providers that own the email upstream?). They change it at their IdP and
+         *     /sso-status syncs it on next login.
+         *
+         *     The code is generated deterministically from (new_email, current_user.external_id)
+         *     so that only this user can complete the change.
+         */
+        post: operations['request_email_change'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/user/confirm-email-change': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Confirm Email Change
+         * @description Confirm email change with verification code.
+         *
+         *     Verifies the 3-word code, then atomically updates:
+         *     1. users.email
+         *     2. contacts.contact_email (all references to old email)
+         *     3. Stripe customer email (fire-and-forget)
+         *
+         *     SSO users are blocked — see /request-email-change for rationale.
+         */
+        post: operations['confirm_email_change'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/user/settings': {
         parameters: {
             query?: never;
@@ -2128,8 +2205,8 @@ interface components {
             AGENT_API_TYPE: 'local' | 'remote';
             /**
              * Llm Agent Temperature
-             * @description Temperature value for agent LLM.
-             * @default 1
+             * @description Temperature value for agent LLM. 0.6 matches the value recommended upstream for Qwen3-27B-AWQ-INT4 with thinking enabled. Higher values (we used to default to 1.0) cause the model to drift from the canonical tool-call grammar under complex agent contexts, producing malformed XML / JSON that vLLM's tool-call parser cannot extract — measured 20% tool-call success at temp=1.0 vs 100% at temp=0.6 on the same 20-run hard-tool-required test.
+             * @default 0.6
              */
             LLM_AGENT_TEMPERATURE: number;
             /**
@@ -2190,6 +2267,10 @@ interface components {
              *     - Numbering for sequential steps or prioritized items
              *     - Bold text for critical conclusions or decision points
              *
+             *     TOOL CALLING:
+             *     - Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write "Searching for X...", "Reading document Y...", "Calling search_inside_documents" as prose — actually call the tool).
+             *     - If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.
+             *
              *     EFFICIENCY:
              *     1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.
              *     2. Call multiple tools in parallel when a query has several aspects.
@@ -2257,13 +2338,13 @@ interface components {
              *       "PERSONA": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.",
              *       "AGENT_MODEL_NAME": "auto",
              *       "AGENT_API_TYPE": "remote",
-             *       "LLM_AGENT_TEMPERATURE": 1,
+             *       "LLM_AGENT_TEMPERATURE": 0.6,
              *       "AGENT_MAX_TOKENS": 10000,
              *       "ENABLE_THINKING": false,
              *       "AGENT_MAX_ITERATIONS": 20,
              *       "AGENT_MAX_PARALLEL_TOOL_CALLS": 10,
              *       "AGENT_HISTORY_CHAR_THRESHOLD": 8000,
-             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
+             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write \"Searching for X...\", \"Reading document Y...\", \"Calling search_inside_documents\" as prose — actually call the tool).\n- If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
              *     }
              */
             Agents: components['schemas']['AgentsConfig'];
@@ -3071,6 +3152,23 @@ interface components {
             /** Confirm Email */
             confirm_email: string;
         };
+        /** ConfirmEmailChangeRequest */
+        ConfirmEmailChangeRequest: {
+            /**
+             * New Email
+             * Format: email
+             */
+            new_email: string;
+            /** Verification Code */
+            verification_code: string;
+        };
+        /** ConfirmEmailChangeResponse */
+        ConfirmEmailChangeResponse: {
+            /** Detail */
+            detail: string;
+            /** Email */
+            email: string;
+        };
         /**
          * ConnectionClosedMessage
          * @description Sent when connection is closed (e.g., another tab opened).
@@ -3469,6 +3567,8 @@ interface components {
             status?: string | null;
             /** Error Message */
             error_message?: string | null;
+            /** Failed Stage */
+            failed_stage?: string | null;
             /** N Pages */
             n_pages?: number | null;
             /** N Chunks */
@@ -5404,6 +5504,19 @@ interface components {
             /** Users */
             users: components['schemas']['RemoveWorkspaceUserItem'][];
         };
+        /** RequestEmailChangeRequest */
+        RequestEmailChangeRequest: {
+            /**
+             * New Email
+             * Format: email
+             */
+            new_email: string;
+        };
+        /** RequestEmailChangeResponse */
+        RequestEmailChangeResponse: {
+            /** Detail */
+            detail: string;
+        };
         /**
          * RerankerConfig
          * @description Wire/storage shape for reranker settings.
@@ -6765,6 +6878,8 @@ interface components {
             status: 'uploading' | 'queued' | 'parsing' | 'encrypting' | 'indexing' | 'analysing' | 'completed' | 'failed' | 'skipped' | 'empty' | 'low-content';
             /** Progress */
             progress: number;
+            /** Failed Stage */
+            failed_stage?: string | null;
         };
         /** Thread */
         Thread: {
@@ -7021,6 +7136,26 @@ interface components {
             /** Updates */
             updates: components['schemas']['NotificationUpdate'][];
         };
+        /** UpdateProfileRequest */
+        UpdateProfileRequest: {
+            /** Given Name */
+            given_name?: string | null;
+            /** Family Name */
+            family_name?: string | null;
+            /** Picture */
+            picture?: string | null;
+        };
+        /** UpdateProfileResponse */
+        UpdateProfileResponse: {
+            /** Given Name */
+            given_name: string;
+            /** Family Name */
+            family_name?: string | null;
+            /** Email */
+            email: string;
+            /** Picture */
+            picture?: string | null;
+        };
         /** UpdateTagRequest */
         UpdateTagRequest: {
             /** Name */
@@ -7252,6 +7387,11 @@ interface components {
             picture?: string | null;
             /** Encryption Public Key */
             encryption_public_key: string;
+            /**
+             * Is Sso
+             * @default false
+             */
+            is_sso: boolean;
         };
         /**
          * UserSettingsResponse
@@ -7619,6 +7759,11 @@ interface components {
             updated_at: string;
             /** Wrapped Key */
             wrapped_key?: string | null;
+            /**
+             * Is Member
+             * @default false
+             */
+            is_member: boolean;
             /**
              * Shared Conversation Count
              * @default 0
@@ -8517,6 +8662,105 @@ interface operations {
             };
         };
     };
+    update_profile: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['UpdateProfileRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['UpdateProfileResponse'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    request_email_change: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['RequestEmailChangeRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['RequestEmailChangeResponse'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    confirm_email_change: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['ConfirmEmailChangeRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['ConfirmEmailChangeResponse'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     get_user_settings: {
         parameters: {
             query?: never;

package/dist/index.d.ts

@@ -534,6 +534,83 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/user/profile': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        /**
+         * Update Profile
+         * @description Update user's display profile (given_name, family_name, picture).
+         *
+         *     Pass an empty string to clear family_name or picture; null means "leave unchanged".
+         */
+        patch: operations['update_profile'];
+        trace?: never;
+    };
+    '/v1/user/request-email-change': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Request Email Change
+         * @description Send a verification code to the new email address.
+         *
+         *     SSO users cannot change their email here — Auth0 with account linking
+         *     makes the semantics ambiguous (which linked identity? what about social
+         *     providers that own the email upstream?). They change it at their IdP and
+         *     /sso-status syncs it on next login.
+         *
+         *     The code is generated deterministically from (new_email, current_user.external_id)
+         *     so that only this user can complete the change.
+         */
+        post: operations['request_email_change'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/user/confirm-email-change': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Confirm Email Change
+         * @description Confirm email change with verification code.
+         *
+         *     Verifies the 3-word code, then atomically updates:
+         *     1. users.email
+         *     2. contacts.contact_email (all references to old email)
+         *     3. Stripe customer email (fire-and-forget)
+         *
+         *     SSO users are blocked — see /request-email-change for rationale.
+         */
+        post: operations['confirm_email_change'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/user/settings': {
         parameters: {
             query?: never;
@@ -2128,8 +2205,8 @@ interface components {
             AGENT_API_TYPE: 'local' | 'remote';
             /**
              * Llm Agent Temperature
-             * @description Temperature value for agent LLM.
-             * @default 1
+             * @description Temperature value for agent LLM. 0.6 matches the value recommended upstream for Qwen3-27B-AWQ-INT4 with thinking enabled. Higher values (we used to default to 1.0) cause the model to drift from the canonical tool-call grammar under complex agent contexts, producing malformed XML / JSON that vLLM's tool-call parser cannot extract — measured 20% tool-call success at temp=1.0 vs 100% at temp=0.6 on the same 20-run hard-tool-required test.
+             * @default 0.6
              */
             LLM_AGENT_TEMPERATURE: number;
             /**
@@ -2190,6 +2267,10 @@ interface components {
              *     - Numbering for sequential steps or prioritized items
              *     - Bold text for critical conclusions or decision points
              *
+             *     TOOL CALLING:
+             *     - Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write "Searching for X...", "Reading document Y...", "Calling search_inside_documents" as prose — actually call the tool).
+             *     - If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.
+             *
              *     EFFICIENCY:
              *     1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.
              *     2. Call multiple tools in parallel when a query has several aspects.
@@ -2257,13 +2338,13 @@ interface components {
              *       "PERSONA": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.",
              *       "AGENT_MODEL_NAME": "auto",
              *       "AGENT_API_TYPE": "remote",
-             *       "LLM_AGENT_TEMPERATURE": 1,
+             *       "LLM_AGENT_TEMPERATURE": 0.6,
              *       "AGENT_MAX_TOKENS": 10000,
              *       "ENABLE_THINKING": false,
              *       "AGENT_MAX_ITERATIONS": 20,
              *       "AGENT_MAX_PARALLEL_TOOL_CALLS": 10,
              *       "AGENT_HISTORY_CHAR_THRESHOLD": 8000,
-             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
+             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write \"Searching for X...\", \"Reading document Y...\", \"Calling search_inside_documents\" as prose — actually call the tool).\n- If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
              *     }
              */
             Agents: components['schemas']['AgentsConfig'];
@@ -3071,6 +3152,23 @@ interface components {
             /** Confirm Email */
             confirm_email: string;
         };
+        /** ConfirmEmailChangeRequest */
+        ConfirmEmailChangeRequest: {
+            /**
+             * New Email
+             * Format: email
+             */
+            new_email: string;
+            /** Verification Code */
+            verification_code: string;
+        };
+        /** ConfirmEmailChangeResponse */
+        ConfirmEmailChangeResponse: {
+            /** Detail */
+            detail: string;
+            /** Email */
+            email: string;
+        };
         /**
          * ConnectionClosedMessage
          * @description Sent when connection is closed (e.g., another tab opened).
@@ -3469,6 +3567,8 @@ interface components {
             status?: string | null;
             /** Error Message */
             error_message?: string | null;
+            /** Failed Stage */
+            failed_stage?: string | null;
             /** N Pages */
             n_pages?: number | null;
             /** N Chunks */
@@ -5404,6 +5504,19 @@ interface components {
             /** Users */
             users: components['schemas']['RemoveWorkspaceUserItem'][];
         };
+        /** RequestEmailChangeRequest */
+        RequestEmailChangeRequest: {
+            /**
+             * New Email
+             * Format: email
+             */
+            new_email: string;
+        };
+        /** RequestEmailChangeResponse */
+        RequestEmailChangeResponse: {
+            /** Detail */
+            detail: string;
+        };
         /**
          * RerankerConfig
          * @description Wire/storage shape for reranker settings.
@@ -6765,6 +6878,8 @@ interface components {
             status: 'uploading' | 'queued' | 'parsing' | 'encrypting' | 'indexing' | 'analysing' | 'completed' | 'failed' | 'skipped' | 'empty' | 'low-content';
             /** Progress */
             progress: number;
+            /** Failed Stage */
+            failed_stage?: string | null;
         };
         /** Thread */
         Thread: {
@@ -7021,6 +7136,26 @@ interface components {
             /** Updates */
             updates: components['schemas']['NotificationUpdate'][];
         };
+        /** UpdateProfileRequest */
+        UpdateProfileRequest: {
+            /** Given Name */
+            given_name?: string | null;
+            /** Family Name */
+            family_name?: string | null;
+            /** Picture */
+            picture?: string | null;
+        };
+        /** UpdateProfileResponse */
+        UpdateProfileResponse: {
+            /** Given Name */
+            given_name: string;
+            /** Family Name */
+            family_name?: string | null;
+            /** Email */
+            email: string;
+            /** Picture */
+            picture?: string | null;
+        };
         /** UpdateTagRequest */
         UpdateTagRequest: {
             /** Name */
@@ -7252,6 +7387,11 @@ interface components {
             picture?: string | null;
             /** Encryption Public Key */
             encryption_public_key: string;
+            /**
+             * Is Sso
+             * @default false
+             */
+            is_sso: boolean;
         };
         /**
          * UserSettingsResponse
@@ -7619,6 +7759,11 @@ interface components {
             updated_at: string;
             /** Wrapped Key */
             wrapped_key?: string | null;
+            /**
+             * Is Member
+             * @default false
+             */
+            is_member: boolean;
             /**
              * Shared Conversation Count
              * @default 0
@@ -8517,6 +8662,105 @@ interface operations {
             };
         };
     };
+    update_profile: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['UpdateProfileRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['UpdateProfileResponse'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    request_email_change: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['RequestEmailChangeRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['RequestEmailChangeResponse'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    confirm_email_change: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['ConfirmEmailChangeRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['ConfirmEmailChangeResponse'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     get_user_settings: {
         parameters: {
             query?: never;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arbidocs/client",
-  "version": "0.3.59",
+  "version": "0.3.61",
   "description": "TypeScript SDK for the ARBI API — zero-knowledge auth, E2E encryption, and type-safe REST client",
   "type": "module",
   "main": "dist/index.cjs",
@@ -29,7 +29,7 @@
     "@types/libsodium-wrappers-sumo": "^0.8.2",
     "fake-indexeddb": "^6.2.5",
     "tsup": "^8.4.0",
-    "typescript": "^5.9.3",
+    "typescript": "^6.0.3",
     "vitest": "^4.0.18"
   },
   "license": "MIT",