@arbidocs/client 0.3.146 → 0.3.147

package/dist/index.d.cts

@@ -885,15 +885,37 @@ interface paths {
         put?: never;
         /**
          * Copy Workspace Data
-         * @description Copy documents from source workspace (current) to target workspace.
+         * @description Copy selected items from the source workspace (current) to a target workspace.
          *
          *     Requires workspace-scoped JWT for the source workspace.
          *     Target workspace key is provided in the request body (SecretBox-encrypted with session key).
          *
-         *     Copies:
-         *     - Document metadata (title, doc_date, shared status, etc.)
-         *     - MinIO encrypted files (downloaded to server memory, re-encrypted, uploaded)
-         *     - Qdrant vectors (with updated doc_ext_id and chunk_ext_id references)
+         *     ``items`` is a flat, heterogeneous list of external IDs; the prefix selects
+         *     what is copied, and **exactly** the listed items are copied — nothing rides
+         *     along:
+         *
+         *     - ``doc-`` document — row + MinIO files + Qdrant vectors, all re-encrypted
+         *       with the target workspace key. Chunk external IDs are preserved.
+         *     - ``tag-`` tag — merged into a same-named tag already in the target if there
+         *       is one, otherwise created. A parent tag that is not in the target flattens
+         *       the copy to a root tag.
+         *     - ``dtj-`` doctag — requires BOTH its document (selected in the same request)
+         *       and its tag (selected, or already present by name) in the target; RLS makes
+         *       any other combination impossible. Fails with a reason otherwise.
+         *     - ``fct-`` fact — content, date span, timezone and citations preserved; pins
+         *       are not (a pin is the pinning account's own state).
+         *     - ``con-`` chat — conversation + every message, with the parent/child tree
+         *       and the encrypted ``tools`` blob rebuilt.
+         *
+         *     Facts and chats need no vector copy: both live in pointer-only collections
+         *     keyed by external ID and are indexed on write / by the lazy backfill.
+         *
+         *     ``created_by`` is NOT preserved. Every content table's RLS ``WITH CHECK``
+         *     forces it to the copying user, so copies are attributed to whoever ran the
+         *     copy, never to the original author.
+         *
+         *     Each item is copied in its own savepoint, so one failure does not abort the
+         *     batch; per-item outcomes are in ``results``.
          */
         post: operations['copy_workspace_data'];
         delete?: never;
@@ -930,28 +952,6 @@ interface paths {
         patch: operations['update_workspace'];
         trace?: never;
     };
-    '/v1/workspace/{workspace_ext_id}/chronology': {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        /**
-         * Get Workspace Chronology
-         * @description Return the last-generated chronology for a workspace.
-         *
-         *     Returns all-null fields when no chronology has been generated yet.
-         */
-        get: operations['get_workspace_chronology'];
-        put?: never;
-        post?: never;
-        delete?: never;
-        options?: never;
-        head?: never;
-        patch?: never;
-        trace?: never;
-    };
     '/v1/document/list': {
         parameters: {
             query?: never;
@@ -1345,30 +1345,6 @@ interface paths {
         patch?: never;
         trace?: never;
     };
-    '/v1/document/chronology': {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        get?: never;
-        put?: never;
-        /**
-         * Generate Workspace Chronology
-         * @description Generate a chronological timeline of events from the specified documents.
-         *
-         *     Runs LLM analysis over the selected documents and persists the result in the
-         *     workspace_chronology table (one row per workspace, upserted on each generation).
-         *     Returns the generated events alongside metadata about when they were produced.
-         */
-        post: operations['generate_chronology'];
-        delete?: never;
-        options?: never;
-        head?: never;
-        patch?: never;
-        trace?: never;
-    };
     '/v1/conversation/list': {
         parameters: {
             query?: never;
@@ -3656,6 +3632,24 @@ interface components {
              * @default 10
              */
             AGENT_MAX_PARALLEL_TOOL_CALLS: number;
+            /**
+             * Agent Max Total Tool Calls
+             * @description Run-wide cap on tool executions across the main agent AND all nested sub-agents (deep_research / run_skill / sub_agent) in a single user query. When reached, further tool calls are refused and the agent is forced to answer from what it has gathered; at 2x the run is hard-stopped. 0 = disabled.
+             * @default 80
+             */
+            AGENT_MAX_TOTAL_TOOL_CALLS: number;
+            /**
+             * Agent Max Run Tokens
+             * @description Run-wide cap on total tokens (input+output+reasoning, provider-reported) across every LLM call in a single user query — agent iterations, nested sub-agents, and helper calls (evaluator, reranker, goal judge). When reached the agent is forced to answer from what it has gathered; at 2x the run is hard-stopped. Best-effort metering — the exact AGENT_MAX_TOTAL_TOOL_CALLS meter backs it up. 0 = disabled.
+             * @default 1500000
+             */
+            AGENT_MAX_RUN_TOKENS: number;
+            /**
+             * Agent Max Subagent Spawns
+             * @description Run-wide cap on nested sub-agent spawns (deep_research / run_skill / sub_agent) in a single user query. Past the cap, spawning tools are refused while direct tools keep working until the tool-call cap. 0 = no spawns.
+             * @default 4
+             */
+            AGENT_MAX_SUBAGENT_SPAWNS: number;
             /**
              * Agent History Char Threshold
              * @description Char threshold for conversation history injected into the agent context. Below: verbatim user/assistant pairs. Above: summarized by SummariseLLM.
@@ -3674,14 +3668,17 @@ interface components {
              *     DOCUMENT INDEX:
              *     The "Workspace Documents" table in your system prompt lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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.
              *
-             *     DOCUMENT STRATEGY:
-             *     - For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.
-             *     - For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.
-             *     - For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.
-             *     - For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.
-             *     - For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.
-             *     - For open-ended investigative queries ("find interesting things", "what's notable", "what stands out", "explore X", "what should I know about", "any findings", "anything unusual", "key insights"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.
-             *     - Never search for meta-queries like "summary", "overview", or "all documents" — search for the actual subject matter.
+             *     READING TOOL RESULTS:
+             *     Every retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example "FULL CONTENT … complete verbatim text, all 10 pages" or "DIGEST … verbatim page text is NOT part of this result"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.
+             *
+             *     DOCUMENT STRATEGY, in order:
+             *     1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.
+             *     2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.
+             *     3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.
+             *     4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.
+             *     5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.
+             *     6. Open-ended investigative queries ("find interesting things", "what's notable", "what stands out", "explore X", "what should I know about", "any findings", "anything unusual", "key insights"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.
+             *     7. Never search for meta-queries like "summary", "overview", or "all documents" — search for the actual subject matter.
              *
              *     FORMATTING:
              *     - 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).
@@ -3692,14 +3689,14 @@ interface components {
              *     - Bold text for critical conclusions or decision points
              *
              *     TOOL CALLING:
-             *     - Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.
+             *     - Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.
              *     - 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.
-             *     3. NEVER repeat a tool call with the same arguments.
+             *     3. NEVER repeat a tool call with the same arguments, and never re-retrieve material you already hold — the caption on each result tells you what that is.
              *     4. Use targeted queries and narrow page ranges per retrieval call.
              *     5. Stop when you have sufficient evidence — do not over-research.
              */
@@ -3893,8 +3890,11 @@ interface components {
              *       "AGENT_MAX_ITERATIONS": 20,
              *       "AGENT_TURN_CREDIT_BUDGET": 50,
              *       "AGENT_MAX_PARALLEL_TOOL_CALLS": 10,
+             *       "AGENT_MAX_TOTAL_TOOL_CALLS": 80,
+             *       "AGENT_MAX_RUN_TOKENS": 1500000,
+             *       "AGENT_MAX_SUBAGENT_SPAWNS": 4,
              *       "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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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- For open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\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- Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.\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."
+             *       "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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. 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- Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.\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, and never re-retrieve material you already hold — the caption on each result tells you what that is.\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'];
@@ -4250,7 +4250,7 @@ interface components {
             type: 'arbi.error';
             /**
              * Code
-             * @description Error code, e.g. 'QUOTA_EXCEEDED'
+             * @description Error code, e.g. 'QUOTA_EXCEEDED' (billing — opens upgrade modal) or 'RUN_BUDGET_EXCEEDED' (per-run safety cap — generic error display).
              */
             code: string;
             /**
@@ -4286,6 +4286,11 @@ interface components {
          *     field) while ours reads it. The item itself stays byte-for-byte standard.
          */
         ArbiItemMeta: {
+            /**
+             * Step
+             * @description Which lifecycle moment this item IS — stated, not inferred. A Responses item type (message / function_call / reasoning) is too coarse for the trace: three different reasoning items are the goal, the plan and a goal check, and the answer is a `message` item that is nonetheless a trace row. Clients previously sniffed `label` prefixes to tell them apart, which broke the moment a label was reworded or localised. Absent on plain tool calls (they carry `detail`) and on narration messages (which are body text, not a step).
+             */
+            step?: ('goal' | 'skill' | 'interjection' | 'planning' | 'tool_progress' | 'goal_progress' | 'answering' | 'evaluation') | null;
             /**
              * Label
              * @description Human display label. Backend-owned.
@@ -4645,11 +4650,6 @@ interface components {
         } & {
             [key: string]: unknown;
         };
-        /** ChronologyRequest */
-        ChronologyRequest: {
-            /** Doc Ext Ids */
-            doc_ext_ids: string[];
-        };
         /** Chunk */
         Chunk: {
             metadata: components['schemas']['ChunkMetadata'];
@@ -5349,7 +5349,15 @@ interface components {
             /** Title */
             title: string;
         };
-        /** CopyDocumentResult */
+        /**
+         * CopyDocumentResult
+         * @description Outcome of copying ONE selected item.
+         *
+         *     Named for documents because that is all ``/workspace/copy`` used to move;
+         *     the field names are kept so existing clients keep parsing the response.
+         *     ``source_doc_ext_id`` / ``new_doc_ext_id`` carry the source and new external
+         *     ID of whatever ``kind`` the item is.
+         */
         CopyDocumentResult: {
             /** Source Doc Ext Id */
             source_doc_ext_id: string;
@@ -5359,7 +5367,17 @@ interface components {
             new_doc_ext_id?: string | null;
             /** Error */
             error?: string | null;
+            /** @default document */
+            kind: components['schemas']['CopyItemKind'];
+            /** Warning */
+            warning?: string | null;
         };
+        /**
+         * CopyItemKind
+         * @description Which entity a copy result refers to — derived from the ext-id prefix.
+         * @enum {string}
+         */
+        CopyItemKind: 'document' | 'tag' | 'doctag' | 'fact' | 'chat' | 'unknown';
         /** CopyRequest */
         CopyRequest: {
             /** Target Workspace Ext Id */
@@ -5371,7 +5389,7 @@ interface components {
             target_workspace_key: string;
             /**
              * Items
-             * @description List of document external IDs to copy (e.g., ['doc-a1b2c3d4', 'doc-e5f6g7h8'])
+             * @description External IDs to copy. Heterogeneous: documents (doc-), tags (tag-), doctags (dtj-), facts (fct-) and chats (con-) may be mixed in one call — the server dispatches on the prefix and copies them in dependency order (tags → documents → doctags/facts → chats). Selection is exact: nothing is copied that was not listed.
              */
             items: string[];
         };
@@ -5384,6 +5402,18 @@ interface components {
              * @default 0
              */
             documents_copied: number;
+            /**
+             * Items Copied
+             * @default 0
+             */
+            items_copied: number;
+            /**
+             * Copied By Kind
+             * @default {}
+             */
+            copied_by_kind: {
+                [key: string]: number;
+            };
             /**
              * Results
              * @default []
@@ -5881,6 +5911,8 @@ interface components {
             /** Note */
             note?: string | null;
             citations?: components['schemas']['CitationSources'] | null;
+            /** External Id */
+            external_id: string;
             /** Doc Ext Id */
             doc_ext_id: string;
             /** Tag Ext Id */
@@ -6292,17 +6324,6 @@ interface components {
             /** Message */
             message: string;
         };
-        /**
-         * EvaluationDetail
-         * @description Detail for an evaluation learning entry.
-         */
-        EvaluationDetail: {
-            /**
-             * Statement
-             * @description Citation/finding statement
-             */
-            statement: string;
-        };
         /** EvaluatorLLMConfig */
         EvaluatorLLMConfig: {
             /**
@@ -9491,8 +9512,6 @@ interface components {
             detail_run_code?: components['schemas']['RunCodeDetail'] | null;
             detail_create_artifact?: components['schemas']['CreateArtifactDetail'] | null;
             detail_ask_user?: components['schemas']['AskUserDetail'] | null;
-            detail_evaluation?: components['schemas']['EvaluationDetail'] | null;
-            detail_tool_progress?: components['schemas']['ToolProgressDetail'] | null;
             detail_goal_progress?: components['schemas']['GoalProgressDetail'] | null;
         };
         /**
@@ -10493,22 +10512,6 @@ interface components {
             /** @description Aggregate usage across all LLM calls in the request */
             all_llm_calls?: components['schemas']['AllLlmCallsAggregate'] | null;
         };
-        /**
-         * ToolProgressDetail
-         * @description Detail for a tool progress update.
-         */
-        ToolProgressDetail: {
-            /**
-             * Tool
-             * @description Tool name
-             */
-            tool: string;
-            /**
-             * Message
-             * @description Progress message
-             */
-            message: string;
-        };
         /**
          * TraceTool
          * @description Execution trace tool that captures the full execution history of a request.
@@ -11020,11 +11023,6 @@ interface components {
              * @default false
              */
             show_skills: boolean;
-            /**
-             * Show Chronology
-             * @default false
-             */
-            show_chronology: boolean;
             /**
              * Show Pa Mode
              * @default false
@@ -11148,8 +11146,6 @@ interface components {
             show_templates?: boolean | null;
             /** Show Skills */
             show_skills?: boolean | null;
-            /** Show Chronology */
-            show_chronology?: boolean | null;
             /** Show Pa Mode */
             show_pa_mode?: boolean | null;
             /** Show Conversation Search */
@@ -11358,23 +11354,6 @@ interface components {
             auth?: components['schemas']['AuthMessage'] | null;
             send_message?: components['schemas']['SendMessageRequest'] | null;
         };
-        /**
-         * WorkspaceChronologyOut
-         * @description API response for both POST /v1/document/chronology and GET /v1/workspace/chronology.
-         *
-         *     For POST: all fields are always populated (generation just happened).
-         *     For GET: all fields are null when no chronology has been generated yet.
-         */
-        WorkspaceChronologyOut: {
-            /** Events */
-            events?: {
-                [key: string]: unknown;
-            }[] | null;
-            /** Generated At */
-            generated_at?: string | null;
-            /** Doc Count */
-            doc_count?: number | null;
-        };
         /** WorkspaceCreateRequest */
         WorkspaceCreateRequest: {
             /** Name */
@@ -12935,37 +12914,6 @@ interface operations {
             };
         };
     };
-    get_workspace_chronology: {
-        parameters: {
-            query?: never;
-            header?: never;
-            path: {
-                workspace_ext_id: string;
-            };
-            cookie?: never;
-        };
-        requestBody?: never;
-        responses: {
-            /** @description Successful Response */
-            200: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['WorkspaceChronologyOut'];
-                };
-            };
-            /** @description Validation Error */
-            422: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['HTTPValidationError'];
-                };
-            };
-        };
-    };
     list_documents: {
         parameters: {
             query?: {
@@ -13575,39 +13523,6 @@ interface operations {
             };
         };
     };
-    generate_chronology: {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        requestBody: {
-            content: {
-                'application/json': components['schemas']['ChronologyRequest'];
-            };
-        };
-        responses: {
-            /** @description Successful Response */
-            200: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['WorkspaceChronologyOut'];
-                };
-            };
-            /** @description Validation Error */
-            422: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['HTTPValidationError'];
-                };
-            };
-        };
-    };
     list_conversations: {
         parameters: {
             query?: never;

package/dist/index.d.ts

@@ -885,15 +885,37 @@ interface paths {
         put?: never;
         /**
          * Copy Workspace Data
-         * @description Copy documents from source workspace (current) to target workspace.
+         * @description Copy selected items from the source workspace (current) to a target workspace.
          *
          *     Requires workspace-scoped JWT for the source workspace.
          *     Target workspace key is provided in the request body (SecretBox-encrypted with session key).
          *
-         *     Copies:
-         *     - Document metadata (title, doc_date, shared status, etc.)
-         *     - MinIO encrypted files (downloaded to server memory, re-encrypted, uploaded)
-         *     - Qdrant vectors (with updated doc_ext_id and chunk_ext_id references)
+         *     ``items`` is a flat, heterogeneous list of external IDs; the prefix selects
+         *     what is copied, and **exactly** the listed items are copied — nothing rides
+         *     along:
+         *
+         *     - ``doc-`` document — row + MinIO files + Qdrant vectors, all re-encrypted
+         *       with the target workspace key. Chunk external IDs are preserved.
+         *     - ``tag-`` tag — merged into a same-named tag already in the target if there
+         *       is one, otherwise created. A parent tag that is not in the target flattens
+         *       the copy to a root tag.
+         *     - ``dtj-`` doctag — requires BOTH its document (selected in the same request)
+         *       and its tag (selected, or already present by name) in the target; RLS makes
+         *       any other combination impossible. Fails with a reason otherwise.
+         *     - ``fct-`` fact — content, date span, timezone and citations preserved; pins
+         *       are not (a pin is the pinning account's own state).
+         *     - ``con-`` chat — conversation + every message, with the parent/child tree
+         *       and the encrypted ``tools`` blob rebuilt.
+         *
+         *     Facts and chats need no vector copy: both live in pointer-only collections
+         *     keyed by external ID and are indexed on write / by the lazy backfill.
+         *
+         *     ``created_by`` is NOT preserved. Every content table's RLS ``WITH CHECK``
+         *     forces it to the copying user, so copies are attributed to whoever ran the
+         *     copy, never to the original author.
+         *
+         *     Each item is copied in its own savepoint, so one failure does not abort the
+         *     batch; per-item outcomes are in ``results``.
          */
         post: operations['copy_workspace_data'];
         delete?: never;
@@ -930,28 +952,6 @@ interface paths {
         patch: operations['update_workspace'];
         trace?: never;
     };
-    '/v1/workspace/{workspace_ext_id}/chronology': {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        /**
-         * Get Workspace Chronology
-         * @description Return the last-generated chronology for a workspace.
-         *
-         *     Returns all-null fields when no chronology has been generated yet.
-         */
-        get: operations['get_workspace_chronology'];
-        put?: never;
-        post?: never;
-        delete?: never;
-        options?: never;
-        head?: never;
-        patch?: never;
-        trace?: never;
-    };
     '/v1/document/list': {
         parameters: {
             query?: never;
@@ -1345,30 +1345,6 @@ interface paths {
         patch?: never;
         trace?: never;
     };
-    '/v1/document/chronology': {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        get?: never;
-        put?: never;
-        /**
-         * Generate Workspace Chronology
-         * @description Generate a chronological timeline of events from the specified documents.
-         *
-         *     Runs LLM analysis over the selected documents and persists the result in the
-         *     workspace_chronology table (one row per workspace, upserted on each generation).
-         *     Returns the generated events alongside metadata about when they were produced.
-         */
-        post: operations['generate_chronology'];
-        delete?: never;
-        options?: never;
-        head?: never;
-        patch?: never;
-        trace?: never;
-    };
     '/v1/conversation/list': {
         parameters: {
             query?: never;
@@ -3656,6 +3632,24 @@ interface components {
              * @default 10
              */
             AGENT_MAX_PARALLEL_TOOL_CALLS: number;
+            /**
+             * Agent Max Total Tool Calls
+             * @description Run-wide cap on tool executions across the main agent AND all nested sub-agents (deep_research / run_skill / sub_agent) in a single user query. When reached, further tool calls are refused and the agent is forced to answer from what it has gathered; at 2x the run is hard-stopped. 0 = disabled.
+             * @default 80
+             */
+            AGENT_MAX_TOTAL_TOOL_CALLS: number;
+            /**
+             * Agent Max Run Tokens
+             * @description Run-wide cap on total tokens (input+output+reasoning, provider-reported) across every LLM call in a single user query — agent iterations, nested sub-agents, and helper calls (evaluator, reranker, goal judge). When reached the agent is forced to answer from what it has gathered; at 2x the run is hard-stopped. Best-effort metering — the exact AGENT_MAX_TOTAL_TOOL_CALLS meter backs it up. 0 = disabled.
+             * @default 1500000
+             */
+            AGENT_MAX_RUN_TOKENS: number;
+            /**
+             * Agent Max Subagent Spawns
+             * @description Run-wide cap on nested sub-agent spawns (deep_research / run_skill / sub_agent) in a single user query. Past the cap, spawning tools are refused while direct tools keep working until the tool-call cap. 0 = no spawns.
+             * @default 4
+             */
+            AGENT_MAX_SUBAGENT_SPAWNS: number;
             /**
              * Agent History Char Threshold
              * @description Char threshold for conversation history injected into the agent context. Below: verbatim user/assistant pairs. Above: summarized by SummariseLLM.
@@ -3674,14 +3668,17 @@ interface components {
              *     DOCUMENT INDEX:
              *     The "Workspace Documents" table in your system prompt lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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.
              *
-             *     DOCUMENT STRATEGY:
-             *     - For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.
-             *     - For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.
-             *     - For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.
-             *     - For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.
-             *     - For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.
-             *     - For open-ended investigative queries ("find interesting things", "what's notable", "what stands out", "explore X", "what should I know about", "any findings", "anything unusual", "key insights"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.
-             *     - Never search for meta-queries like "summary", "overview", or "all documents" — search for the actual subject matter.
+             *     READING TOOL RESULTS:
+             *     Every retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example "FULL CONTENT … complete verbatim text, all 10 pages" or "DIGEST … verbatim page text is NOT part of this result"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.
+             *
+             *     DOCUMENT STRATEGY, in order:
+             *     1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.
+             *     2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.
+             *     3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.
+             *     4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.
+             *     5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.
+             *     6. Open-ended investigative queries ("find interesting things", "what's notable", "what stands out", "explore X", "what should I know about", "any findings", "anything unusual", "key insights"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.
+             *     7. Never search for meta-queries like "summary", "overview", or "all documents" — search for the actual subject matter.
              *
              *     FORMATTING:
              *     - 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).
@@ -3692,14 +3689,14 @@ interface components {
              *     - Bold text for critical conclusions or decision points
              *
              *     TOOL CALLING:
-             *     - Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.
+             *     - Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.
              *     - 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.
-             *     3. NEVER repeat a tool call with the same arguments.
+             *     3. NEVER repeat a tool call with the same arguments, and never re-retrieve material you already hold — the caption on each result tells you what that is.
              *     4. Use targeted queries and narrow page ranges per retrieval call.
              *     5. Stop when you have sufficient evidence — do not over-research.
              */
@@ -3893,8 +3890,11 @@ interface components {
              *       "AGENT_MAX_ITERATIONS": 20,
              *       "AGENT_TURN_CREDIT_BUDGET": 50,
              *       "AGENT_MAX_PARALLEL_TOOL_CALLS": 10,
+             *       "AGENT_MAX_TOTAL_TOOL_CALLS": 80,
+             *       "AGENT_MAX_RUN_TOKENS": 1500000,
+             *       "AGENT_MAX_SUBAGENT_SPAWNS": 4,
              *       "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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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- For open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\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- Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.\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."
+             *       "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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. 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- Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.\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, and never re-retrieve material you already hold — the caption on each result tells you what that is.\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'];
@@ -4250,7 +4250,7 @@ interface components {
             type: 'arbi.error';
             /**
              * Code
-             * @description Error code, e.g. 'QUOTA_EXCEEDED'
+             * @description Error code, e.g. 'QUOTA_EXCEEDED' (billing — opens upgrade modal) or 'RUN_BUDGET_EXCEEDED' (per-run safety cap — generic error display).
              */
             code: string;
             /**
@@ -4286,6 +4286,11 @@ interface components {
          *     field) while ours reads it. The item itself stays byte-for-byte standard.
          */
         ArbiItemMeta: {
+            /**
+             * Step
+             * @description Which lifecycle moment this item IS — stated, not inferred. A Responses item type (message / function_call / reasoning) is too coarse for the trace: three different reasoning items are the goal, the plan and a goal check, and the answer is a `message` item that is nonetheless a trace row. Clients previously sniffed `label` prefixes to tell them apart, which broke the moment a label was reworded or localised. Absent on plain tool calls (they carry `detail`) and on narration messages (which are body text, not a step).
+             */
+            step?: ('goal' | 'skill' | 'interjection' | 'planning' | 'tool_progress' | 'goal_progress' | 'answering' | 'evaluation') | null;
             /**
              * Label
              * @description Human display label. Backend-owned.
@@ -4645,11 +4650,6 @@ interface components {
         } & {
             [key: string]: unknown;
         };
-        /** ChronologyRequest */
-        ChronologyRequest: {
-            /** Doc Ext Ids */
-            doc_ext_ids: string[];
-        };
         /** Chunk */
         Chunk: {
             metadata: components['schemas']['ChunkMetadata'];
@@ -5349,7 +5349,15 @@ interface components {
             /** Title */
             title: string;
         };
-        /** CopyDocumentResult */
+        /**
+         * CopyDocumentResult
+         * @description Outcome of copying ONE selected item.
+         *
+         *     Named for documents because that is all ``/workspace/copy`` used to move;
+         *     the field names are kept so existing clients keep parsing the response.
+         *     ``source_doc_ext_id`` / ``new_doc_ext_id`` carry the source and new external
+         *     ID of whatever ``kind`` the item is.
+         */
         CopyDocumentResult: {
             /** Source Doc Ext Id */
             source_doc_ext_id: string;
@@ -5359,7 +5367,17 @@ interface components {
             new_doc_ext_id?: string | null;
             /** Error */
             error?: string | null;
+            /** @default document */
+            kind: components['schemas']['CopyItemKind'];
+            /** Warning */
+            warning?: string | null;
         };
+        /**
+         * CopyItemKind
+         * @description Which entity a copy result refers to — derived from the ext-id prefix.
+         * @enum {string}
+         */
+        CopyItemKind: 'document' | 'tag' | 'doctag' | 'fact' | 'chat' | 'unknown';
         /** CopyRequest */
         CopyRequest: {
             /** Target Workspace Ext Id */
@@ -5371,7 +5389,7 @@ interface components {
             target_workspace_key: string;
             /**
              * Items
-             * @description List of document external IDs to copy (e.g., ['doc-a1b2c3d4', 'doc-e5f6g7h8'])
+             * @description External IDs to copy. Heterogeneous: documents (doc-), tags (tag-), doctags (dtj-), facts (fct-) and chats (con-) may be mixed in one call — the server dispatches on the prefix and copies them in dependency order (tags → documents → doctags/facts → chats). Selection is exact: nothing is copied that was not listed.
              */
             items: string[];
         };
@@ -5384,6 +5402,18 @@ interface components {
              * @default 0
              */
             documents_copied: number;
+            /**
+             * Items Copied
+             * @default 0
+             */
+            items_copied: number;
+            /**
+             * Copied By Kind
+             * @default {}
+             */
+            copied_by_kind: {
+                [key: string]: number;
+            };
             /**
              * Results
              * @default []
@@ -5881,6 +5911,8 @@ interface components {
             /** Note */
             note?: string | null;
             citations?: components['schemas']['CitationSources'] | null;
+            /** External Id */
+            external_id: string;
             /** Doc Ext Id */
             doc_ext_id: string;
             /** Tag Ext Id */
@@ -6292,17 +6324,6 @@ interface components {
             /** Message */
             message: string;
         };
-        /**
-         * EvaluationDetail
-         * @description Detail for an evaluation learning entry.
-         */
-        EvaluationDetail: {
-            /**
-             * Statement
-             * @description Citation/finding statement
-             */
-            statement: string;
-        };
         /** EvaluatorLLMConfig */
         EvaluatorLLMConfig: {
             /**
@@ -9491,8 +9512,6 @@ interface components {
             detail_run_code?: components['schemas']['RunCodeDetail'] | null;
             detail_create_artifact?: components['schemas']['CreateArtifactDetail'] | null;
             detail_ask_user?: components['schemas']['AskUserDetail'] | null;
-            detail_evaluation?: components['schemas']['EvaluationDetail'] | null;
-            detail_tool_progress?: components['schemas']['ToolProgressDetail'] | null;
             detail_goal_progress?: components['schemas']['GoalProgressDetail'] | null;
         };
         /**
@@ -10493,22 +10512,6 @@ interface components {
             /** @description Aggregate usage across all LLM calls in the request */
             all_llm_calls?: components['schemas']['AllLlmCallsAggregate'] | null;
         };
-        /**
-         * ToolProgressDetail
-         * @description Detail for a tool progress update.
-         */
-        ToolProgressDetail: {
-            /**
-             * Tool
-             * @description Tool name
-             */
-            tool: string;
-            /**
-             * Message
-             * @description Progress message
-             */
-            message: string;
-        };
         /**
          * TraceTool
          * @description Execution trace tool that captures the full execution history of a request.
@@ -11020,11 +11023,6 @@ interface components {
              * @default false
              */
             show_skills: boolean;
-            /**
-             * Show Chronology
-             * @default false
-             */
-            show_chronology: boolean;
             /**
              * Show Pa Mode
              * @default false
@@ -11148,8 +11146,6 @@ interface components {
             show_templates?: boolean | null;
             /** Show Skills */
             show_skills?: boolean | null;
-            /** Show Chronology */
-            show_chronology?: boolean | null;
             /** Show Pa Mode */
             show_pa_mode?: boolean | null;
             /** Show Conversation Search */
@@ -11358,23 +11354,6 @@ interface components {
             auth?: components['schemas']['AuthMessage'] | null;
             send_message?: components['schemas']['SendMessageRequest'] | null;
         };
-        /**
-         * WorkspaceChronologyOut
-         * @description API response for both POST /v1/document/chronology and GET /v1/workspace/chronology.
-         *
-         *     For POST: all fields are always populated (generation just happened).
-         *     For GET: all fields are null when no chronology has been generated yet.
-         */
-        WorkspaceChronologyOut: {
-            /** Events */
-            events?: {
-                [key: string]: unknown;
-            }[] | null;
-            /** Generated At */
-            generated_at?: string | null;
-            /** Doc Count */
-            doc_count?: number | null;
-        };
         /** WorkspaceCreateRequest */
         WorkspaceCreateRequest: {
             /** Name */
@@ -12935,37 +12914,6 @@ interface operations {
             };
         };
     };
-    get_workspace_chronology: {
-        parameters: {
-            query?: never;
-            header?: never;
-            path: {
-                workspace_ext_id: string;
-            };
-            cookie?: never;
-        };
-        requestBody?: never;
-        responses: {
-            /** @description Successful Response */
-            200: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['WorkspaceChronologyOut'];
-                };
-            };
-            /** @description Validation Error */
-            422: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['HTTPValidationError'];
-                };
-            };
-        };
-    };
     list_documents: {
         parameters: {
             query?: {
@@ -13575,39 +13523,6 @@ interface operations {
             };
         };
     };
-    generate_chronology: {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        requestBody: {
-            content: {
-                'application/json': components['schemas']['ChronologyRequest'];
-            };
-        };
-        responses: {
-            /** @description Successful Response */
-            200: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['WorkspaceChronologyOut'];
-                };
-            };
-            /** @description Validation Error */
-            422: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    'application/json': components['schemas']['HTTPValidationError'];
-                };
-            };
-        };
-    };
     list_conversations: {
         parameters: {
             query?: never;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arbidocs/client",
-  "version": "0.3.146",
+  "version": "0.3.147",
   "description": "TypeScript SDK for the ARBI API — zero-knowledge auth, E2E encryption, and type-safe REST client",
   "type": "module",
   "main": "dist/index.cjs",