@deepraxis/sdk 0.1.1-dev.daf2585 → 0.1.1-dev.dc553d7

package/dist/generated/sdk.gen.js

@@ -971,6 +971,20 @@ export const browserViewerHeartbeat = (options) => (options.client ?? client).po
         ...options.headers
     }
 });
+/**
+ * 读取会话只读画面帧
+ *
+ * 读取会话的一张只读画面帧（JPEG 字节）。创建者可读，同组织其他成员只在该会话声明为组织可见时可读；其余情况一律返回 404 SESSION_NOT_FOUND，不提示会话是否存在。响应体没有任何可控制浏览器的凭据，且不接受任何动作参数。
+ */
+export const browserGetSessionFrame = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'BrowserBearer',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/browser/v1/sessions/{sessionId}/frame',
+    ...options
+});
 /**
  * 列出浏览器上下文
  *
@@ -1099,6 +1113,20 @@ export const browserStreamSession = (options) => (options.client ?? client).sse.
     url: '/browser/v1/sessions/{sessionId}/stream',
     ...options
 });
+/**
+ * 订阅会话只读画面
+ *
+ * SSE：只推送只读画面帧，event 为 frame 或 end，data 为帧的 JSON 或 null；帧 data 是 JPEG 的 base64 编码，ts 是浏览器产生该帧的时刻（epoch 毫秒），约每秒最多 5 帧。评论 ping 每 15 秒一次，end 后关闭。这条通道与 /sessions/{sessionId}/stream 相互独立：它的消息只含画面，绝不含 wsUrl、signingKey、connectUrl、debuggerUrl、debuggerFullscreenUrl。创建者可订阅，同组织其他成员只在该会话声明为组织可见时可订阅；其余情况一律返回 404 SESSION_NOT_FOUND。
+ */
+export const browserStreamSessionFrames = (options) => (options.client ?? client).sse.get({
+    security: [{
+            key: 'BrowserBearer',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/browser/v1/sessions/{sessionId}/frames',
+    ...options
+});
 /**
  * 读取 Selenium 不支持提示
  *
@@ -7546,77 +7574,59 @@ export const devopsTestReportsUpload = (options) => (options.client ?? client).p
     }
 });
 /**
- * List knowledge bases
+ * List projects
  *
- * Lists knowledge bases visible to the caller, newest first by default. Use last_id as after to read the next page; for example, ?limit=20.
+ * List the delivery projects this organization has, newest first, with each project's repository binding and settings. Call this first when you do not already hold a project id: every other operation in this domain is addressed by one. A project from another organization is never listed, so an empty page means this organization has none rather than that they are hidden. The order is by creation time descending; follow nextPageToken until it is empty to see them all.
  */
-export const knowledgeListVectorStores = (options) => (options?.client ?? client).get({
+export const devopsProjectsList = (options) => (options?.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores',
+    url: '/devops/v1/projects',
     ...options
 });
 /**
- * Create knowledge base
- *
- * Create a knowledge base, optionally starting ingestion of uploaded file_ids in the same call; no separate attachment or batch is needed for those files. Use the returned id with vectorStores.files.retrieve to poll each attachment until completed, failed or cancelled; store status=completed alone does not mean every file succeeded. PDF files accept up to 536870912 bytes (512 MiB), while other formats accept up to 52428800 bytes (50 MiB), constrained by Router conversion; every file is limited to 5000000 estimated tokens; each account holds up to 100 active/nondeleted stores. Minimal body: {"name":"Refund policies"}.
- */
-export const knowledgeCreateVectorStore = (options) => (options.client ?? client).post({
-    security: [{
-            key: 'knowledge-bearerAuth',
-            scheme: 'bearer',
-            type: 'http'
-        }],
-    url: '/knowledge/v1/vector_stores',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
-});
-/**
- * Delete knowledge base
+ * Retrieve a project
  *
- * Remove a knowledge base from active use while keeping a recovery window. Unlike OpenAI vector stores, native DELETE returns the store with status=deleting and ISO purge_at, retains it for 7 days and is idempotent on repeat. Retrieve remains 200; object operations return 409. Use restore before purge_at to recover it, or purge to remove it irreversibly.
+ * Read one project by id: its repository binding, its release schedule and its gate settings. Use it to confirm a project's configuration before releasing into it, and to learn which environment a promotion order starts from. A project that was deleted, or that belongs to another organization, answers PROJECT_NOT_FOUND — the two are indistinguishable on purpose, so the answer never tells you whether a project exists elsewhere.
  */
-export const knowledgeDeleteVectorStore = (options) => (options.client ?? client).delete({
+export const devopsProjectsGet = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}',
+    url: '/devops/v1/projects/{id}',
     ...options
 });
 /**
- * Retrieve knowledge base
+ * List releases
  *
- * Retrieves a knowledge base using an id returned by create or list. Add ?expand=files to include the first page of attached files. Soft-deleted stores remain readable with status=deleting until purged.
+ * List the project's releases, newest first. Use it to find the release a promotion should carry, or to see what has been released recently and whether any of it was abandoned. The list carries the render state and the abandoned flag, so a caller can skip a release that is still rendering or that was withdrawn without reading each one. Neither filter nor orderBy is accepted on this collection yet; a request that sends one is refused rather than silently ignored.
  */
-export const knowledgeRetrieveVectorStore = (options) => (options.client ?? client).get({
+export const devopsReleasesList = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}',
+    url: '/devops/v1/projects/{project}/releases',
     ...options
 });
 /**
- * Update knowledge base
+ * Create a release
  *
- * Updates an active knowledge base using its returned id. Omitted fields stay unchanged; metadata replaces the whole map. Example body: {"name":"Refund policies"}.
+ * Create a release: an immutable snapshot of what will be deployed, named and fingerprinted once so later promotions can be compared against it. Send commit to release a commit as it stands, or base plus picks to build a patch release on a release that is already in production; the two shapes are exclusive and the patch shape is refused with PATCH_NOT_ELIGIBLE when the picks do not qualify. Rendering starts immediately and the answer reports its state; a promotion refuses a release that is still rendering with RELEASE_NOT_READY rather than deploying half of it. Set validateOnly to see the plan and the refusals without writing a release, and requestId to make a retry of the same call answer the first release instead of creating a second.
  */
-export const knowledgeUpdateVectorStore = (options) => (options.client ?? client).post({
+export const devopsReleasesCreate = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}',
+    url: '/devops/v1/projects/{project}/releases',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -7624,49 +7634,49 @@ export const knowledgeUpdateVectorStore = (options) => (options.client ?? client
     }
 });
 /**
- * Search knowledge base
+ * Retrieve a release
  *
- * Search ingested text to answer a question or find supporting passages. Native results contain one chunk each, so file_id can repeat; max_num_results counts chunks (1–50, default 10), while the compatible URL groups results by file. Unlike OpenAI vector stores, next_page is always null even when has_more is true. Only completed attachments are searchable. For keyword-only retrieval set ranking_options.hybrid_search to {"embedding_weight":0,"text_weight":1}; omit rewrite_query or set it to false to avoid query rewriting. Unlike OpenAI, ranker auto does not rerank; only default-2024-11-15 requests reranking. Set praxis.explain=true to inspect scores and use returned content[].chunk_id to retrieve a segment.
+ * Read one release in full: the commit it carries, the targets and source digests it was rendered from, which environments have verified it, and where it currently runs. Call it before promoting to confirm the release is not abandoned and that its render succeeded, and after deploying to learn which environments already hold it so the same release is not promoted twice. A release from another organization answers RELEASE_NOT_FOUND, which is also the answer for one that never existed.
  */
-export const knowledgeSearchVectorStore = (options) => (options.client ?? client).post({
+export const devopsReleasesGet = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/search',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/devops/v1/releases/{id}',
+    ...options
 });
 /**
- * List files
+ * Abandon a release
  *
- * Lists attached files and their ingestion status, newest attachment first by default. Use last_id as after to continue; ?filter=failed selects files that can be retried.
+ * Withdraw a release so it can no longer be promoted: a later promotion of it is refused with RELEASE_ABANDONED. Use it when a release was created by mistake or has been superseded, and record why in reason — the reason is stored on the release as the attribution of the act. A release with a promotion still in flight cannot be abandoned, because the queue is mid-flight on it; cancel that promotion first, which is the door for stopping a deployment. Abandoning is one-way: a withdrawn release is never un-abandoned, and a new release is created instead.
  */
-export const knowledgeListFiles = (options) => (options.client ?? client).get({
+export const devopsReleasesAbandon = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files',
-    ...options
+    url: '/devops/v1/releases/{id}:abandon',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Add file
+ * Create a promotion
  *
- * Attach an uploaded File for asynchronous ingestion, then poll this attachment until status is completed, failed or cancelled before searching. PDF files accept up to 536870912 bytes (512 MiB), while other formats accept up to 52428800 bytes (50 MiB), constrained by Router conversion; every file is limited to 5000000 estimated tokens; chunk sizes use estimated tokens rather than a model tokenizer. Text, Markdown, CSV, JSON, HTML, PDF, DOCX, PPTX, XLSX and PNG/JPEG/GIF/WebP images can be extracted; audio and video uploads are not knowledge documents. Images may yield generated descriptions rather than verbatim OCR. auto chunking resolves to static 800/400; explicit sizes are 100–4096 with overlap at most half the size. Each store holds at most 10000 attached files. Reattaching the same file returns its existing record without applying new attributes or chunking; inspect last_error after failure.
+ * Promote a release into one environment: this is the operation that actually schedules a deployment. Name the release and the environment; path is regular for an ordinary promotion, patch to carry a patch release, targeted to deploy only the targets you list, and rollback to return the environment to an earlier release. The service reads the environment's promotion order and refuses when an upstream environment has not verified this release yet, unless a bypass carries the authorization for that gate. An environment takes one promotion at a time, so a create while another is running is queued behind it rather than refused. Set validateOnly to read the plan and its refusals — layers, skipped targets, pending migrations, missing configuration keys — without scheduling anything, which is the safe way to find out what a promotion will do.
  */
-export const knowledgeAttachFile = (options) => (options.client ?? client).post({
+export const devopsPromotionsCreate = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files',
+    url: '/devops/v1/promotions',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -7674,45 +7684,45 @@ export const knowledgeAttachFile = (options) => (options.client ?? client).post(
     }
 });
 /**
- * Remove file
+ * List promotions
  *
- * Removes the file from search immediately; does not delete the original File.
+ * List the project's promotions, newest first, across every environment. Use it to see what is queued, what is observing, and what finished recently, without reading each environment separately. A promotion in a terminal state stays in this list, which is how a caller tells "never promoted" apart from "promoted and then rolled back". Neither filter nor orderBy is accepted yet, so page through with pageToken instead of narrowing the query.
  */
-export const knowledgeRemoveFile = (options) => (options.client ?? client).delete({
+export const devopsPromotionsList = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}',
+    url: '/devops/v1/projects/{project}/promotions',
     ...options
 });
 /**
- * Retrieve file
+ * Retrieve a promotion
  *
- * Retrieves an attached file using the id returned by attachment or file listing. Poll this operation until status leaves in_progress to observe the ingestion outcome.
+ * Read one promotion: its state, its approval, its plan, and the failure that stopped it when there is one. Poll this after creating a promotion to follow it to a terminal state, or read it to find out why a deployment stopped — failure.cause tells plan refusal apart from a failed deploy, and executor names the runs involved. Pass expand=rollouts to receive the per-target rollouts in the same answer instead of listing them separately. state observing means the environment is deployed and the observation window is running, so the promotion is not finished and conclude is still to come.
  */
-export const knowledgeRetrieveFile = (options) => (options.client ?? client).get({
+export const devopsPromotionsGet = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}',
+    url: '/devops/v1/promotions/{id}',
     ...options
 });
 /**
- * Update file attributes
+ * Approve or reject a promotion
  *
- * Replaces search-filter attributes of an existing attachment without reingesting its content. Use an attached file id. Example body: {"attributes":{"category":"refund"}}; null clears the attributes.
+ * Answer the approval an environment asked for: send approved true to let the promotion proceed, false to reject it and end it in approval_rejected. This is the environment-level gate an environment with requireApproval raises, not the per-rollout approval. Comment records the reasoning next to the decision, which is what a later reader sees instead of the bare verdict. The call is refused with PROMOTION_NOT_AWAITING_APPROVAL when the promotion is not waiting for one, so a stale approval cannot restart something that already finished. Approving is attributed to the credential that sends it.
  */
-export const knowledgeUpdateFile = (options) => (options.client ?? client).post({
+export const devopsPromotionsApprove = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}',
+    url: '/devops/v1/promotions/{id}:approve',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -7720,189 +7730,201 @@ export const knowledgeUpdateFile = (options) => (options.client ?? client).post(
     }
 });
 /**
- * Read extracted content
+ * Cancel a promotion
  *
- * Extracted text chunks may overlap. Image content can be a generated description rather than verbatim OCR.
+ * Stop a promotion that has not finished, moving it through cancelling to cancelled and stopping the deploys it had scheduled. Use it to halt a deployment that is failing or that should no longer continue; reason is recorded as the attribution of the stop. Cancelling does not undo what already deployed: an environment whose targets were written keeps those targets, and returning them to an earlier release is a separate rollback promotion. A promotion that already reached a terminal state is refused with PROMOTION_ALREADY_FINISHED rather than silently ignored.
  */
-export const knowledgeRetrieveFileContent = (options) => (options.client ?? client).get({
+export const devopsPromotionsCancel = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}/content',
-    ...options
+    url: '/devops/v1/promotions/{id}:cancel',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Create file batch
+ * Retry a promotion
  *
- * Attaches existing Files as a batch for asynchronous ingestion. Supply exactly one of file_ids or files; files allows per-file settings. Existing attachments are reused. Read the returned batch id to monitor status.
+ * Continue a promotion that stopped part-way, such as one in halted where some targets succeeded and others failed. The retry re-runs the targets that did not succeed and leaves the ones that did alone, so a partially deployed environment is completed rather than redeployed from the start. A promotion that is still running is refused, and so is one that already reached a terminal state; read the promotion first and retry only a halted or errored one. The retry is attributed to the credential that sends it and is recorded on the promotion.
  */
-export const knowledgeCreateFileBatch = (options) => (options.client ?? client).post({
+export const devopsPromotionsRetry = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/devops/v1/promotions/{id}:retry',
+    ...options
 });
 /**
- * Retrieve file batch
+ * Conclude an observation
  *
- * Retrieves a batch created in this knowledge base, including current status and file counts. Use the batch id returned by batch creation to monitor ingestion.
+ * Record the verdict on a promotion that is observing: send keep to accept the deployment as the environment's new state, or rollback to return the environment to the release it held before. This is the decision the observation window exists for, so a promotion in observing state stays open until it is concluded; reason is stored as the attribution. Concluding with rollback schedules the return, it does not merely label the promotion. A promotion that is not observing is refused with PROMOTION_NOT_OBSERVING, which is how a caller tells "already concluded" apart from a call that had no effect.
  */
-export const knowledgeRetrieveFileBatch = (options) => (options.client ?? client).get({
+export const devopsPromotionsConclude = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches/{batch_id}',
-    ...options
+    url: '/devops/v1/promotions/{id}:conclude',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Cancel file batch
+ * List a promotion's rollouts
  *
- * Cancels only in-progress batches and pending files. Completed, failed and cancelled batches return unchanged (200, idempotent).
+ * List the per-target rollouts of one promotion: which target each is deploying, which layer it waits on, and where in its phases it has got to. Call it when a promotion is halted or failed to find the target that stopped, since the promotion's own state summarises what the rollouts show one by one. A promotion with nothing to deploy answers an empty page rather than a refusal. Neither filter nor orderBy is accepted here, and the rollouts come in the order the plan laid them out.
  */
-export const knowledgeCancelFileBatch = (options) => (options.client ?? client).post({
+export const devopsRolloutsList = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches/{batch_id}/cancel',
+    url: '/devops/v1/promotions/{promotion}/rollouts',
     ...options
 });
 /**
- * List batch files
+ * Retrieve a rollout
  *
- * Lists files still attached from the identified batch, newest attachment first by default. Use the batch creation id and ?filter=failed to inspect failures; last_id is the next after cursor.
+ * Read one rollout in full: its phases and the jobs inside them, each job's most recent attempt, the checkpoint it was deploying from, and why it failed when it did. This is the level that names the failing step — a promotion tells you that a target failed, a rollout tells you which job run did and what it reported. Use logFileId or a job run's eventLogPath to reach the logs that step produced. A rollout from another organization answers ROLLOUT_NOT_FOUND, the same answer as one that never existed.
  */
-export const knowledgeListBatchFiles = (options) => (options.client ?? client).get({
+export const devopsRolloutsGet = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches/{batch_id}/files',
+    url: '/devops/v1/rollouts/{id}',
     ...options
 });
 /**
- * Restore knowledge base
+ * List environments
  *
- * Restores a deleting store within 7 days. Active stores return 409 VECTOR_STORE_INVALID_STATE; absent stores return 404. Empty body is allowed.
+ * List the project's environments in promotion order: development first, production last. order is the promotion sequence, so the environment before the one you are promoting into is the one that must have verified the release first. Each entry carries its tier, whether it requires approval, and whether its queue is idle or busy; a busy queue names the promotion holding it and how many wait behind. This collection is not paged: a project has few environments and the whole ordered list is the answer.
  */
-export const knowledgeRestoreVectorStore = (options) => (options.client ?? client).post({
+export const devopsEnvironmentsList = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/restore',
+    url: '/devops/v1/projects/{project}/environments',
     ...options
 });
 /**
- * Permanently purge knowledge base
+ * List environment checkpoints
  *
- * Immediately and irreversibly clears a deleting store using the retention cleanup path. Active stores return 409; absent stores return 404. Empty body is allowed.
+ * List where each target of an environment currently stands: the release and commit deployed to it, the promotion that put it there, and how far behind the default branch that commit is. Read it to answer "what is running in production right now" and to tell a promotion that will change something apart from one that will skip every target as unchanged. behindMain counts commits on the default branch that the deployed commit does not have, so zero means the environment carries the current branch head. Targets that were never deployed to have no checkpoints until something deploys to them.
  */
-export const knowledgePurgeVectorStore = (options) => (options.client ?? client).post({
+export const devopsEnvironmentsCheckpointsList = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/purge',
+    url: '/devops/v1/environments/{id}/checkpoints',
     ...options
 });
 /**
- * Retry failed file
+ * List targets
  *
- * Retries only failed files; other states return 409 FILE_INVALID_STATE. Retry after failure has not yet been observed in the documented run.
+ * List what the project deploys — one target per deployable path in the repository, with its kind, its destination and the targets it depends on. Targets are discovered from the code, not entered by hand, so this list is the service's reading of the repository rather than a configuration you maintain here. A project whose catalog has never been read has it read on the first call, at the default branch's head, so the first answer is already the catalog instead of an empty page. Archived targets, which the repository no longer deploys, are left out.
  */
-export const knowledgeRetryFile = (options) => (options.client ?? client).post({
+export const devopsTargetsList = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}/retry',
+    url: '/devops/v1/projects/{project}/targets',
     ...options
 });
 /**
- * List file segments
+ * Refresh the target catalog
  *
- * Lists the stored chunks of an attached file, ordered by increasing segment index by default. Use the attachment id and last_id as after to continue; returned chunk ids can be retrieved individually.
+ * Re-read the repository at a commit and answer the deployment targets it implies, recording what was found. Call it after adding or removing a deployable service so later promotions see the current layout; omit commit to read the default branch's head, or name one to read that commit. The answer includes the dependency graph and any cycles in it, and a cycle is reported rather than refused, matching how the deploy pipeline treats one. This is a read of the repository that also remembers what it read, so it is safe to call again; nothing is deployed by it.
  */
-export const knowledgeListSegments = (options) => (options.client ?? client).get({
+export const devopsTargetsRefresh = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}/segments',
-    ...options
+    url: '/devops/v1/projects/{project}/targets:refresh',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Retrieve segment
+ * List flags
  *
- * Retrieves one chunk and its term statistics. Take chunk_id from segment listing or native search content; the chunk must belong to this knowledge base.
+ * List the project's flags with their per-environment configuration, newest first. Use it to find a flag by key when code names one, and to review the flags of a project — the entries carry lifecycle, staleness, the observation deadline and the removal ticket, which is what an expiry review reads. filter accepts exactly one term, lifecycle=archived, to list the archived flags instead of the live ones; any other filter or orderBy is refused rather than ignored. totalSize is answered on the first page only.
  */
-export const knowledgeRetrieveSegment = (options) => (options.client ?? client).get({
+export const devopsFlagsList = (options) => (options.client ?? client).get({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/segments/{chunk_id}',
+    url: '/devops/v1/projects/{project}/flags',
     ...options
 });
 /**
- * List events
+ * Create a flag
  *
- * Reads events for this knowledge base in increasing sequence order, including while soft-deleted. Pass next_seq as after_seq to continue; null next_seq marks the current end. Example: ?after_seq=0&limit=20.
+ * Create a feature flag in a project: its key, what kind of flag it is, the values it can serve, and which variation is served when it is off. The key is what code names, so it is unique per project and a key already in use is refused with FLAG_KEY_TAKEN rather than reused — an archived flag keeps its key. owner, observeUntil and removalTicket carry the flag's lifecycle: a release or experiment flag expects an observation deadline and the ticket that removes it, and a flag missing them is refused with FLAG_LIFECYCLE_INCOMPLETE. A new flag starts with every environment off, so creating one changes no runtime behaviour; turn an environment on with the environment update.
  */
-export const knowledgeListEvents = (options) => (options.client ?? client).get({
+export const devopsFlagsCreate = (options) => (options.client ?? client).post({
     security: [{
-            key: 'knowledge-bearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/knowledge/v1/vector_stores/{vector_store_id}/events',
-    ...options
+    url: '/devops/v1/projects/{project}/flags',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * List libraries
+ * Retrieve a flag
  *
- * Read a caller-owned library’s current settings, usage and lifecycle status. A deleting library remains readable; missing, foreign or purged libraries return LIBRARY_NOT_FOUND.
+ * Read one flag in full: every environment's configuration, the rules and rollouts each environment serves, the flag's lifecycle, and where code references its key as of the last scan. Call it before changing an environment so you can send the version you read, and after a release to confirm the flag reached the state you expected. An archived flag is still readable here — that is how its key and history stay answerable after it stopped evaluating. codeRefs.count tells you how much code still names the key, which is what decides whether removing the flag is safe.
  */
-export const mediaListLibraries = (options) => (options?.client ?? client).get({
+export const devopsFlagsGet = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries',
+    url: '/devops/v1/flags/{id}',
     ...options
 });
 /**
- * Create library
+ * Update a flag
  *
- * Create a library owned by the caller with a name, optional labels and understanding settings. Understanding is enabled by default; the returned id is used for subsequent asset operations.
+ * Change a flag's metadata — its name, description, owner, observation deadline, removal ticket or tags — without touching what any environment serves. Send the fields to change inside flag and name them in updateMask; a field present in flag but absent from the mask is left alone, and a mask naming a field this operation cannot change is refused rather than ignored. Sending null clears a nullable field such as observeUntil. Served values are not changed here: use the environment update for what an environment serves, which is versioned and checked. An archived flag cannot be updated.
  */
-export const mediaCreateLibrary = (options) => (options.client ?? client).post({
+export const devopsFlagsUpdate = (options) => (options.client ?? client).patch({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries',
+    url: '/devops/v1/flags/{id}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -7910,17 +7932,17 @@ export const mediaCreateLibrary = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Create frame URLs
+ * Update a flag's environment
  *
- * Media creates JPEG frame URLs for inspecting one or more moments in a video without downloading the original. Obtain library_id from libraries and asset_id plus duration from assets. Send 1–20 integer microsecond timestamps strictly below duration, for example {"at_micros":[0,1000000],"width":640}. Only video assets are supported; audio and images return INVALID_PARAMS. Width defaults to 640 and accepts 160, 320 or 640. This read operation does not store a new asset or rerun understanding. Fetch each returned URL to obtain the frame; delivery usage follows media pricing. Authenticated links expire after 300 seconds; upload links remain public and permanent. Reissue expired links. Foreign libraries and assets return 404 without revealing their existence.
+ * Change what one environment of a flag serves: whether it is on, its targeting rules, its prerequisite flags, its individually targeted keys, its fallthrough, and the progressive rollout it runs. This is the write that changes runtime behaviour, so it is versioned: send the version you read and a change based on a stale version is refused with FLAG_VERSION_CONFLICT instead of silently overwriting someone else's edit. comment records why the configuration changed, next to the change itself. Targets whose keys are not deployed yet are refused with FLAG_CODE_NOT_DEPLOYED, because serving a variation the running code cannot name would fail at evaluation time.
  */
-export const mediaCreateFrameUrls = (options) => (options.client ?? client).post({
+export const devopsFlagsUpdateEnvironment = (options) => (options.client ?? client).patch({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/frames',
+    url: '/devops/v1/flags/{id}/environments/{environment}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -7928,45 +7950,49 @@ export const mediaCreateFrameUrls = (options) => (options.client ?? client).post
     }
 });
 /**
- * Delete library
+ * Conclude a flag
  *
- * Restore a deleting library before its purge_at deadline. The library becomes active again and deleted_at and purge_at are cleared; expired or non-deleting libraries cannot be restored.
+ * Record the decision a temporary flag's observation window ended with: promote makes the chosen variation the permanent behaviour and moves the flag to launched, rollback returns the environment to its off behaviour, and extend keeps observing with a new observeUntil deadline. reason is stored as the attribution of the decision. This is the act the observation flag machinery requires when the deadline arrives, so an expired flag is concluded rather than left standing. A promote or rollback finishes the flag's rollout; the code and the flag are then removed by the ticket the flag recorded, which this call does not do.
  */
-export const mediaDeleteLibrary = (options) => (options.client ?? client).delete({
+export const devopsFlagsConclude = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}',
-    ...options
+    url: '/devops/v1/flags/{id}:conclude',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Get library
+ * Archive a flag
  *
- * Update an active library’s supplied settings. Labels replace the complete map; understanding settings and model roles merge with current values. Changing the embedding model is rejected while assets exist.
+ * Archive a flag once it is no longer needed: it stops evaluating in every environment, leaves the ordinary flag list, and keeps its key and history. Use it for a flag whose code has been removed and whose key nothing names any more; codeRefs.count on the flag is what tells you whether that is true. Archiving is the terminal lifecycle state — an archived flag is never un-archived and its key is never reused, so a flag that may come back is turned off in its environment instead. The key stays reserved, which is why a later create with the same key is refused.
  */
-export const mediaGetLibrary = (options) => (options.client ?? client).get({
+export const devopsFlagsArchive = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}',
+    url: '/devops/v1/flags/{id}:archive',
     ...options
 });
 /**
- * Update library
+ * Create a progressive rollout
  *
- * Update an active library. Set hotwords for spelling evidence in subsequent transcripts; [] disables inferred vocabulary. Transcript understanding calls the timestamped ASR, optional reference ASR and correction model through the existing metered model path. Reprocess assets to apply new settings to existing transcripts.
+ * Start a staged rollout of one variation of a flag in one environment: the steps are percentages with a hold time each, and the guard says which signals are watched and whether a bad reading pauses the rollout or rolls it back. Use it instead of turning a flag fully on, so a bad variation is caught at a small percentage. bucketBy names the context attribute that decides which bucket a caller falls into, so the same caller stays in the same bucket across steps. One progressive rollout runs per flag and environment; a second one while the first is active is refused with ROLLOUT_ALREADY_ACTIVE.
  */
-export const mediaUpdateLibrary = (options) => (options.client ?? client).patch({
+export const devopsProgressiveRolloutsCreate = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}',
+    url: '/devops/v1/progressive-rollouts',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -7974,59 +8000,63 @@ export const mediaUpdateLibrary = (options) => (options.client ?? client).patch(
     }
 });
 /**
- * Restore library
+ * Retrieve a progressive rollout
  *
- * Permanently remove a library that is already deleting, without waiting for purge_at. Its assets and related resources are removed and cannot be restored; first soft-delete an active library.
+ * Read one progressive rollout: which step it is on, how much of the audience that is, when the next step is due, and every step it has already taken with who moved it and why. Poll it to follow a rollout, and read history to find out why it paused or rolled back — a guard that fired leaves the step and the reason there. state scheduled means the first step has not started, running means it is advancing on its hold times, and rolled_back is terminal. nextStepTime is the time the current hold ends.
  */
-export const mediaRestoreLibrary = (options) => (options.client ?? client).post({
+export const devopsProgressiveRolloutsGet = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/restore',
+    url: '/devops/v1/progressive-rollouts/{id}',
     ...options
 });
 /**
- * Purge library
+ * Pause a progressive rollout
  *
- * List assets in an active library, newest first, optionally filtering by exact folder and stored resource type. Continue using next_cursor; video includes audio-only assets.
+ * Hold a running progressive rollout at its current percentage: no further step is taken until it is resumed, and the percentage already served keeps being served. Use it when a guard signal looks wrong but not wrong enough to roll back, so a person can look before the rollout advances. reason is recorded on the rollout as the attribution of the hold. Pausing a rollout that already completed or was rolled back is refused; read it first to see whether there is anything to hold.
  */
-export const mediaPurgeLibrary = (options) => (options.client ?? client).post({
+export const devopsProgressiveRolloutsPause = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/purge',
-    ...options
+    url: '/devops/v1/progressive-rollouts/{id}:pause',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * List assets
+ * Resume a progressive rollout
  *
- * Upload content into an active library and return a Cloudinary-compatible resource. Use file for a multipart file, data URI, public HTTPS URL or same-owner file identifier. Reusing public_id overwrites by default; overwrite=false returns the existing resource. Chunk uploads require both chunk headers.
+ * Continue a paused progressive rollout from the step it stopped at, restarting the hold time for the current step rather than skipping it. Use it after a pause has been looked into and the rollout is judged safe to continue. A rollout that is running already, or that finished, is refused; read it first to see whether it is paused. The resumption is attributed to the credential that sends it and recorded in the rollout's step history.
  */
-export const mediaListAssets = (options) => (options.client ?? client).get({
+export const devopsProgressiveRolloutsResume = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets',
+    url: '/devops/v1/progressive-rollouts/{id}:resume',
     ...options
 });
 /**
- * Upload asset
+ * Roll back a progressive rollout
  *
- *  For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
+ * End a progressive rollout by returning the flag's environment to the variation it served before the rollout started, so the audience that was already switched over goes back. Use it when a guard signal says the variation is bad and waiting for the next step would expose more callers. reason is recorded on the rollout as the attribution of the decision. The rollback is terminal: the rollout does not restart, and a new rollout is created if the variation should be tried again. It changes what the environment serves, not the flag's other environments.
  */
-export const mediaUploadAsset = (options) => (options.client ?? client).post({
+export const devopsProgressiveRolloutsRollback = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'devops-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets',
+    url: '/devops/v1/progressive-rollouts/{id}:rollback',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8034,17 +8064,31 @@ export const mediaUploadAsset = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Import file
+ * List knowledge bases
  *
- * Copy a File into an independent Media asset. New assets default to organization-private delivery (type=authenticated); explicitly set type=upload for public originals and derivatives. Omitting type on overwrite preserves the current type. Deleting the source File does not delete this copy. For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
+ * Lists knowledge bases visible to the caller, newest first by default. Use last_id as after to read the next page; for example, ?limit=20.
  */
-export const mediaImportAsset = (options) => (options.client ?? client).post({
+export const knowledgeListVectorStores = (options) => (options?.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets/import',
+    url: '/knowledge/v1/vector_stores',
+    ...options
+});
+/**
+ * Create knowledge base
+ *
+ * Create a knowledge base, optionally starting ingestion of uploaded file_ids in the same call; no separate attachment or batch is needed for those files. Use the returned id with vectorStores.files.retrieve to poll each attachment until completed, failed or cancelled; store status=completed alone does not mean every file succeeded. PDF files accept up to 536870912 bytes (512 MiB), while other formats accept up to 52428800 bytes (50 MiB), constrained by Router conversion; every file is limited to 5000000 estimated tokens; each account holds up to 100 active/nondeleted stores. Minimal body: {"name":"Refund policies"}.
+ */
+export const knowledgeCreateVectorStore = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'knowledge-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/knowledge/v1/vector_stores',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8052,45 +8096,45 @@ export const mediaImportAsset = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Delete asset
+ * Delete knowledge base
  *
- * Queue reprocessing of the asset’s current version and return its updated state immediately. Omit kinds to retry failed tasks and legacy source-size unsupported tasks; explicit kinds rerun applicable completed tasks and recoverable source-size unsupported tasks. Other unsupported causes remain unchanged. Replaced understandings become superseded, and processing finishes asynchronously.
+ * Remove a knowledge base from active use while keeping a recovery window. Unlike OpenAI vector stores, native DELETE returns the store with status=deleting and ISO purge_at, retains it for 7 days and is idempotent on repeat. Retrieve remains 200; object operations return 409. Use restore before purge_at to recover it, or purge to remove it irreversibly.
  */
-export const mediaDeleteAsset = (options) => (options.client ?? client).delete({
+export const knowledgeDeleteVectorStore = (options) => (options.client ?? client).delete({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets/{asset_id}',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}',
     ...options
 });
 /**
- * Get asset
+ * Retrieve knowledge base
  *
- * Update an asset’s supplied metadata fields. Tags and context replace their current collections; an empty collection clears them. Moving asset_folder or changing display_name preserves public_id and delivery URLs.
+ * Retrieves a knowledge base using an id returned by create or list. Add ?expand=files to include the first page of attached files. Soft-deleted stores remain readable with status=deleting until purged.
  */
-export const mediaGetAsset = (options) => (options.client ?? client).get({
+export const knowledgeRetrieveVectorStore = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets/{asset_id}',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}',
     ...options
 });
 /**
- * Update asset
+ * Update knowledge base
  *
- * Delete an asset from the library so it is no longer readable, searchable or deliverable. This removes the asset rather than placing it in the library’s restoration window; a missing asset returns ASSET_NOT_FOUND.
+ * Updates an active knowledge base using its returned id. Omitted fields stay unchanged; metadata replaces the whole map. Example body: {"name":"Refund policies"}.
  */
-export const mediaUpdateAsset = (options) => (options.client ?? client).patch({
+export const knowledgeUpdateVectorStore = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets/{asset_id}',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8098,17 +8142,17 @@ export const mediaUpdateAsset = (options) => (options.client ?? client).patch({
     }
 });
 /**
- * Reprocess asset
+ * Search knowledge base
  *
- *  For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
+ * Search ingested text to answer a question or find supporting passages. Native results contain one chunk each, so file_id can repeat; max_num_results counts chunks (1–50, default 10), while the compatible URL groups results by file. Unlike OpenAI vector stores, next_page is always null even when has_more is true. Only completed attachments are searchable. For keyword-only retrieval set ranking_options.hybrid_search to {"embedding_weight":0,"text_weight":1}; omit rewrite_query or set it to false to avoid query rewriting. Unlike OpenAI, ranker auto does not rerank; only default-2024-11-15 requests reranking. Set praxis.explain=true to inspect scores and use returned content[].chunk_id to retrieve a segment.
  */
-export const mediaReprocessAsset = (options) => (options.client ?? client).post({
+export const knowledgeSearchVectorStore = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/reprocess',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/search',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8116,31 +8160,31 @@ export const mediaReprocessAsset = (options) => (options.client ?? client).post(
     }
 });
 /**
- * List understandings
+ * List files
  *
- * List understanding results for an asset, ordered by creation time. Use the cursor to continue; include_superseded also returns replaced records. The optional shots array contains current-version shot boundaries and per-shot captions, scene, location guesses, visible text and confidence flags; it is absent on legacy records. Location guesses and folder mismatch are unverified hints. Correction-enabled transcripts expose text_original, corrected text and a correction audit. Their timed data array remains suitable for subtitles. Reference failure is marked missing; correction failure returns the original verbatim. Model inference uses the existing metered model path.
+ * Lists attached files and their ingestion status, newest attachment first by default. Use last_id as after to continue; ?filter=failed selects files that can be retried.
  */
-export const mediaListUnderstandings = (options) => (options.client ?? client).get({
+export const knowledgeListFiles = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/understandings',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files',
     ...options
 });
 /**
- * Expression search
+ * Add file
  *
- * Find visually similar assets using exactly one of asset_id or an inline base64 image. The library must support image search; an asset query needs a current image embedding and excludes that source asset from results.
+ * Attach an uploaded File for asynchronous ingestion, then poll this attachment until status is completed, failed or cancelled before searching. PDF files accept up to 536870912 bytes (512 MiB), while other formats accept up to 52428800 bytes (50 MiB), constrained by Router conversion; every file is limited to 5000000 estimated tokens; chunk sizes use estimated tokens rather than a model tokenizer. Text, Markdown, CSV, JSON, HTML, PDF, DOCX, PPTX, XLSX and PNG/JPEG/GIF/WebP images can be extracted; audio and video uploads are not knowledge documents. Images may yield generated descriptions rather than verbatim OCR. auto chunking resolves to static 800/400; explicit sizes are 100–4096 with overlap at most half the size. Each store holds at most 10000 attached files. Reattaching the same file returns its existing record without applying new attributes or chunking; inspect last_error after failure.
  */
-export const mediaExpressionSearch = (options) => (options.client ?? client).post({
+export const knowledgeAttachFile = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/search/expression',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8148,53 +8192,45 @@ export const mediaExpressionSearch = (options) => (options.client ?? client).pos
     }
 });
 /**
- * Visual search
+ * Remove file
  *
- * Search assets with a nonblank text query and optional expression filter. Hybrid mode combines semantic and keyword matches; semantic mode uses vector similarity only. Results are ranked and limited by top_k.
+ * Removes the file from search immediately; does not delete the original File.
  */
-export const mediaVisualSearch = (options) => (options.client ?? client).post({
+export const knowledgeRemoveFile = (options) => (options.client ?? client).delete({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/search/visual',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}',
+    ...options
 });
 /**
- * Semantic search
+ * Retrieve file
  *
- * Alias of semantic search. Search assets with a nonblank text query, optional expression filter and top_k; hybrid combines semantic and keyword matches, while semantic uses vector similarity only.
+ * Retrieves an attached file using the id returned by attachment or file listing. Poll this operation until status leaves in_progress to observe the ingestion outcome.
  */
-export const mediaSemanticSearch = (options) => (options.client ?? client).post({
+export const knowledgeRetrieveFile = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/search/semantic',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}',
+    ...options
 });
 /**
- * Semantic search alias
+ * Update file attributes
  *
- * List all immediate child folders under parent, or under the root when parent is omitted. Counts include descendant assets. The result is unpaginated; limit and cursor are rejected.
+ * Replaces search-filter attributes of an existing attachment without reingesting its content. Use an attached file id. Example body: {"attributes":{"category":"refund"}}; null clears the attributes.
  */
-export const mediaSearch = (options) => (options.client ?? client).post({
+export const knowledgeUpdateFile = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/search',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8202,31 +8238,31 @@ export const mediaSearch = (options) => (options.client ?? client).post({
     }
 });
 /**
- * List folders
+ * Read extracted content
  *
- * undefined understood_count includes ready and partial assets; failed_count includes failed assets. Both accumulate descendants. counts_complete is false during historical backfill.
+ * Extracted text chunks may overlap. Image content can be a generated description rather than verbatim OCR.
  */
-export const mediaListFolders = (options) => (options.client ?? client).get({
+export const knowledgeRetrieveFileContent = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/folders',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}/content',
     ...options
 });
 /**
- * Create batch
+ * Create file batch
  *
- * Queue a frozen selection for tagging, untagging, context replacement, moving, deleting or reprocessing. IDs are limited to 1000; use an expression for larger selections, subject to the search scan budget. reprocess starts at most 30 assets per rolling minute per library. Only retryable failed steps and legacy source-size unsupported steps rerun. Omit kinds to inspect all recoverable steps, or supply kinds to narrow them. Other unsupported, permanent and completed steps remain unchanged; a permanent output blocks only its own step. Assets without any selected recoverable step count as failed items without starting understanding. Poll the returned job id; done counts accepted launches, not successful model inference. Staff Admin only permits reprocess and requires a nonblank reason. Example: {"action":"reprocess","selector":{"expression":"processing_state=failed AND failure_code=UPSTREAM_FAILED"}}. For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
+ * Attaches existing Files as a batch for asynchronous ingestion. Supply exactly one of file_ids or files; files allows per-file settings. Existing attachments are reused. Read the returned batch id to monitor status.
  */
-export const mediaCreateBatch = (options) => (options.client ?? client).post({
+export const knowledgeCreateFileBatch = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/batches',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8234,169 +8270,157 @@ export const mediaCreateBatch = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Get batch
+ * Retrieve file batch
  *
- * Alias of batch creation. Apply one metadata or deletion action to ids or a frozen expression selection asynchronously; poll the returned job id to inspect completion and item failures.
+ * Retrieves a batch created in this knowledge base, including current status and file counts. Use the batch id returned by batch creation to monitor ingestion.
  */
-export const mediaGetBatch = (options) => (options.client ?? client).get({
+export const knowledgeRetrieveFileBatch = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/batches/{job_id}',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches/{batch_id}',
     ...options
 });
 /**
- * Batch assets alias
+ * Cancel file batch
  *
- * Queue a frozen selection for tagging, untagging, context replacement, moving, deleting or reprocessing. IDs are limited to 1000; use an expression for larger selections, subject to the search scan budget. reprocess starts at most 30 assets per rolling minute per library. Only retryable failed steps and legacy source-size unsupported steps rerun. Omit kinds to inspect all recoverable steps, or supply kinds to narrow them. Other unsupported, permanent and completed steps remain unchanged; a permanent output blocks only its own step. Assets without any selected recoverable step count as failed items without starting understanding. Poll the returned job id; done counts accepted launches, not successful model inference. Staff Admin only permits reprocess and requires a nonblank reason. Example: {"action":"reprocess","selector":{"expression":"processing_state=failed AND failure_code=UPSTREAM_FAILED"}}. For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
+ * Cancels only in-progress batches and pending files. Completed, failed and cancelled batches return unchanged (200, idempotent).
  */
-export const mediaBatchAssets = (options) => (options.client ?? client).post({
+export const knowledgeCancelFileBatch = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/assets:batch',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches/{batch_id}/cancel',
+    ...options
 });
 /**
- * Get job
+ * List batch files
  *
- * Read the current batch or video-generation Job status and progress. For generation, inspect outputs and failures, then save successful candidates before their preview and save window expires after 7 days.
+ * Lists files still attached from the identified batch, newest attachment first by default. Use the batch creation id and ?filter=failed to inspect failures; last_id is the next after cursor.
  */
-export const mediaGetJob = (options) => (options.client ?? client).get({
+export const knowledgeListBatchFiles = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/jobs/{job_id}',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/file_batches/{batch_id}/files',
     ...options
 });
 /**
- * List events
+ * Restore knowledge base
  *
- * Read library events in sequence order for observing asset writes and understanding progress. Obtain library_id from creation or listing; continue with after_seq for asc or before_seq for desc, without combining both. Use next_cursor when supplied. Reads do not start or retry understanding.
+ * Restores a deleting store within 7 days. Active stores return 409 VECTOR_STORE_INVALID_STATE; absent stores return 404. Empty body is allowed.
  */
-export const mediaListEvents = (options) => (options.client ?? client).get({
+export const knowledgeRestoreVectorStore = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/events',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/restore',
     ...options
 });
 /**
- * Create delivery token
+ * Permanently purge knowledge base
  *
- * Issue a time-limited bearer token for originals and transformed authenticated assets in an active library. Use library_id from library creation or listing; read access is sufficient. Append token as the __cld_token__ query parameter on a matching delivery URL. The default ACL covers this library and the default lifetime is 900 seconds; narrow acl and expires_in before sharing. Anyone holding the token can read matching paths until expires_at.
+ * Immediately and irreversibly clears a deleting store using the retention cleanup path. Active stores return 409; absent stores return 404. Empty body is allowed.
  */
-export const mediaCreateDeliveryToken = (options) => (options.client ?? client).post({
+export const knowledgePurgeVectorStore = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/delivery_tokens',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/purge',
+    ...options
 });
 /**
- * Summarize understanding failures
+ * Retry failed file
  *
- * Inspect current understanding failures before retrying. Use library_id from library creation or listing. Groups include code, output kind, actual producer model, retryability and up to five sample asset IDs. At most 1024 detailed groups plus two overflow groups are returned; overflow groups separate retryable and unrecoverable entries and mark overflow=true. Unknown failure codes remain retryable. Historical counts are provisional while counts_complete is false. Example: GET /media/v1/libraries/lib_example/understandings/failure_summary.
+ * Retries only failed files; other states return 409 FILE_INVALID_STATE. Retry after failure has not yet been observed in the documented run.
  */
-export const mediaUnderstandingFailureSummary = (options) => (options.client ?? client).get({
+export const knowledgeRetryFile = (options) => (options.client ?? client).post({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/understandings/failure_summary',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}/retry',
     ...options
 });
 /**
- * List understanding results across a library
+ * List file segments
  *
- * Read current understanding entries across one library without fetching every asset separately. Use library_id from creation or listing. folder includes descendants; kinds is a comma-separated list of output kinds. Entries are ordered by asset_id and then understanding id. Continue with next_cursor and the same folder and kinds; limit defaults to 100 and cannot exceed 100. Superseded, deleted and old-version entries are excluded. During historical backfill, this method returns 503 CAPACITY rather than incomplete pages; poll failureSummary until counts_complete is true, then start pagination. Example: GET /media/v1/libraries/lib_example/understandings?folder=travel&kinds=caption,transcript&limit=100.
+ * Lists the stored chunks of an attached file, ordered by increasing segment index by default. Use the attachment id and last_id as after to continue; returned chunk ids can be retrieved individually.
  */
-export const mediaListUnderstandingsByLibrary = (options) => (options.client ?? client).get({
+export const knowledgeListSegments = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/understandings',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/files/{file_id}/segments',
     ...options
 });
 /**
- * Create video generation
+ * Retrieve segment
  *
- * Create a video.generate job. Generation is charged per second. The response is 202 with a queued Job; poll GET /media/v1/libraries/{library_id}/jobs/{job_id} until terminal, then save successful outputs. Unsaved candidate Files expire after 7 days.
+ * Retrieves one chunk and its term statistics. Take chunk_id from segment listing or native search content; the chunk must belong to this knowledge base.
  */
-export const mediaCreateGeneration = (options) => (options.client ?? client).post({
+export const knowledgeRetrieveSegment = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/generations',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/segments/{chunk_id}',
+    ...options
 });
 /**
- * List jobs
+ * List events
  *
- * List batch and video-generation jobs in a library. Filter by status and continue with next_cursor. Poll a generation Job until terminal, then save successful candidate outputs before they expire after 7 days.
+ * Reads events for this knowledge base in increasing sequence order, including while soft-deleted. Pass next_seq as after_seq to continue; null next_seq marks the current end. Example: ?after_seq=0&limit=20.
  */
-export const mediaListJobs = (options) => (options.client ?? client).get({
+export const knowledgeListEvents = (options) => (options.client ?? client).get({
     security: [{
-            key: 'media-BearerAuth',
+            key: 'knowledge-bearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/jobs',
+    url: '/knowledge/v1/vector_stores/{vector_store_id}/events',
     ...options
 });
 /**
- * Cancel job
+ * List libraries
  *
- * Cancel a queued or running generation job. Already completed outputs remain available to save; poll or read the returned Job to confirm its status.
+ * Read a caller-owned library’s current settings, usage and lifecycle status. A deleting library remains readable; missing, foreign or purged libraries return LIBRARY_NOT_FOUND.
  */
-export const mediaCancelJob = (options) => (options.client ?? client).post({
+export const mediaListLibraries = (options) => (options?.client ?? client).get({
     security: [{
             key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/jobs/{job_id}/cancel',
+    url: '/media/v1/libraries',
     ...options
 });
 /**
- * Save generation output
+ * Create library
  *
- * Save a successful candidate as a library asset. Candidate outputs expire after 7 days; save before expiry. Generation is charged per second when the job runs, not when an output is saved.
+ * Create a library owned by the caller with a name, optional labels and understanding settings. Understanding is enabled by default; the returned id is used for subsequent asset operations.
  */
-export const mediaSaveGenerationOutput = (options) => (options.client ?? client).post({
+export const mediaCreateLibrary = (options) => (options.client ?? client).post({
     security: [{
             key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/libraries/{library_id}/jobs/{job_id}/outputs/{index}/save',
+    url: '/media/v1/libraries',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8404,45 +8428,63 @@ export const mediaSaveGenerationOutput = (options) => (options.client ?? client)
     }
 });
 /**
- * Get generation capabilities
+ * Create frame URLs
  *
- * Read supported text-to-video intent, default model, duration and aspect-ratio limits, per-library concurrency and candidate retention. Generation is charged per second; unsaved candidates expire after 7 days.
+ * Media creates JPEG frame URLs for inspecting one or more moments in a video without downloading the original. Obtain library_id from libraries and asset_id plus duration from assets. Send 1–20 integer microsecond timestamps strictly below duration, for example {"at_micros":[0,1000000],"width":640}. Only video assets are supported; audio and images return INVALID_PARAMS. Width defaults to 640 and accepts 160, 320 or 640. This read operation does not store a new asset or rerun understanding. Fetch each returned URL to obtain the frame; delivery usage follows media pricing. Authenticated links expire after 300 seconds; upload links remain public and permanent. Reissue expired links. Foreign libraries and assets return 404 without revealing their existence.
  */
-export const mediaGetGenerationCapabilities = (options) => (options?.client ?? client).get({
+export const mediaCreateFrameUrls = (options) => (options.client ?? client).post({
     security: [{
             key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/media/v1/generation/capabilities',
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/frames',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Delete library
+ *
+ * Restore a deleting library before its purge_at deadline. The library becomes active again and deleted_at and purge_at are cleared; expired or non-deleting libraries cannot be restored.
+ */
+export const mediaDeleteLibrary = (options) => (options.client ?? client).delete({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}',
     ...options
 });
 /**
- * List types
+ * Get library
  *
- * Read the node and relation types registered for this organization before writing, so a create names a type the graph accepts. Each entry is one registrant's registration with its owner, version and definitions. Types cannot be created at runtime; they are registered by the owning service at deploy time, so a type missing here is not available to write.
+ * Update an active library’s supplied settings. Labels replace the complete map; understanding settings and model roles merge with current values. Changing the embedding model is rejected while assets exist.
  */
-export const ontologyListTypes = (options) => (options?.client ?? client).get({
+export const mediaGetLibrary = (options) => (options.client ?? client).get({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/types',
+    url: '/media/v1/libraries/{library_id}',
     ...options
 });
 /**
- * Register type
+ * Update library
  *
- * Register a node or relation type for this organization. Not open yet — this call currently answers 501 NOT_IMPLEMENTED and writes nothing, because a registration is checked and stored by the deploy gate that ships the registering service, not by a runtime call. Until it opens, read the types already in force with praxis.ontology.types.list and create records only of those types.
+ * Update an active library. Set hotwords for spelling evidence in subsequent transcripts; [] disables inferred vocabulary. Transcript understanding calls the timestamped ASR, optional reference ASR and correction model through the existing metered model path. Reprocess assets to apply new settings to existing transcripts.
  */
-export const ontologyRegisterType = (options) => (options.client ?? client).post({
+export const mediaUpdateLibrary = (options) => (options.client ?? client).patch({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/types',
+    url: '/media/v1/libraries/{library_id}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8450,77 +8492,77 @@ export const ontologyRegisterType = (options) => (options.client ?? client).post
     }
 });
 /**
- * Retrieve type
+ * Restore library
  *
- * Read one registered type's definition before writing a record of it, to learn whether it is a node or an edge, which endpoints an edge type admits, and which origins it accepts. The name comes from types.list; a name that is not registered answers ONTOLOGY_TYPE_UNKNOWN, and writes of that type are refused.
+ * Permanently remove a library that is already deleting, without waiting for purge_at. Its assets and related resources are removed and cannot be restored; first soft-delete an active library.
  */
-export const ontologyRetrieveType = (options) => (options.client ?? client).get({
+export const mediaRestoreLibrary = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/types/{name}',
+    url: '/media/v1/libraries/{library_id}/restore',
     ...options
 });
 /**
- * List nodes
+ * Purge library
  *
- * Discover the entities in this organization's graph and obtain node ids for retrieval, updates and relations. Filter by type, by free text over names, aliases, descriptions and facts, or by owner; limit is 1–100 and defaults to 50. Omit cursor for the first page, then copy next_cursor into the next request until it is null. A node whose content belongs to somebody else comes back as a restricted entry carrying only its id, type and name.
+ * List assets in an active library, newest first, optionally filtering by exact folder and stored resource type. Continue using next_cursor; video includes audio-only assets.
  */
-export const ontologyListNodes = (options) => (options?.client ?? client).get({
+export const mediaPurgeLibrary = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/nodes',
+    url: '/media/v1/libraries/{library_id}/purge',
     ...options
 });
 /**
- * Create node
+ * List assets
  *
- * Record one entity in the graph, for a system mirroring a record it owns. type must already be registered and ref, when given, must match that type's ref_prefix. Send an Idempotency-Key header; repeating the same key with the same content returns the first result instead of creating a second node. This writes structure only — to give an agent something to remember, use POST /agent/v1/agents/{agent_id}/consolidations.
+ * Upload content into an active library and return the stored asset. Use file for a multipart file, data URI, public HTTPS URL or same-owner file identifier. Reusing public_id overwrites by default; overwrite=false returns the existing asset. Chunk uploads require both chunk headers.
  */
-export const ontologyCreateNode = (options) => (options.client ?? client).post({
+export const mediaListAssets = (options) => (options.client ?? client).get({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/nodes',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/media/v1/libraries/{library_id}/assets',
+    ...options
 });
 /**
- * Retrieve node
+ * Upload asset
  *
- * Read one node's content and, with expand=relations, every relation on and around it. as_of reads the node as it was at that time. A node id from another organization, or one that never existed, answers ONTOLOGY_NODE_NOT_FOUND; a node you may reach but not read returns restricted true with its name only.
+ *  For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
  */
-export const ontologyRetrieveNode = (options) => (options.client ?? client).get({
+export const mediaUploadAsset = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/nodes/{node_id}',
-    ...options
+    url: '/media/v1/libraries/{library_id}/assets',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Update node
+ * Import file
  *
- * Change a node's name, aliases or description when the mirrored record was renamed, without touching its type or identity. Send only the fields to change; omitted fields keep their current values and an explicitly null description clears it. Repeating the same edit converges on the same node, so this needs no Idempotency-Key.
+ * Copy a File into an independent Media asset. New assets default to organization-private delivery (type=authenticated); explicitly set type=upload for public originals and derivatives. Omitting type on overwrite preserves the current type. Deleting the source File does not delete this copy. For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
  */
-export const ontologyUpdateNode = (options) => (options.client ?? client).patch({
+export const mediaImportAsset = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/nodes/{node_id}',
+    url: '/media/v1/libraries/{library_id}/assets/import',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8528,63 +8570,63 @@ export const ontologyUpdateNode = (options) => (options.client ?? client).patch(
     }
 });
 /**
- * Retrieve neighborhood
+ * Delete asset
  *
- * Load the subgraph around one node instead of the whole graph — the read to use when a screen or an agent needs the context of one entity. Returns the start node, every node within depth hops of it, the relations whose both ends are in that set, and truncated true when the node limit cut the walk short. direction chooses which way relations are followed; as_of and include_invalid read the graph as those parameters do elsewhere. Visibility is exactly nodes.retrieve's — a node you may reach but not read comes back restricted with its name only, and relations touching it are withheld, so this read never reaches further than a node read does. The node id comes from nodes.list, nodes.create or a changeset; an unknown one answers ONTOLOGY_NODE_NOT_FOUND, the same answer nodes.retrieve gives.
+ * Queue reprocessing of the asset’s current version and return its updated state immediately. Omit kinds to retry failed tasks and legacy source-size unsupported tasks; explicit kinds rerun applicable completed tasks and recoverable source-size unsupported tasks. Other unsupported causes remain unchanged. Replaced understandings become superseded, and processing finishes asynchronously.
  */
-export const ontologyNeighborhood = (options) => (options.client ?? client).get({
+export const mediaDeleteAsset = (options) => (options.client ?? client).delete({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/nodes/{node_id}/neighborhood',
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}',
     ...options
 });
 /**
- * Merge node
+ * Get asset
  *
- * Fold a duplicate node into the node that should survive, when two records are discovered to be the same entity. The merged node's relations and aliases move to the survivor and later reads of the duplicate resolve to it. Send an Idempotency-Key header; repeating the same key replays the first result. Reversal is a staff operation, not available here.
+ * Update an asset’s supplied metadata fields. Tags and context replace their current collections; an empty collection clears them. Moving asset_folder or changing display_name preserves public_id and delivery URLs.
  */
-export const ontologyMergeNode = (options) => (options.client ?? client).post({
+export const mediaGetAsset = (options) => (options.client ?? client).get({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/nodes/{node_id}/merge',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}',
+    ...options
 });
 /**
- * List relations
+ * Update asset
  *
- * Read the facts in the graph and obtain relation ids for retrieval, invalidation or spreading. Filter by endpoint node, by type and by direction; as_of reads the relations as they were then. Invalidated relations are omitted unless include_invalid is true. limit is 1–100 and defaults to 50; follow next_cursor until it is null.
+ * Delete an asset from the library so it is no longer readable, searchable or deliverable. This removes the asset rather than placing it in the library’s restoration window; a missing asset returns ASSET_NOT_FOUND.
  */
-export const ontologyListRelations = (options) => (options?.client ?? client).get({
+export const mediaUpdateAsset = (options) => (options.client ?? client).patch({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/relations',
-    ...options
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Create relation
+ * Reprocess asset
  *
- * Record one fact between two existing nodes, for a system mirroring a relationship it owns. type must be registered and must admit these endpoints; fact states the relationship in one sentence. Send an Idempotency-Key header; repeating the same key returns the first result instead of writing a second relation. This writes structure only — to give an agent something to remember, use POST /agent/v1/agents/{agent_id}/consolidations.
+ *  For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
  */
-export const ontologyCreateRelation = (options) => (options.client ?? client).post({
+export const mediaReprocessAsset = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/relations',
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/reprocess',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8592,31 +8634,31 @@ export const ontologyCreateRelation = (options) => (options.client ?? client).po
     }
 });
 /**
- * Retrieve relation
+ * List understandings
  *
- * Read one relation's fact and both of its clocks — valid_at and invalid_at for when it was true in the world, created_at and expired_at for when it was recorded and retired. An id from another organization, or one that never existed, answers ONTOLOGY_EDGE_NOT_FOUND.
+ * List understanding results for an asset, ordered by creation time. Use the cursor to continue; include_superseded also returns replaced records. The optional shots array contains current-version shot boundaries and per-shot captions, scene, location guesses, visible text and confidence flags; it is absent on legacy records. Location guesses and folder mismatch are unverified hints. Correction-enabled transcripts expose text_original, corrected text and a correction audit. Their timed data array remains suitable for subtitles. Reference failure is marked missing; correction failure returns the original verbatim. Model inference uses the existing metered model path.
  */
-export const ontologyRetrieveRelation = (options) => (options.client ?? client).get({
+export const mediaListUnderstandings = (options) => (options.client ?? client).get({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/relations/{relation_id}',
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/understandings',
     ...options
 });
 /**
- * Invalidate relation
+ * Expression search
  *
- * Mark a relation as no longer true from a world time, when the mirrored record changed. The relation is kept — invalid_at moves and the relation still reads at an earlier as_of, so history stays answerable. Send an Idempotency-Key header; repeating the same key replays the first result. There is no delete.
+ * Find visually similar assets using exactly one of asset_id or an inline base64 image. The library must support image search; an asset query needs a current image embedding and excludes that source asset from results.
  */
-export const ontologyInvalidateRelation = (options) => (options.client ?? client).post({
+export const mediaExpressionSearch = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/relations/{relation_id}/invalidate',
+    url: '/media/v1/libraries/{library_id}/search/expression',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8624,17 +8666,17 @@ export const ontologyInvalidateRelation = (options) => (options.client ?? client
     }
 });
 /**
- * Apply changeset
+ * Visual search
  *
- * Apply a batch of node, relation and invalidation operations as one transaction, when a mirror has several records to write together and a partial write would leave the graph inconsistent. Every operation succeeds or none is applied. Send an Idempotency-Key header; the same key with the same content replays the first result, and the same key with different content is ONTOLOGY_CONFLICT.
+ * Search assets with a nonblank text query and optional expression filter. Hybrid mode combines semantic and keyword matches; semantic mode uses vector similarity only. Results are ranked and limited by top_k.
  */
-export const ontologyApplyChangeset = (options) => (options.client ?? client).post({
+export const mediaVisualSearch = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/changesets',
+    url: '/media/v1/libraries/{library_id}/search/visual',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8642,17 +8684,17 @@ export const ontologyApplyChangeset = (options) => (options.client ?? client).po
     }
 });
 /**
- * Search nodes
+ * Semantic search
  *
- * Resolve text to the nodes it most likely names, when a mirror holds a name and needs the node id it corresponds to. Results are ranked candidates, not an answer, each reporting whether the match came from the node's name, an alias, its description or a relation's fact. Narrow with types, and cap the result count with limit (1–50, default 20). This reads structure; it is not an agent recall — agents recall through POST /agent/v1/agents/{agent_id}/consolidations.
+ * Alias of semantic search. Search assets with a nonblank text query, optional expression filter and top_k; hybrid combines semantic and keyword matches, while semantic uses vector similarity only.
  */
-export const ontologySearch = (options) => (options.client ?? client).post({
+export const mediaSemanticSearch = (options) => (options.client ?? client).post({
     security: [{
-            key: 'ontology-bearerAuth',
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
         }],
-    url: '/ontology/v1/search',
+    url: '/media/v1/libraries/{library_id}/search/semantic',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -8660,47 +8702,605 @@ export const ontologySearch = (options) => (options.client ?? client).post({
     }
 });
 /**
- * List sandboxes (v2)
+ * Semantic search alias
  *
- * List your running and paused sandboxes with paging and filters. Use it to find a sandboxID before connecting to, pausing or killing a sandbox. Filter by state, template (id or alias), name, metadata (key=value pairs joined with &) and startedAfter; order sorts by start time (default newest first); limit is 1 to 100 (default 100). When more results exist the response carries an x-next-token header; send it back as nextToken for the next page. To read one sandbox use getSandbox.
+ * List all immediate child folders under parent, or under the root when parent is omitted. Counts include descendant assets. The result is unpaginated; limit and cursor are rejected.
  */
-export const getSandboxV1Sandboxes = (options) => (options?.client ?? client).get({
-    querySerializer: { parameters: { state: { array: { explode: false } } } },
-    security: [
-        {
-            key: 'sandbox-ApiKeyAuth',
-            name: 'X-API-Key',
-            type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AuthProviderBearerAuth',
-            scheme: 'bearer',
-            type: 'http'
-        },
-        {
-            key: 'sandbox-AuthProviderTeamAuth',
-            name: 'X-Team-ID',
-            type: 'apiKey'
-        },
-        { name: 'X-Admin-Token', type: 'apiKey' },
-        {
-            key: 'sandbox-AdminTeamAuth',
-            name: 'X-Team-ID',
-            type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AdminJWTAuth',
+export const mediaSearch = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        }
-    ],
+        }],
+    url: '/media/v1/libraries/{library_id}/search',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * List folders
+ *
+ * undefined understood_count includes ready and partial assets; failed_count includes failed assets. Both accumulate descendants. counts_complete is false during historical backfill.
+ */
+export const mediaListFolders = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/folders',
+    ...options
+});
+/**
+ * Create batch
+ *
+ * Queue a frozen selection for tagging, untagging, context replacement, moving, deleting or reprocessing. IDs are limited to 1000; use an expression for larger selections, subject to the search scan budget. reprocess starts at most 30 assets per rolling minute per library. Only retryable failed steps and legacy source-size unsupported steps rerun. Omit kinds to inspect all recoverable steps, or supply kinds to narrow them. Other unsupported, permanent and completed steps remain unchanged; a permanent output blocks only its own step. Assets without any selected recoverable step count as failed items without starting understanding. Poll the returned job id; done counts accepted launches, not successful model inference. Staff Admin only permits reprocess and requires a nonblank reason. Example: {"action":"reprocess","selector":{"expression":"processing_state=failed AND failure_code=UPSTREAM_FAILED"}}. For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
+ */
+export const mediaCreateBatch = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/batches',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Get batch
+ *
+ * Alias of batch creation. Apply one metadata or deletion action to ids or a frozen expression selection asynchronously; poll the returned job id to inspect completion and item failures.
+ */
+export const mediaGetBatch = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/batches/{job_id}',
+    ...options
+});
+/**
+ * Batch assets alias
+ *
+ * Queue a frozen selection for tagging, untagging, context replacement, moving, deleting or reprocessing. IDs are limited to 1000; use an expression for larger selections, subject to the search scan budget. reprocess starts at most 30 assets per rolling minute per library. Only retryable failed steps and legacy source-size unsupported steps rerun. Omit kinds to inspect all recoverable steps, or supply kinds to narrow them. Other unsupported, permanent and completed steps remain unchanged; a permanent output blocks only its own step. Assets without any selected recoverable step count as failed items without starting understanding. Poll the returned job id; done counts accepted launches, not successful model inference. Staff Admin only permits reprocess and requires a nonblank reason. Example: {"action":"reprocess","selector":{"expression":"processing_state=failed AND failure_code=UPSTREAM_FAILED"}}. For understanding, Media generates proxies for video sources of 25 MB or more or longer than 10 minutes, and for audio-only sources of 100 MB or more; originals remain available unchanged. Long videos are supported. When a video proxy is needed and is still above 95 MB after recompression, the source is reported as UNSUPPORTED with the limit in the failure message. Proxy preparation uses the organization’s metered sandbox resources.
+ */
+export const mediaBatchAssets = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/assets:batch',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Get job
+ *
+ * Read the current batch or generation Job status and progress. For generation, inspect outputs and failures; a successful output has already landed in the library as an asset.
+ */
+export const mediaGetJob = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/jobs/{job_id}',
+    ...options
+});
+/**
+ * List events
+ *
+ * Read library events in sequence order for observing asset writes and understanding progress. Obtain library_id from creation or listing; continue with after_seq for asc or before_seq for desc, without combining both. Use next_cursor when supplied. Reads do not start or retry understanding.
+ */
+export const mediaListEvents = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/events',
+    ...options
+});
+/**
+ * Create delivery token
+ *
+ * Issue a time-limited bearer token for originals and transformed authenticated assets in an active library. Use library_id from library creation or listing; read access is sufficient. Append token as the __cld_token__ query parameter on a matching delivery URL. The default ACL covers this library and the default lifetime is 900 seconds; narrow acl and expires_in before sharing. Anyone holding the token can read matching paths until expires_at.
+ */
+export const mediaCreateDeliveryToken = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/delivery_tokens',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Get default library
+ *
+ * Return this organization’s default library. Calling ensures the organization’s default library exists (ADR-093): the first call creates it and later calls return the same library, so this is the method to call before writing when no library id is known. Generated and edited media land here when no library is named. The path segment {lib} accepts the literal default, which resolves to this library before the credential check — so an agent that has never listed libraries can still write to the right place. Returns the same Library object as libraries.retrieve; a credential bound to one library reaches this only when that binding covers the default library.
+ */
+export const mediaGetDefaultLibrary = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/default',
+    ...options
+});
+/**
+ * Set default library
+ *
+ * Point this organization’s default library at an existing library. Calling ensures the organization’s default library exists (ADR-093): the path is resolved before the credential check, so a first call creates the default library when there is none and then repoints it. The path segment {lib} accepts the literal default, which resolves to this library before the credential check. Supply library_id from library creation or listing; the library must be active and belong to the organization. This changes where library-less generation and uploads land across the whole organization, so it affects other callers as well as this one. It does not move or copy any asset — assets already in the previous default library stay there. Returns the library now set as the default. Deleting the default library is refused with LIBRARY_IS_DEFAULT until another library is made the default.
+ */
+export const mediaSetDefaultLibrary = (options) => (options.client ?? client).put({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/default',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Get asset lineage
+ *
+ * Read the whole edit tree containing one asset, so a caller sees what it was edited from and what was edited from it. Use library_id from creation or listing and asset_id from asset creation or listing; library_id also accepts the literal default, which resolves to the organization’s default library before the credential check. The response names the root the tree descends from, the asset asked about, and every step between them, each with the operation, prompt and creation time that produced it. Deleted assets stay in the tree, marked deleted, so the chain stays connected after cleanup. This is a read: it starts no processing and changes no asset. Example: GET /media/v1/libraries/lib_example/assets/9dfa312ef9bc4b00816339b598b1152c/lineage.
+ */
+export const mediaGetAssetLineage = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/lineage',
+    ...options
+});
+/**
+ * Generate image
+ *
+ * Generate one or more images from a text prompt and store them straight into the library. Use library_id from creation or listing; the path segment {library_id} also accepts the literal default, which resolves to the organization’s default library before the credential check, so an agent that has never listed a library can still generate. The request body is the image request itself: prompt is required, and n, size, background, output_format, output, references, seed, model, asset_folder and understanding are optional. Set output to sticker for a cut-out with a transparent background. references attach existing assets with a role — edit_target, style, structure or subject — and a model that cannot honour a role returns REFERENCE_TYPE_MISMATCH. Aspect ratio is not accepted for images; name size instead. Generation is charged through Router and the job records the charge in usage; nothing is charged for a request refused before it starts. The response is 202 with a queued Job whose type is image and whose operation is generate; poll GET /media/v1/libraries/{library_id}/jobs/{job_id} until its status is completed or failed, then read the produced assets from the library. Send Idempotency-Key, or idempotency_key in the body, to retry without generating and charging twice. Example: POST /media/v1/libraries/default/images/generations with {"prompt":"A red kite above a calm sea at sunrise","n":1,"output":"sticker"}.
+ */
+export const mediaGenerateImage = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/images/generations',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Generate video
+ *
+ * Generate one or more videos from a text prompt and store them straight into the library. Use library_id from creation or listing; the path segment {library_id} also accepts the literal default, which resolves to the organization’s default library before the credential check, so an agent that has never listed a library can still generate. mode says what the video is anchored to: text needs only a prompt, image animates the existing image named by first_frame, and first_last interpolates between first_frame and last_frame. The frames must be image or sticker assets of the same library; Router is sent a fetchable URL for each, recorded in the produced asset’s provenance. mode reference and output gif are refused with OPERATION_NOT_SUPPORTED in this release, and negative_prompt, references and an unknown mode are refused before anything is charged. Every output lands in the library as a video asset as soon as it is ready — there is no candidate state and nothing expires, so outputs.save is not part of this lane. Generation is charged per second through Router and the job records the charge in usage; a refused request costs nothing. The response is 202 with a queued Job whose type is video and whose operation is generate; poll GET /media/v1/libraries/{library_id}/jobs/{job_id} until its status is completed or failed, then read the produced assets from the library. Send Idempotency-Key, or idempotency_key in the body, to retry without generating and charging twice. Example: POST /media/v1/libraries/default/videos/generations with {"prompt":"A red kite above a calm sea at sunrise","mode":"text","n":1}.
+ */
+export const mediaGenerateVideo = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/videos/generations',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Edit asset
+ *
+ * Edit an existing asset and store the result as a new asset. Use library_id from creation or listing and asset_id from asset creation or listing; library_id also accepts the literal default, which resolves to the organization’s default library before the credential check. The source asset is never overwritten: the new asset hangs under it in the edit chain, records it in derived_from, and reads back with assets.lineage, so earlier steps stay reachable. The body is operation plus the optional model, asset_folder, understanding and idempotency_key; operation.type selects the edit and carries that operation’s own fields. This release performs variations, inpaint, erase, replace_object, recolor, remove_background and replace_background on images; every other type in the operation vocabulary — the video and audio edits — is refused with OPERATION_NOT_SUPPORTED. inpaint takes mask, a PNG File identifier beginning with file- whose transparent area marks the region to replace, plus the prompt describing what belongs there. Aspects beyond the source asset’s material type return REFERENCE_TYPE_MISMATCH. Editing is charged through Router and the job records the charge in usage. The response is 202 with a queued Job whose type is image, whose operation is the edit applied, and whose source_asset_id is the asset edited; poll GET /media/v1/libraries/{library_id}/jobs/{job_id} until it is completed or failed, then read the produced asset. Example: POST /media/v1/libraries/lib_example/assets/9dfa312ef9bc4b00816339b598b1152c/edits with {"operation":{"type":"variations","strength":"subtle"}}.
+ */
+export const mediaEditAsset = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/assets/{asset_id}/edits',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Create speech
+ *
+ * Synthesise speech from text and store the recording straight into the library. Use library_id from creation or listing; the path segment {library_id} also accepts the literal default, which resolves to the organization’s default library before the credential check, so an agent that has never listed a library can still synthesise. input is the text to speak and voice is required; speed is passed to the provider unchanged, and instructions and language are refused with OPERATION_NOT_SUPPORTED in this release. A voice that names a voice material of this library is refused the same way — voice cloning opens with voices.create. The provider caps one request at a short stretch of text, so a long input is cut into segments at paragraph and sentence boundaries and synthesised in order, then joined into the single recording the library receives: nothing is spoken twice and nothing is dropped. Because the segments are joined byte for byte, a multi-segment input accepts only response_format mp3 (the default) or pcm; opus is available for a single-segment input. A speech job has one result however many segments it took. Synthesis is charged through Router and the job records the charge in usage; a request refused before it starts costs nothing. The response is 202 with a queued Job whose type is speech and whose operation is generate; poll GET /media/v1/libraries/{library_id}/jobs/{job_id} until its status is completed or failed, then read the produced asset from the library — the recording carries material_type audio, audio_role voice, ai_generated true, and provenance naming this job, the text spoken and the model. Send Idempotency-Key, or idempotency_key in the body, to retry without synthesising and charging twice. Example: POST /media/v1/libraries/default/audio/speech with {"input":"A red kite above a calm sea at sunrise.","voice":"alloy"}.
+ */
+export const mediaCreateSpeech = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/audio/speech',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Summarize understanding failures
+ *
+ * Inspect current understanding failures before retrying. Use library_id from library creation or listing. Groups include code, output kind, actual producer model, retryability and up to five sample asset IDs. At most 1024 detailed groups plus two overflow groups are returned; overflow groups separate retryable and unrecoverable entries and mark overflow=true. Unknown failure codes remain retryable. Historical counts are provisional while counts_complete is false. Example: GET /media/v1/libraries/lib_example/understandings/failure_summary.
+ */
+export const mediaUnderstandingFailureSummary = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/understandings/failure_summary',
+    ...options
+});
+/**
+ * List understanding results across a library
+ *
+ * Read current understanding entries across one library without fetching every asset separately. Use library_id from creation or listing. folder includes descendants; kinds is a comma-separated list of output kinds. Entries are ordered by asset_id and then understanding id. Continue with next_cursor and the same folder and kinds; limit defaults to 100 and cannot exceed 100. Superseded, deleted and old-version entries are excluded. During historical backfill, this method returns 503 CAPACITY rather than incomplete pages; poll failureSummary until counts_complete is true, then start pagination. Example: GET /media/v1/libraries/lib_example/understandings?folder=travel&kinds=caption,transcript&limit=100.
+ */
+export const mediaListUnderstandingsByLibrary = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/understandings',
+    ...options
+});
+/**
+ * List jobs
+ *
+ * List batch and generation jobs in a library. Filter by status and continue with next_cursor. Poll a generation Job until terminal; every produced output is already a library asset.
+ */
+export const mediaListJobs = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/jobs',
+    ...options
+});
+/**
+ * Cancel job
+ *
+ * Cancel a queued or running generation job. Outputs already produced remain in the library; poll or read the returned Job to confirm its status.
+ */
+export const mediaCancelJob = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/libraries/{library_id}/jobs/{job_id}/cancel',
+    ...options
+});
+/**
+ * Get generation capabilities
+ *
+ * Read what Praxis offers for each kind of generation — image, video and speech — before asking for one. Every type answers the models available for it, the model it uses when a request names none, and what each model costs per unit; the video fields beside them keep their original meaning (intents, default model, duration and aspect-ratio limits, per-library concurrency). The models come from the platform model catalogue, and an id listed here is accepted verbatim as the model field of that type’s generation request. price.amount is a decimal string with its currency; video models that charge by resolution also carry price.by_resolution, whose amount is then the cheapest tier. A model the catalogue cannot route right now is still listed, with available false, so a caller can show it as temporarily unavailable instead of hiding it. When the catalogue cannot be read the endpoint still answers: every type comes back with an empty models list and its real default_model. Generation is charged per unit and every output is stored in the library.
+ */
+export const mediaGetGenerationCapabilities = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'media-BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/media/v1/generation/capabilities',
+    ...options
+});
+/**
+ * List types
+ *
+ * Read the node and relation types registered for this organization before writing, so a create names a type the graph accepts. Each entry is one registrant's registration with its owner, version and definitions. Types cannot be created at runtime; they are registered by the owning service at deploy time, so a type missing here is not available to write.
+ */
+export const ontologyListTypes = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/types',
+    ...options
+});
+/**
+ * Register type
+ *
+ * Register a node or relation type for this organization. Not open yet — this call currently answers 501 NOT_IMPLEMENTED and writes nothing, because a registration is checked and stored by the deploy gate that ships the registering service, not by a runtime call. Until it opens, read the types already in force with praxis.ontology.types.list and create records only of those types.
+ */
+export const ontologyRegisterType = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/types',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Retrieve type
+ *
+ * Read one registered type's definition before writing a record of it, to learn whether it is a node or an edge, which endpoints an edge type admits, and which origins it accepts. The name comes from types.list; a name that is not registered answers ONTOLOGY_TYPE_UNKNOWN, and writes of that type are refused.
+ */
+export const ontologyRetrieveType = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/types/{name}',
+    ...options
+});
+/**
+ * List nodes
+ *
+ * Discover the entities in this organization's graph and obtain node ids for retrieval, updates and relations. Filter by type, by free text over names, aliases, descriptions and facts, or by owner; limit is 1–100 and defaults to 50. Omit cursor for the first page, then copy next_cursor into the next request until it is null. A node whose content belongs to somebody else comes back as a restricted entry carrying only its id, type and name.
+ */
+export const ontologyListNodes = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/nodes',
+    ...options
+});
+/**
+ * Create node
+ *
+ * Record one entity in the graph, for a system mirroring a record it owns. type must already be registered and ref, when given, must match that type's ref_prefix. Send an Idempotency-Key header; repeating the same key with the same content returns the first result instead of creating a second node. This writes structure only; it does not give any agent a memory.
+ */
+export const ontologyCreateNode = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/nodes',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Retrieve node
+ *
+ * Read one node's content and, with expand=relations, every relation on and around it. as_of reads the node as it was at that time. A node id from another organization, or one that never existed, answers ONTOLOGY_NODE_NOT_FOUND; a node you may reach but not read returns restricted true with its name only.
+ */
+export const ontologyRetrieveNode = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/nodes/{node_id}',
+    ...options
+});
+/**
+ * Update node
+ *
+ * Change a node's name, aliases or description when the mirrored record was renamed, without touching its type or identity. Send only the fields to change; omitted fields keep their current values and an explicitly null description clears it. Repeating the same edit converges on the same node, so this needs no Idempotency-Key.
+ */
+export const ontologyUpdateNode = (options) => (options.client ?? client).patch({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/nodes/{node_id}',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Retrieve neighborhood
+ *
+ * Load the subgraph around one node instead of the whole graph — the read to use when a screen or an agent needs the context of one entity. Returns the start node, every node within depth hops of it, the relations whose both ends are in that set, and truncated true when the node limit cut the walk short. direction chooses which way relations are followed; as_of and include_invalid read the graph as those parameters do elsewhere. Visibility is exactly nodes.retrieve's — a node you may reach but not read comes back restricted with its name only, and relations touching it are withheld, so this read never reaches further than a node read does. The node id comes from nodes.list, nodes.create or a changeset; an unknown one answers ONTOLOGY_NODE_NOT_FOUND, the same answer nodes.retrieve gives.
+ */
+export const ontologyNeighborhood = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/nodes/{node_id}/neighborhood',
+    ...options
+});
+/**
+ * Merge node
+ *
+ * Fold a duplicate node into the node that should survive, when two records are discovered to be the same entity. The merged node's relations and aliases move to the survivor and later reads of the duplicate resolve to it. Send an Idempotency-Key header; repeating the same key replays the first result. Reversal is a staff operation, not available here.
+ */
+export const ontologyMergeNode = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/nodes/{node_id}/merge',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * List relations
+ *
+ * Read the facts in the graph and obtain relation ids for retrieval, invalidation or spreading. Filter by endpoint node, by type and by direction; as_of reads the relations as they were then. Invalidated relations are omitted unless include_invalid is true. limit is 1–100 and defaults to 50; follow next_cursor until it is null.
+ */
+export const ontologyListRelations = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/relations',
+    ...options
+});
+/**
+ * Create relation
+ *
+ * Record one fact between two existing nodes, for a system mirroring a relationship it owns. type must be registered and must admit these endpoints; fact states the relationship in one sentence. Send an Idempotency-Key header; repeating the same key returns the first result instead of writing a second relation. This writes structure only; it does not give any agent a memory.
+ */
+export const ontologyCreateRelation = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/relations',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Retrieve relation
+ *
+ * Read one relation's fact and both of its clocks — valid_at and invalid_at for when it was true in the world, created_at and expired_at for when it was recorded and retired. An id from another organization, or one that never existed, answers ONTOLOGY_EDGE_NOT_FOUND.
+ */
+export const ontologyRetrieveRelation = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/relations/{relation_id}',
+    ...options
+});
+/**
+ * Invalidate relation
+ *
+ * Mark a relation as no longer true from a world time, when the mirrored record changed. The relation is kept — invalid_at moves and the relation still reads at an earlier as_of, so history stays answerable. Send an Idempotency-Key header; repeating the same key replays the first result. There is no delete.
+ */
+export const ontologyInvalidateRelation = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/relations/{relation_id}/invalidate',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Apply changeset
+ *
+ * Apply a batch of node, relation and invalidation operations as one transaction, when a mirror has several records to write together and a partial write would leave the graph inconsistent. Every operation succeeds or none is applied. Send an Idempotency-Key header; the same key with the same content replays the first result, and the same key with different content is ONTOLOGY_CONFLICT.
+ */
+export const ontologyApplyChangeset = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/changesets',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Search nodes
+ *
+ * Resolve text to the nodes it most likely names, when a mirror holds a name and needs the node id it corresponds to. Results are ranked candidates, not an answer, each reporting whether the match came from the node's name, an alias, its description or a relation's fact. Narrow with types, and cap the result count with limit (1–50, default 20). This reads structure; it is not an agent's recall, which reads the graph from that agent's own viewpoint inside its sessions.
+ */
+export const ontologySearch = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'ontology-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/ontology/v1/search',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * List sandboxes (v2)
+ *
+ * List your running and paused sandboxes with paging and filters. Use it to find a sandboxID before connecting to, pausing or killing a sandbox. Filter by state, template (id or alias), name, metadata (key=value pairs joined with &) and startedAfter; order sorts by start time (default newest first); limit is 1 to 100 (default 100). When more results exist the response carries an x-next-token header; send it back as nextToken for the next page. To read one sandbox use getSandbox.
+ */
+export const getSandboxV1Sandboxes = (options) => (options?.client ?? client).get({
+    querySerializer: { parameters: { state: { array: { explode: false } } } },
+    security: [
+        {
+            key: 'sandbox-ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AuthProviderBearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        },
+        {
+            key: 'sandbox-AuthProviderTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        { name: 'X-Admin-Token', type: 'apiKey' },
+        {
+            key: 'sandbox-AdminTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AdminJWTAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }
+    ],
     url: '/sandbox/v1/sandboxes',
     ...options
 });
 /**
  * Create sandbox (v2)
  *
- * Create a sandbox from the template. All system communication with the sandbox is secured.
+ * Create a sandbox from a template. Every sandbox declares its lifecycle at creation. On the own face (X-Praxis-Face: own-v1) send ephemeral: true for an ephemeral sandbox (never pauses, cannot be snapshotted, deleted when it ends; for jobs such as transcodes, scripts and builds) or ephemeral: false for a persistent one (pauses and resumes, snapshots, mounts volumes, kept after it stops; for long-lived computers). Leaving ephemeral out returns INVALID_PARAMS. autoPause: true, onExpire: pause, autoPauseMemory, autoResume, idleTimeout, retention and volumes belong to persistent sandboxes and need ephemeral: false. Choose persistent only for long-lived computers. On the E2B-compatible face autoPause is the declaration: true is persistent, false or absent is ephemeral and ends at its timeout. Responses carry ephemeral. When a sandbox's machine has ended (timeout, kill, retention, provider loss), reaching it returns SANDBOX_EXPIRED (410) with terminationReason in the message: its files are gone, create a new sandbox.
  */
 export const postSandboxV1Sandboxes = (options) => (options.client ?? client).post({
     security: [
@@ -9162,19 +9762,212 @@ export const postSandboxV1SandboxesBySandboxIdFork = (options) => (options.clien
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/sandboxes/{sandboxID}/fork',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/sandbox/v1/sandboxes/{sandboxID}/fork',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Create snapshot
+ *
+ * Create a persistent snapshot from the sandbox's current state. Snapshots can be used to create new sandboxes and persist beyond the original sandbox's lifetime.
+ */
+export const postSandboxV1SandboxesBySandboxIdSnapshots = (options) => (options.client ?? client).post({
+    security: [
+        {
+            key: 'sandbox-ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AuthProviderBearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        },
+        {
+            key: 'sandbox-AuthProviderTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        { name: 'X-Admin-Token', type: 'apiKey' },
+        {
+            key: 'sandbox-AdminTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AdminJWTAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }
+    ],
+    url: '/sandbox/v1/sandboxes/{sandboxID}/snapshots',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * List snapshots
+ *
+ * List the snapshots you created, one cursor page at a time. Use it to find a snapshot id before you create a sandbox from it or delete it. Filter by sandboxID (the source sandbox) or by name or snapshot id, optionally tag-qualified; limit is 1 to 100 (default 100). When more results exist send the cursor from the response back as nextToken.
+ */
+export const getSandboxV1Snapshots = (options) => (options?.client ?? client).get({
+    security: [
+        {
+            key: 'sandbox-ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AuthProviderBearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        },
+        {
+            key: 'sandbox-AuthProviderTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        { name: 'X-Admin-Token', type: 'apiKey' },
+        {
+            key: 'sandbox-AdminTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AdminJWTAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }
+    ],
+    url: '/sandbox/v1/snapshots',
+    ...options
+});
+/**
+ * Delete template
+ *
+ * Delete one of your snapshots. Sandboxes already created from it keep running; no new sandbox can be created from it afterwards. Success answers 204. A snapshot that does not exist or belongs to someone else answers 404.
+ */
+export const deleteSandboxV1SnapshotsBySnapshotId = (options) => (options.client ?? client).delete({
+    security: [
+        {
+            key: 'sandbox-ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AuthProviderBearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        },
+        {
+            key: 'sandbox-AuthProviderTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        { name: 'X-Admin-Token', type: 'apiKey' },
+        {
+            key: 'sandbox-AdminTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AdminJWTAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }
+    ],
+    url: '/sandbox/v1/snapshots/{snapshotID}',
+    ...options
+});
+/**
+ * Update sandbox network
+ *
+ * Update the network configuration for a running sandbox. Replaces the current egress rules with the provided configuration. Omitting field clears it.
+ */
+export const putSandboxV1SandboxesBySandboxIdNetwork = (options) => (options.client ?? client).put({
+    security: [
+        {
+            key: 'sandbox-ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AuthProviderBearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        },
+        {
+            key: 'sandbox-AuthProviderTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        { name: 'X-Admin-Token', type: 'apiKey' },
+        {
+            key: 'sandbox-AdminTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AdminJWTAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }
+    ],
+    url: '/sandbox/v1/sandboxes/{sandboxID}/network',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Sandbox logs (v2)
+ *
+ * Read the log lines of a sandbox. Use it to debug what ran inside a sandbox. cursor is a start timestamp in milliseconds, direction chooses forward or backward from it, level sets the lowest level to return, search is a case-sensitive substring filter (at most 256 characters) and limit caps the count (at most 1000, default 1000). To continue, pass the timestamp of the last entry as the next cursor.
+ */
+export const getSandboxV1SandboxesBySandboxIdLogs = (options) => (options.client ?? client).get({
+    security: [
+        {
+            key: 'sandbox-ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AuthProviderBearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        },
+        {
+            key: 'sandbox-AuthProviderTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        { name: 'X-Admin-Token', type: 'apiKey' },
+        {
+            key: 'sandbox-AdminTeamAuth',
+            name: 'X-Team-ID',
+            type: 'apiKey'
+        },
+        {
+            key: 'sandbox-AdminJWTAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }
+    ],
+    url: '/sandbox/v1/sandboxes/{sandboxID}/logs',
+    ...options
 });
 /**
- * Create snapshot
+ * Start template build (v2)
  *
- * Create a persistent snapshot from the sandbox's current state. Snapshots can be used to create new sandboxes and persist beyond the original sandbox's lifetime.
+ * Submit source for a waiting build returned by templates.create; returns 202 after queueing, not after successful publication. Unlike E2B, COPY is rejected (use RUN curl or git clone), fromTemplate accepts official catalog names only, and plaintext registry credentials are rejected. The own face also accepts dockerfile, mutually exclusive with fromImage/fromTemplate/steps, and fromImageRegistry vault references for nonofficial images. Poll templates.builds.status.list until ready or error. Example: {"fromImage":"node:22","steps":[{"type":"RUN","args":["echo hello"]}]}.
  */
-export const postSandboxV1SandboxesBySandboxIdSnapshots = (options) => (options.client ?? client).post({
+export const startTemplateBuild = (options) => (options.client ?? client).post({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9203,7 +9996,7 @@ export const postSandboxV1SandboxesBySandboxIdSnapshots = (options) => (options.
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/sandboxes/{sandboxID}/snapshots',
+    url: '/sandbox/v1/templates/{templateID}/builds/{buildID}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9211,11 +10004,11 @@ export const postSandboxV1SandboxesBySandboxIdSnapshots = (options) => (options.
     }
 });
 /**
- * List snapshots
+ * Template build status
  *
- * List the snapshots you created, one cursor page at a time. Use it to find a snapshot id before you create a sandbox from it or delete it. Filter by sandboxID (the source sandbox) or by name or snapshot id, optionally tag-qualified; limit is 1 to 100 (default 100). When more results exist send the cursor from the response back as nextToken.
+ * Poll a build using templateID and buildID from templates.create. waiting means source has not been submitted; building includes queued work; ready permits sandbox creation; error is terminal, with reason when available. logsOffset counts previously read log entries, starting at zero; add logEntries.length after each response. limit is 0–100, default 100. level selects one log level; offsets then count entries at that level. Drain logs until an empty page, including after a terminal status.
  */
-export const getSandboxV1Snapshots = (options) => (options?.client ?? client).get({
+export const getTemplateBuildStatus = (options) => (options.client ?? client).get({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9244,15 +10037,15 @@ export const getSandboxV1Snapshots = (options) => (options?.client ?? client).ge
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/snapshots',
+    url: '/sandbox/v1/templates/{templateID}/builds/{buildID}/status',
     ...options
 });
 /**
  * Delete template
  *
- * Delete one of your snapshots. Sandboxes already created from it keep running; no new sandbox can be created from it afterwards. Success answers 204. A snapshot that does not exist or belongs to someone else answers 404.
+ * Permanently remove your template, its builds and tag assignments using templateID from templates.create. Active instances prevent deletion with 409; terminate them first. Unknown or other-organization IDs return 404. Snapshot IDs use snapshots.delete instead.
  */
-export const deleteSandboxV1SnapshotsBySnapshotId = (options) => (options.client ?? client).delete({
+export const deleteUserTemplate = (options) => (options.client ?? client).delete({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9281,15 +10074,15 @@ export const deleteSandboxV1SnapshotsBySnapshotId = (options) => (options.client
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/snapshots/{snapshotID}',
+    url: '/sandbox/v1/templates/{templateID}',
     ...options
 });
 /**
- * Update sandbox network
+ * List template builds
  *
- * Update the network configuration for a running sandbox. Replaces the current egress rules with the provided configuration. Omitting field clears it.
+ * Inspect your template and its newest builds using templateID from templates.create. Build states are waiting, building, ready or error. Use limit and the returned x-next-token header to page builds. Unknown or other-organization templates return 404.
  */
-export const putSandboxV1SandboxesBySandboxIdNetwork = (options) => (options.client ?? client).put({
+export const getTemplateWithBuilds = (options) => (options.client ?? client).get({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9318,19 +10111,15 @@ export const putSandboxV1SandboxesBySandboxIdNetwork = (options) => (options.cli
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/sandboxes/{sandboxID}/network',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/sandbox/v1/templates/{templateID}',
+    ...options
 });
 /**
- * Sandbox logs (v2)
+ * Delete template tags
  *
- * Read the log lines of a sandbox. Use it to debug what ran inside a sandbox. cursor is a start timestamp in milliseconds, direction chooses forward or backward from it, level sets the lowest level to return, search is a case-sensitive substring filter (at most 256 characters) and limit caps the count (at most 1000, default 1000). To continue, pass the timestamp of the last entry as the next cursor.
+ * Remove the specified tag labels from your template by name, for example {"name":"my-template","tags":["stable"]}. Builds remain available. Removing default means untagged sandbox creation no longer resolves this template. Unknown or other-organization names return 404. b<number> names are reserved read-only build aliases and cannot be assigned or deleted as tags.
  */
-export const getSandboxV1SandboxesBySandboxIdLogs = (options) => (options.client ?? client).get({
+export const deleteTemplateTags = (options) => (options.client ?? client).delete({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9359,15 +10148,19 @@ export const getSandboxV1SandboxesBySandboxIdLogs = (options) => (options.client
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/sandboxes/{sandboxID}/logs',
-    ...options
+    url: '/sandbox/v1/templates/tags',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Start template build (v2)
+ * Assign template tags
  *
- * Submit source for a waiting build returned by templates.create; returns 202 after queueing, not after successful publication. Unlike E2B, COPY is rejected (use RUN curl or git clone), fromTemplate accepts official catalog names only, and plaintext registry credentials are rejected. The own face also accepts dockerfile, mutually exclusive with fromImage/fromTemplate/steps, and fromImageRegistry vault references for nonofficial images. Poll templates.builds.status.list until ready or error. Example: {"fromImage":"node:22","steps":[{"type":"RUN","args":["echo hello"]}]}.
+ * Assign tags to the ready build selected by target in name:tag format, for example {"target":"my-template:default","tags":["stable"]}. Names belong to your organization. Tags move an existing label to this build without rebuilding. Obtain available names from templates.list and tags from templates.tags.list. b<number> names are reserved read-only build aliases and cannot be assigned or deleted as tags. target also accepts name:b<number> to select a ready build by number, for example my-template:b1.
  */
-export const startTemplateBuild = (options) => (options.client ?? client).post({
+export const assignTemplateTags = (options) => (options.client ?? client).post({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9396,7 +10189,7 @@ export const startTemplateBuild = (options) => (options.client ?? client).post({
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/templates/{templateID}/builds/{buildID}',
+    url: '/sandbox/v1/templates/tags',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9404,11 +10197,11 @@ export const startTemplateBuild = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Template build status
+ * List template tags
  *
- * Poll a build using templateID and buildID from templates.create. waiting means source has not been submitted; building includes queued work; ready permits sandbox creation; error is terminal, with reason when available. logsOffset counts previously read log entries, starting at zero; add logEntries.length after each response. limit is 0–100, default 100. level selects one log level; offsets then count entries at that level. Drain logs until an empty page, including after a terminal status.
+ * Read the tag-to-build assignments for your template using templateID from templates.create. Only ready builds acquire tags. Use a returned tag with the template name as name:tag when creating a sandbox or assigning additional tags. Foreign IDs return 404.
  */
-export const getTemplateBuildStatus = (options) => (options.client ?? client).get({
+export const listTemplateTags = (options) => (options.client ?? client).get({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9437,15 +10230,15 @@ export const getTemplateBuildStatus = (options) => (options.client ?? client).ge
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/templates/{templateID}/builds/{buildID}/status',
+    url: '/sandbox/v1/templates/{templateID}/tags',
     ...options
 });
 /**
- * Delete template
+ * Check template alias
  *
- * Permanently remove your template, its builds and tag assignments using templateID from templates.create. Active instances prevent deletion with 409; terminate them first. Unknown or other-organization IDs return 404. Snapshot IDs use snapshots.delete instead.
+ * Resolve a name within your organization to its templateID before reading or managing builds. Use the bare template name, without a :tag suffix. Unknown and other-organization names return 404. The response public field is false for your private templates.
  */
-export const deleteUserTemplate = (options) => (options.client ?? client).delete({
+export const resolveTemplateAlias = (options) => (options.client ?? client).get({
     security: [
         {
             key: 'sandbox-ApiKeyAuth',
@@ -9474,81 +10267,187 @@ export const deleteUserTemplate = (options) => (options.client ?? client).delete
             type: 'http'
         }
     ],
-    url: '/sandbox/v1/templates/{templateID}',
+    url: '/sandbox/v1/templates/aliases/{alias}',
     ...options
 });
 /**
- * List template builds
+ * Search for data based on a query
  *
- * Inspect your template and its newest builds using templateID from templates.create. Build states are waiting, building, ready or error. Use limit and the returned x-next-token header to page builds. Unknown or other-organization templates return 404.
+ * Search the web and return ranked results with extracted content. Use it to answer questions with current information; to read the full text of known URLs use searchExtract, to walk a site use searchCrawl and to list a site's URLs use searchMap. query is required. topic chooses general, news or finance; time_range limits results to the last day, week, month or year; country boosts results from one country (topic general only). Each result carries title, url, content and a relevance score, and the response can include a generated answer, images and follow-up questions when requested.
  */
-export const getTemplateWithBuilds = (options) => (options.client ?? client).get({
-    security: [
-        {
-            key: 'sandbox-ApiKeyAuth',
+export const searchSearch = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'search-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/search/v1/search',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Retrieve raw web content from specified URLs
+ *
+ * Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_results. Check both arrays even when the response is HTTP 200. Request options apply to every URL in the batch.
+ */
+export const searchExtract = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'search-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/search/v1/extract',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Initiate a web crawl from a base URL
+ *
+ * Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent discovery.
+ */
+export const searchCrawl = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'search-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/search/v1/crawl',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * Initiate a web mapping from a base URL
+ *
+ * Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensive site maps.
+ */
+export const searchMap = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'search-bearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }],
+    url: '/search/v1/map',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * List the genres Studio can write
+ *
+ * List the genre catalog so you can choose how a piece is structured before creating a draft. Each genre names its unit kinds, draft properties, deterministic checks and writing rules, and by default only the genres open today are returned. Read the chosen genre in full with studioGenresGet before the first write, because its kinds and limits decide what that draft accepts.
+ */
+export const studioGenresList = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
             name: 'X-API-Key',
             type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AuthProviderBearerAuth',
+        }],
+    url: '/studio/v1/genres',
+    ...options
+});
+/**
+ * Read one genre with its built-in templates
+ *
+ * Read the full rules of one genre: its unit kinds and what each may contain, the draft properties with their limits, the deterministic checks the software runs, the semantic review list, and the built-in templates that can seed a draft. Ask for this before creating a draft of that genre, and again when a write is refused for an unknown kind, a property limit or a block type the genre does not allow.
+ */
+export const studioGenresGet = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        },
-        {
-            key: 'sandbox-AuthProviderTeamAuth',
-            name: 'X-Team-ID',
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
             type: 'apiKey'
-        },
-        { name: 'X-Admin-Token', type: 'apiKey' },
-        {
-            key: 'sandbox-AdminTeamAuth',
-            name: 'X-Team-ID',
+        }],
+    url: '/studio/v1/genres/{genre}',
+    ...options
+});
+/**
+ * List the platforms a work can be produced for
+ *
+ * List rendition targets with the format each needs, whether it receives a finished piece through an API, a draft box or an export, and the hard limits a piece must respect. Pass a genre to see only the platforms that genre produces by default. Read one platform in full before rendering, because its limits decide whether the rendition validates.
+ */
+export const studioPlatformsList = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
             type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AdminJWTAuth',
+        }],
+    url: '/studio/v1/platforms',
+    ...options
+});
+/**
+ * Read the rules of one platform
+ *
+ * Read one platform in full: the format it consumes, how it receives a finished piece, the preview fidelity the Console can offer, the limits on title, body, image count and aspect, and whether a connected channel is required. Read this before creating a rendition, and again when validation reports that the piece breaks a platform limit.
+ */
+export const studioPlatformsGet = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        }
-    ],
-    url: '/sandbox/v1/templates/{templateID}',
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/platforms/{platform}',
+    ...options
+});
+/**
+ * List the works of this organization
+ *
+ * List works owned by the API key organization so you can find the one being discussed, with its drafts and how long ago each moved. Archived works are left out unless you ask for them. Continue with next_page_token until the answer stops carrying one; the summaries carry no unit bodies, so read a work before writing in it.
+ */
+export const studioWorksList = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/works',
     ...options
 });
 /**
- * Delete template tags
+ * Create a work with its goal
  *
- * Remove the specified tag labels from your template by name, for example {"name":"my-template","tags":["stable"]}. Builds remain available. Removing default means untagged sandbox creation no longer resolves this template. Unknown or other-organization names return 404. b<number> names are reserved read-only build aliases and cannot be assigned or deleted as tags.
+ * Create a work: one deliverable piece plus everything around it. Pass the goal the writing serves — the reader, what that reader should get or do, the one-sentence message and the constraints — and the original brief the person gave in their own words. A slug is derived from the title unless you pass one. The work starts with no drafts; create the first one with the drafts create call, because the genre decides the structure.
  */
-export const deleteTemplateTags = (options) => (options.client ?? client).delete({
-    security: [
-        {
-            key: 'sandbox-ApiKeyAuth',
-            name: 'X-API-Key',
-            type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AuthProviderBearerAuth',
+export const studioWorksCreate = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        },
-        {
-            key: 'sandbox-AuthProviderTeamAuth',
-            name: 'X-Team-ID',
-            type: 'apiKey'
-        },
-        { name: 'X-Admin-Token', type: 'apiKey' },
-        {
-            key: 'sandbox-AdminTeamAuth',
-            name: 'X-Team-ID',
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
             type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AdminJWTAuth',
-            scheme: 'bearer',
-            type: 'http'
-        }
-    ],
-    url: '/sandbox/v1/templates/tags',
+        }],
+    url: '/studio/v1/works',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9556,40 +10455,57 @@ export const deleteTemplateTags = (options) => (options.client ?? client).delete
     }
 });
 /**
- * Assign template tags
+ * Resolve a loose reference to a work, draft or unit
  *
- * Assign tags to the ready build selected by target in name:tag format, for example {"target":"my-template:default","tags":["stable"]}. Names belong to your organization. Tags move an existing label to this build without rebuilding. Obtain available names from templates.list and tags from templates.tags.list. b<number> names are reserved read-only build aliases and cannot be assigned or deleted as tags. target also accepts name:b<number> to select a ready build by number, for example my-template:b1.
+ * Turn a loose reference into the address the other calls take: a slug, a work title, a draft key or a unit number, as a person or another tool would say it. A hit answers the work slug and, when the reference pointed deeper, the draft key and unit number; a miss answers an empty resolved value with up to three near matches instead of failing. Use it when a person names something instead of an id.
  */
-export const assignTemplateTags = (options) => (options.client ?? client).post({
-    security: [
-        {
-            key: 'sandbox-ApiKeyAuth',
+export const studioWorksResolve = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
             name: 'X-API-Key',
             type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AuthProviderBearerAuth',
+        }],
+    url: '/studio/v1/works:resolve',
+    ...options
+});
+/**
+ * Read a work, optionally with one draft and unit
+ *
+ * Read a work and, in the same answer, whatever part of it the page needs: pass draft to get that draft with its todos, its unit outline and its properties, and unit to get one unit with its blocks and Markdown body. This is the call that opens an editing session, because it answers the goal, the brief, the current revisions and the unit to write in one round trip.
+ */
+export const studioWorksGet = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        },
-        {
-            key: 'sandbox-AuthProviderTeamAuth',
-            name: 'X-Team-ID',
-            type: 'apiKey'
-        },
-        { name: 'X-Admin-Token', type: 'apiKey' },
-        {
-            key: 'sandbox-AdminTeamAuth',
-            name: 'X-Team-ID',
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
             type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AdminJWTAuth',
+        }],
+    url: '/studio/v1/works/{work}',
+    ...options
+});
+/**
+ * Change the title, goal or attached libraries
+ *
+ * Change work-level settings: the title, the slug, the goal, the attached reference libraries, the style or the archived flag. Send update_mask naming exactly the fields you change; a field left out keeps its value. Pass expected_revision to have the write refused when someone else changed the work first, and note that changing the message makes every draft derived from it stale.
+ */
+export const studioWorksUpdate = (options) => (options.client ?? client).patch({
+    security: [{
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        }
-    ],
-    url: '/sandbox/v1/templates/tags',
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/works/{work}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9597,91 +10513,61 @@ export const assignTemplateTags = (options) => (options.client ?? client).post({
     }
 });
 /**
- * List template tags
+ * Add to or correct the original brief
  *
- * Read the tag-to-build assignments for your template using templateID from templates.create. Only ready builds acquire tags. Use a returned tag with the template name as name:tag when creating a sandbox or assigning additional tags. Foreign IDs return 404.
+ * Extend the original brief: append text, attach files, add points taken from an outline, edit one point, or drop a point. Points are how the software checks that every requirement landed in a written unit, so split the person's outline into points here rather than burying them in prose. The brief carries its own revision, separate from the work and from each draft.
  */
-export const listTemplateTags = (options) => (options.client ?? client).get({
-    security: [
-        {
-            key: 'sandbox-ApiKeyAuth',
-            name: 'X-API-Key',
-            type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AuthProviderBearerAuth',
+export const studioWorksUpdateBrief = (options) => (options.client ?? client).patch({
+    security: [{
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        },
-        {
-            key: 'sandbox-AuthProviderTeamAuth',
-            name: 'X-Team-ID',
-            type: 'apiKey'
-        },
-        { name: 'X-Admin-Token', type: 'apiKey' },
-        {
-            key: 'sandbox-AdminTeamAuth',
-            name: 'X-Team-ID',
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
             type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AdminJWTAuth',
-            scheme: 'bearer',
-            type: 'http'
-        }
-    ],
-    url: '/sandbox/v1/templates/{templateID}/tags',
-    ...options
+        }],
+    url: '/studio/v1/works/{work}/brief',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Check template alias
+ * List the drafts a work carries
  *
- * Resolve a name within your organization to its templateID before reading or managing builds. Use the bare template name, without a :tag suffix. Unknown and other-organization names return 404. The response public field is false for your private templates.
+ * List every draft of one work, each with its genre, its size and whether it is out of date against what it was derived from. Use it to choose the draft a later call works in: the key beside each draft is what the draft path segment takes. This list is not paged, because a work carries a handful of drafts rather than thousands.
  */
-export const resolveTemplateAlias = (options) => (options.client ?? client).get({
-    security: [
-        {
-            key: 'sandbox-ApiKeyAuth',
-            name: 'X-API-Key',
-            type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AuthProviderBearerAuth',
+export const studioDraftsList = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        },
-        {
-            key: 'sandbox-AuthProviderTeamAuth',
-            name: 'X-Team-ID',
-            type: 'apiKey'
-        },
-        { name: 'X-Admin-Token', type: 'apiKey' },
-        {
-            key: 'sandbox-AdminTeamAuth',
-            name: 'X-Team-ID',
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
             type: 'apiKey'
-        },
-        {
-            key: 'sandbox-AdminJWTAuth',
-            scheme: 'bearer',
-            type: 'http'
-        }
-    ],
-    url: '/sandbox/v1/templates/aliases/{alias}',
+        }],
+    url: '/studio/v1/works/{work}/drafts',
     ...options
 });
 /**
- * Search for data based on a query
+ * Create a draft of a genre inside a work
  *
- * Search the web and return ranked results with extracted content. Use it to answer questions with current information; to read the full text of known URLs use searchExtract, to walk a site use searchCrawl and to list a site's URLs use searchMap. query is required. topic chooses general, news or finance; time_range limits results to the last day, week, month or year; country boosts results from one country (topic general only). Each result carries title, url, content and a relevance score, and the response can include a generated answer, images and follow-up questions when requested.
+ * Create a draft: one way of delivering the work, written in one genre. The genre decides the unit kinds, the properties and the checks, so read it first with the genre call and pass its key. A template may seed the unit tree, an outline may be given instead, and derived_from records that this draft is built from the goal message or from another draft of the work. The work may hold several drafts, one per platform or per length.
  */
-export const searchSearch = (options) => (options.client ?? client).post({
+export const studioDraftsCreate = (options) => (options.client ?? client).post({
     security: [{
-            key: 'search-bearerAuth',
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
         }],
-    url: '/search/v1/search',
+    url: '/studio/v1/works/{work}/drafts',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9689,35 +10575,39 @@ export const searchSearch = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Retrieve raw web content from specified URLs
+ * Read one draft with optional units and todos
  *
- * Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_results. Check both arrays even when the response is HTTP 200. Request options apply to every URL in the batch.
+ * Read one draft: its genre, its properties, its revisions, whether it is stale, and optionally its unit tree and its todo list. Pass expand to add the parts you need in this one call instead of reading them separately. Read this before writing to the draft, because the revision it returns is the precondition the next write has to carry.
  */
-export const searchExtract = (options) => (options.client ?? client).post({
+export const studioDraftsGet = (options) => (options.client ?? client).get({
     security: [{
-            key: 'search-bearerAuth',
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
         }],
-    url: '/search/v1/extract',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/studio/v1/works/{work}/drafts/{draft}',
+    ...options
 });
 /**
- * Initiate a web crawl from a base URL
+ * Change a draft title, key, properties or style
  *
- * Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent discovery.
+ * Change the draft itself rather than its units: its page title, its in-work key, its generic properties, the style that overrides the work style, or its mode. Send update_mask naming exactly the fields you change. Changing the key keeps the previous one resolving, so old links and old references still work; a key another draft of the work already uses answers DRAFT_KEY_TAKEN.
  */
-export const searchCrawl = (options) => (options.client ?? client).post({
+export const studioDraftsUpdate = (options) => (options.client ?? client).patch({
     security: [{
-            key: 'search-bearerAuth',
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
         }],
-    url: '/search/v1/crawl',
+    url: '/studio/v1/works/{work}/drafts/{draft}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9725,29 +10615,29 @@ export const searchCrawl = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Initiate a web mapping from a base URL
+ * Read the whole unit outline as Markdown
  *
- * Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensive site maps.
+ * Read the draft structure as one Markdown page: one line per unit carrying its number, structure name, intent, status, length and revision, followed by the unit list itself. Use it to plan a sequence of writes without reading every unit, since it carries no body text. Read one unit in full with the unit call once you know which one to write.
  */
-export const searchMap = (options) => (options.client ?? client).post({
+export const studioDraftsOutline = (options) => (options.client ?? client).get({
     security: [{
-            key: 'search-bearerAuth',
+            key: 'BearerAuth',
             scheme: 'bearer',
             type: 'http'
-        }],
-    url: '/search/v1/map',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/works/{work}/drafts/{draft}/outline',
+    ...options
 });
 /**
- * List the genres Studio can write
+ * Read the computed todo list of a draft
  *
- * List the genre catalog so you can choose how a piece is structured before creating a draft. Each genre names its unit kinds, draft properties, deterministic checks and writing rules, and by default only the genres open today are returned. Read the chosen genre in full with studioGenresGet before the first write, because its kinds and limits decide what that draft accepts.
+ * Read what is outstanding in one draft, computed from the data rather than from a plan: a unit without an intent, a body behind its intent, an unclaimed brief point, a failed check, a stale rendition. Each item names the layer it belongs to and suggests the call that resolves it. Follow the list instead of inventing an order, and re-read it after a batch of writes.
  */
-export const studioGenresList = (options) => (options?.client ?? client).get({
+export const studioDraftsStatus = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9757,15 +10647,15 @@ export const studioGenresList = (options) => (options?.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/genres',
+    url: '/studio/v1/works/{work}/drafts/{draft}/status',
     ...options
 });
 /**
- * Read one genre with its built-in templates
+ * Read a review pass over the whole draft
  *
- * Read the full rules of one genre: its unit kinds and what each may contain, the draft properties with their limits, the deterministic checks the software runs, the semantic review list, and the built-in templates that can seed a draft. Ask for this before creating a draft of that genre, and again when a write is refused for an unknown kind, a property limit or a block type the genre does not allow.
+ * Read everything a reviewer needs in one answer: the deterministic check results, the semantic review list the genre asks a reader to judge, the brief coverage showing which unit claims each requirement point, and the body text. When the draft is long the body is a synopsis with an excerpt around each unit and next_page_token carries the full text. This is the call an agent makes before writing review comments.
  */
-export const studioGenresGet = (options) => (options.client ?? client).get({
+export const studioDraftsReview = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9775,15 +10665,15 @@ export const studioGenresGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/genres/{genre}',
+    url: '/studio/v1/works/{work}/drafts/{draft}/review',
     ...options
 });
 /**
- * List the platforms a work can be produced for
+ * Confirm a draft already follows its source
  *
- * List rendition targets with the format each needs, whether it receives a finished piece through an API, a draft box or an export, and the hard limits a piece must respect. Pass a genre to see only the platforms that genre produces by default. Read one platform in full before rendering, because its limits decide whether the rendition validates.
+ * Clear the stale flag after checking that the draft still matches what it was derived from: the recorded source revision moves to the source current revision without touching any unit. Call it after the source moved and you have brought this draft up to date, not to make the flag disappear while the text is still behind. It answers the same shape as a draft write, and the draft revision does not move.
  */
-export const studioPlatformsList = (options) => (options?.client ?? client).get({
+export const studioDraftsRebase = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9793,15 +10683,19 @@ export const studioPlatformsList = (options) => (options?.client ?? client).get(
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/platforms',
-    ...options
+    url: '/studio/v1/works/{work}/drafts/{draft}:rebase',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Read the rules of one platform
+ * Export the draft as Markdown or plain text
  *
- * Read one platform in full: the format it consumes, how it receives a finished piece, the preview fidelity the Console can offer, the limits on title, body, image count and aspect, and whether a connected channel is required. Read this before creating a rendition, and again when validation reports that the piece breaks a platform limit.
+ * Read the whole draft as one document in Markdown or plain text, returned synchronously in the answer. This is the quick path for a person who wants the text now; a file in a platform format, a card image or a docx comes from creating a rendition instead. Ask for text rather than markdown when the reader should not see block anchors or heading syntax.
  */
-export const studioPlatformsGet = (options) => (options.client ?? client).get({
+export const studioDraftsExport = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9811,15 +10705,15 @@ export const studioPlatformsGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/platforms/{platform}',
+    url: '/studio/v1/works/{work}/drafts/{draft}/export',
     ...options
 });
 /**
- * List the works of this organization
+ * Add one unit to the draft tree
  *
- * List works owned by the API key organization so you can find the one being discussed, with its drafts and how long ago each moved. Archived works are left out unless you ask for them. Continue with next_page_token until the answer stops carrying one; the summaries carry no unit bodies, so read a work before writing in it.
+ * Add a unit to the structure: a chapter, a scene, a section, an argument or a product depending on the genre. Say where it goes with parent and after, give it the structure name people will use to manage it, and write the intent that says what it has to accomplish. Adding a unit changes the draft revision, so pass expected_revision, and the new unit itself starts with no body.
  */
-export const studioWorksList = (options) => (options?.client ?? client).get({
+export const studioUnitsCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9829,15 +10723,19 @@ export const studioWorksList = (options) => (options?.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works',
-    ...options
+    url: '/studio/v1/works/{work}/drafts/{draft}/units',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Create a work with its goal
+ * Add a whole outline of units at once
  *
- * Create a work: one deliverable piece plus everything around it. Pass the goal the writing serves — the reader, what that reader should get or do, the one-sentence message and the constraints — and the original brief the person gave in their own words. A slug is derived from the title unless you pass one. The work starts with no drafts; create the first one with the drafts create call, because the genre decides the structure.
+ * Create many units in one write from a nested outline, which is how a structure is built after the person approved a plan. Nesting in the outline becomes the parent chain, numbers are assigned in order, and the draft gets one revision for the whole batch rather than one per unit. Sending the same outline twice would duplicate it, so pass the draft revision you read and repeat the call only after a refusal.
  */
-export const studioWorksCreate = (options) => (options.client ?? client).post({
+export const studioUnitsBatchCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9847,7 +10745,7 @@ export const studioWorksCreate = (options) => (options.client ?? client).post({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works',
+    url: '/studio/v1/works/{work}/drafts/{draft}/units:batchCreate',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9855,11 +10753,11 @@ export const studioWorksCreate = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Resolve a loose reference to a work, draft or unit
+ * Write intents for many units in one call
  *
- * Turn a loose reference into the address the other calls take: a slug, a work title, a draft key or a unit number, as a person or another tool would say it. A hit answers the work slug and, when the reference pointed deeper, the draft key and unit number; a miss answers an empty resolved value with up to three near matches instead of failing. Use it when a person names something instead of an id.
+ * Change the intent of several units in one write: the synopsis, the points and the brief points each of them claims. Bodies are not part of this call, because a body is written one unit at a time with its own revision; here the whole batch shares the draft revision you read. Use it to lay out a plan across the tree, then write bodies one by one.
  */
-export const studioWorksResolve = (options) => (options.client ?? client).get({
+export const studioUnitsBatchUpdate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9869,15 +10767,19 @@ export const studioWorksResolve = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works:resolve',
-    ...options
+    url: '/studio/v1/works/{work}/drafts/{draft}/units:batchUpdate',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Read a work, optionally with one draft and unit
+ * Read one unit with its blocks and Markdown
  *
- * Read a work and, in the same answer, whatever part of it the page needs: pass draft to get that draft with its todos, its unit outline and its properties, and unit to get one unit with its blocks and Markdown body. This is the call that opens an editing session, because it answers the goal, the brief, the current revisions and the unit to write in one round trip.
+ * Read one unit: its intent, its status, its revision, its links to reference entries, and its body as both blocks and Markdown. The Markdown carries each block identifier inline as an anchor comment, so a rewrite can keep the identifiers of the blocks it keeps. Read this before writing the body, because the revision it returns is the precondition that write has to carry.
  */
-export const studioWorksGet = (options) => (options.client ?? client).get({
+export const studioUnitsGet = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9887,15 +10789,15 @@ export const studioWorksGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}',
+    url: '/studio/v1/works/{work}/units/{unit}',
     ...options
 });
 /**
- * Change the title, goal or attached libraries
+ * Change a unit intent, body or status
  *
- * Change work-level settings: the title, the slug, the goal, the attached reference libraries, the style or the archived flag. Send update_mask naming exactly the fields you change; a field left out keeps its value. Pass expected_revision to have the write refused when someone else changed the work first, and note that changing the message makes every draft derived from it stale.
+ * Change one unit: its name, its heading, its synopsis and points, the brief points it claims, its status, its links to reference entries, or its body as a whole Markdown text. A body write requires expected_revision, because replacing the whole text would drop blocks someone else inserted. The answer carries the unit as it now stands, so read the next field of the answer instead of re-reading the unit.
  */
-export const studioWorksUpdate = (options) => (options.client ?? client).patch({
+export const studioUnitsUpdate = (options) => (options.client ?? client).patch({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9905,7 +10807,7 @@ export const studioWorksUpdate = (options) => (options.client ?? client).patch({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}',
+    url: '/studio/v1/works/{work}/units/{unit}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9913,11 +10815,11 @@ export const studioWorksUpdate = (options) => (options.client ?? client).patch({
     }
 });
 /**
- * Add to or correct the original brief
+ * Move a unit to another place in the tree
  *
- * Extend the original brief: append text, attach files, add points taken from an outline, edit one point, or drop a point. Points are how the software checks that every requirement landed in a written unit, so split the person's outline into points here rather than burying them in prose. The brief carries its own revision, separate from the work and from each draft.
+ * Move a unit under another parent or after another sibling, without changing its number, its identifier, its intent or its body. A move that would put a unit inside its own descendant, or that would cross into another draft, is refused. Only the moved unit changes, so the revision to pass is its own.
  */
-export const studioWorksUpdateBrief = (options) => (options.client ?? client).patch({
+export const studioUnitsMove = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9927,7 +10829,7 @@ export const studioWorksUpdateBrief = (options) => (options.client ?? client).pa
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/brief',
+    url: '/studio/v1/works/{work}/units/{unit}:move',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -9935,11 +10837,11 @@ export const studioWorksUpdateBrief = (options) => (options.client ?? client).pa
     }
 });
 /**
- * List the drafts a work carries
+ * Edit a unit body block by block
  *
- * List every draft of one work, each with its genre, its size and whether it is out of date against what it was derived from. Use it to choose the draft a later call works in: the key beside each draft is what the draft path segment takes. This list is not paged, because a work carries a handful of drafts rather than thousands.
+ * Change a body by naming the blocks to insert, replace or delete instead of resending the whole text. This is the safe way for a writer that only touches part of a unit, because a block another writer changed after your revision is refused rather than overwritten. The revision is required, and the answer carries the unit with its blocks so the next edit can address them.
  */
-export const studioDraftsList = (options) => (options.client ?? client).get({
+export const studioUnitsPatchBlocks = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9949,15 +10851,19 @@ export const studioDraftsList = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts',
-    ...options
+    url: '/studio/v1/works/{work}/units/{unit}/blocks:patch',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Create a draft of a genre inside a work
+ * Read the context pack for writing one unit
  *
- * Create a draft: one way of delivering the work, written in one genre. The genre decides the unit kinds, the properties and the checks, so read it first with the genre call and pass its key. A template may seed the unit tree, an outline may be given instead, and derived_from records that this draft is built from the goal message or from another draft of the work. The work may hold several drafts, one per platform or per length.
+ * Read everything a writer needs before touching one unit: the genre rules, the goal, the brief, the style, the upstream source, the reference entries this unit draws on, the synopses of the units before it, and the intent of this unit, assembled in a fixed order and measured against a token budget. Entries left out say why, so a missing detail is visible rather than silent. Same input gives the same pack, which is what makes a written result reproducible.
  */
-export const studioDraftsCreate = (options) => (options.client ?? client).post({
+export const studioUnitsContext = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9967,19 +10873,15 @@ export const studioDraftsCreate = (options) => (options.client ?? client).post({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/studio/v1/works/{work}/units/{unit}/context',
+    ...options
 });
 /**
- * Read one draft with optional units and todos
+ * List the reference libraries of this organization
  *
- * Read one draft: its genre, its properties, its revisions, whether it is stale, and optionally its unit tree and its todo list. Pass expand to add the parts you need in this one call instead of reading them separately. Read this before writing to the draft, because the revision it returns is the precondition the next write has to carry.
+ * List the reference libraries this API key organization owns, each with how many entries it holds, so you can choose the one a work draws on. Continue with next_page_token until the answer stops carrying one. A library is shared across works, so the list is the whole organization's rather than one work's.
  */
-export const studioDraftsGet = (options) => (options.client ?? client).get({
+export const studioCodexesList = (options) => (options?.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -9989,15 +10891,15 @@ export const studioDraftsGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}',
+    url: '/studio/v1/codexes',
     ...options
 });
 /**
- * Change a draft title, key, properties or style
+ * Create a reference library
  *
- * Change the draft itself rather than its units: its page title, its in-work key, its generic properties, the style that overrides the work style, or its mode. Send update_mask naming exactly the fields you change. Changing the key keeps the previous one resolving, so old links and old references still work; a key another draft of the work already uses answers DRAFT_KEY_TAKEN.
+ * Create a reference library: a shared store of the people, places, products and facts a piece draws on, reusable across works. Attach it to a work with the work update call, and the entries it holds then reach the context packs of that work's units. A library is not private to one work, so the same brand facts can serve every piece that mentions them.
  */
-export const studioDraftsUpdate = (options) => (options.client ?? client).patch({
+export const studioCodexesCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10007,7 +10909,7 @@ export const studioDraftsUpdate = (options) => (options.client ?? client).patch(
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}',
+    url: '/studio/v1/codexes',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10015,11 +10917,11 @@ export const studioDraftsUpdate = (options) => (options.client ?? client).patch(
     }
 });
 /**
- * Read the whole unit outline as Markdown
+ * Delete a reference library
  *
- * Read the draft structure as one Markdown page: one line per unit carrying its number, structure name, intent, status, length and revision, followed by the unit list itself. Use it to plan a sequence of writes without reading every unit, since it carries no body text. Read one unit in full with the unit call once you know which one to write.
+ * Delete a library and every entry inside it. A library attached to any work is refused with CODEX_IN_USE, because deleting it would silently strip the reference material those units draw on; detach it from the work first. This cannot be undone, so confirm which library the identifier names.
  */
-export const studioDraftsOutline = (options) => (options.client ?? client).get({
+export const studioCodexesDelete = (options) => (options.client ?? client).delete({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10029,15 +10931,15 @@ export const studioDraftsOutline = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}/outline',
+    url: '/studio/v1/codexes/{codex}',
     ...options
 });
 /**
- * Read the computed todo list of a draft
+ * Read one reference library
  *
- * Read what is outstanding in one draft, computed from the data rather than from a plan: a unit without an intent, a body behind its intent, an unclaimed brief point, a failed check, a stale rendition. Each item names the layer it belongs to and suggests the call that resolves it. Follow the list instead of inventing an order, and re-read it after a batch of writes.
+ * Read one reference library: its name, its description, its labels and how many entries it holds. Read this to confirm a library exists before attaching it to a work; the entries themselves are listed with the entry list call, because a library may hold more of them than fit in one answer.
  */
-export const studioDraftsStatus = (options) => (options.client ?? client).get({
+export const studioCodexesGet = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10047,15 +10949,15 @@ export const studioDraftsStatus = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}/status',
+    url: '/studio/v1/codexes/{codex}',
     ...options
 });
 /**
- * Read a review pass over the whole draft
+ * Rename a reference library or change its description
  *
- * Read everything a reviewer needs in one answer: the deterministic check results, the semantic review list the genre asks a reader to judge, the brief coverage showing which unit claims each requirement point, and the body text. When the draft is long the body is a synopsis with an excerpt around each unit and next_page_token carries the full text. This is the call an agent makes before writing review comments.
+ * Change the library itself: its name, its description or its labels. Send update_mask naming exactly the fields you change; a field left out keeps its value. The entries inside are untouched, and a work that has the library attached keeps it attached under the new name.
  */
-export const studioDraftsReview = (options) => (options.client ?? client).get({
+export const studioCodexesUpdate = (options) => (options.client ?? client).patch({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10065,15 +10967,37 @@ export const studioDraftsReview = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}/review',
+    url: '/studio/v1/codexes/{codex}',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
+});
+/**
+ * List the entries of a reference library
+ *
+ * List the entries of one library in pages, each with its type, its name, its aliases and whether it is always present in context. Use it to see what a work already knows before adding an entry, since a duplicate name is refused rather than merged. Continue with next_page_token until the answer stops carrying one.
+ */
+export const studioEntriesList = (options) => (options.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/codexes/{codex}/entries',
     ...options
 });
 /**
- * Confirm a draft already follows its source
+ * Add an entry to a reference library
  *
- * Clear the stale flag after checking that the draft still matches what it was derived from: the recorded source revision moves to the source current revision without touching any unit. Call it after the source moved and you have brought this draft up to date, not to make the flag disappear while the text is still behind. It answers the same shape as a draft write, and the draft revision does not move.
+ * Add one entry: a character, a place, a product, a source of facts. Give it the type the genre uses, the name the text will mention, and the description and facts that should reach a writer when it is mentioned. Aliases and excluded phrases keep detection honest, so a common word inside an idiom is not mistaken for the entry. A name already used in the library is refused.
  */
-export const studioDraftsRebase = (options) => (options.client ?? client).post({
+export const studioEntriesCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10083,7 +11007,7 @@ export const studioDraftsRebase = (options) => (options.client ?? client).post({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}:rebase',
+    url: '/studio/v1/codexes/{codex}/entries',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10091,11 +11015,11 @@ export const studioDraftsRebase = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Export the draft as Markdown or plain text
+ * Delete a reference entry
  *
- * Read the whole draft as one document in Markdown or plain text, returned synchronously in the answer. This is the quick path for a person who wants the text now; a file in a platform format, a card image or a docx comes from creating a rendition instead. Ask for text rather than markdown when the reader should not see block anchors or heading syntax.
+ * Delete one entry from a library, which also removes the mentions and the links that pointed at it. Units that claimed it keep their text; only the reference goes away. This cannot be undone, so confirm the name of the entry before deleting it, and prefer changing its tracking setting to never when it should stop reaching writers but stay recorded.
  */
-export const studioDraftsExport = (options) => (options.client ?? client).get({
+export const studioEntriesDelete = (options) => (options.client ?? client).delete({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10105,15 +11029,15 @@ export const studioDraftsExport = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}/export',
+    url: '/studio/v1/codexes/{codex}/entries/{entry}',
     ...options
 });
 /**
- * Add one unit to the draft tree
+ * Read one reference entry
  *
- * Add a unit to the structure: a chapter, a scene, a section, an argument or a product depending on the genre. Say where it goes with parent and after, give it the structure name people will use to manage it, and write the intent that says what it has to accomplish. Adding a unit changes the draft revision, so pass expected_revision, and the new unit itself starts with no body.
+ * Read one entry in full: its description, its fact ledger, its relations to other entries, its detection settings and its images. Read it before changing it, because an update replaces the fields it names rather than merging them. The entry is addressed by its name in this library, or by its ent_ identifier.
  */
-export const studioUnitsCreate = (options) => (options.client ?? client).post({
+export const studioEntriesGet = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10123,7 +11047,25 @@ export const studioUnitsCreate = (options) => (options.client ?? client).post({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}/units',
+    url: '/studio/v1/codexes/{codex}/entries/{entry}',
+    ...options
+});
+/**
+ * Change what a reference entry says
+ *
+ * Change one entry: its type, its name, its aliases, its description, its facts, its notes, its tracking setting, its images or its relations. Send update_mask naming exactly the fields you change, because a field the mask leaves out keeps its value while a list field the mask names is replaced whole. Renaming an entry changes what the text has to mention for detection to find it.
+ */
+export const studioEntriesUpdate = (options) => (options.client ?? client).patch({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/codexes/{codex}/entries/{entry}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10131,11 +11073,29 @@ export const studioUnitsCreate = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Add a whole outline of units at once
+ * List the writing styles of this organization
  *
- * Create many units in one write from a nested outline, which is how a structure is built after the person approved a plan. Nesting in the outline becomes the parent chain, numbers are assigned in order, and the draft gets one revision for the whole batch rather than one per unit. Sending the same outline twice would duplicate it, so pass the draft revision you read and repeat the call only after a refusal.
+ * List the styles this API key organization owns, each with its name and description, so you can choose the voice a work should be written in. Continue with next_page_token until the answer stops carrying one. Read one style in full before attaching it, because its samples are what actually shape the writing.
+ */
+export const studioStylesList = (options) => (options?.client ?? client).get({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/styles',
+    ...options
+});
+/**
+ * Create a writing style
+ *
+ * Create a style: the voice a piece is written in, held as samples rather than as adjectives. Samples matter more than a description, so paste one to five paragraphs of writing the piece should sound like, and put the words to avoid into avoid so the banned-word check uses them. Attach a style to a work, or to one draft of it, and its samples then reach every context pack.
  */
-export const studioUnitsBatchCreate = (options) => (options.client ?? client).post({
+export const studioStylesCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10145,7 +11105,7 @@ export const studioUnitsBatchCreate = (options) => (options.client ?? client).po
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}/units:batchCreate',
+    url: '/studio/v1/styles',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10153,11 +11113,11 @@ export const studioUnitsBatchCreate = (options) => (options.client ?? client).po
     }
 });
 /**
- * Write intents for many units in one call
+ * Delete a writing style
  *
- * Change the intent of several units in one write: the synopsis, the points and the brief points each of them claims. Bodies are not part of this call, because a body is written one unit at a time with its own revision; here the whole batch shares the draft revision you read. Use it to lay out a plan across the tree, then write bodies one by one.
+ * Delete a style, which detaches it from every work and draft that used it; those units then stop receiving its samples and glossary in their context packs. This cannot be undone, so confirm the style identifier before deleting it, and read the work first when it is not certain which style it uses.
  */
-export const studioUnitsBatchUpdate = (options) => (options.client ?? client).post({
+export const studioStylesDelete = (options) => (options.client ?? client).delete({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10167,19 +11127,15 @@ export const studioUnitsBatchUpdate = (options) => (options.client ?? client).po
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/drafts/{draft}/units:batchUpdate',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/studio/v1/styles/{style}',
+    ...options
 });
 /**
- * Read one unit with its blocks and Markdown
+ * Read one writing style
  *
- * Read one unit: its intent, its status, its revision, its links to reference entries, and its body as both blocks and Markdown. The Markdown carries each block identifier inline as an anchor comment, so a rewrite can keep the identifiers of the blocks it keeps. Read this before writing the body, because the revision it returns is the precondition that write has to carry.
+ * Read one style in full: its samples, the wording to use and to avoid, and its glossary of wrong-to-right terms. Read it before attaching it to a work, since samples decide the sound of the writing far more than the description does, and a glossary term also becomes a deterministic check against the text.
  */
-export const studioUnitsGet = (options) => (options.client ?? client).get({
+export const studioStylesGet = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10189,15 +11145,15 @@ export const studioUnitsGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/units/{unit}',
+    url: '/studio/v1/styles/{style}',
     ...options
 });
 /**
- * Change a unit intent, body or status
+ * Change a writing style
  *
- * Change one unit: its name, its heading, its synopsis and points, the brief points it claims, its status, its links to reference entries, or its body as a whole Markdown text. A body write requires expected_revision, because replacing the whole text would drop blocks someone else inserted. The answer carries the unit as it now stands, so read the next field of the answer instead of re-reading the unit.
+ * Change a style: its name, its description, its samples, its use and avoid lists, or its glossary. Send update_mask naming exactly the fields you change; a list the mask names is replaced whole. Adding a term to the glossary or to avoid also changes what the deterministic checks flag, so a work that uses this style sees new findings on its next check.
  */
-export const studioUnitsUpdate = (options) => (options.client ?? client).patch({
+export const studioStylesUpdate = (options) => (options.client ?? client).patch({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10207,7 +11163,7 @@ export const studioUnitsUpdate = (options) => (options.client ?? client).patch({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/units/{unit}',
+    url: '/studio/v1/styles/{style}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10215,11 +11171,11 @@ export const studioUnitsUpdate = (options) => (options.client ?? client).patch({
     }
 });
 /**
- * Move a unit to another place in the tree
+ * List the templates a genre can start from
  *
- * Move a unit under another parent or after another sibling, without changing its number, its identifier, its intent or its body. A move that would put a unit inside its own descendant, or that would cross into another draft, is refused. Only the moved unit changes, so the revision to pass is its own.
+ * List templates: the built-in starting structures of each genre, followed by the ones this organization saved. Pass a genre to see only the templates that genre can use. A template is used once when a draft is created and is then detached, so changing a template never rewrites a draft that already started from it.
  */
-export const studioUnitsMove = (options) => (options.client ?? client).post({
+export const studioTemplatesList = (options) => (options?.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10229,19 +11185,15 @@ export const studioUnitsMove = (options) => (options.client ?? client).post({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/units/{unit}:move',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/studio/v1/templates',
+    ...options
 });
 /**
- * Edit a unit body block by block
+ * Save a starting structure as a template
  *
- * Change a body by naming the blocks to insert, replace or delete instead of resending the whole text. This is the safe way for a writer that only touches part of a unit, because a block another writer changed after your revision is refused rather than overwritten. The revision is required, and the answer carries the unit with its blocks so the next edit can address them.
+ * Save a unit tree as a reusable template for one genre, so the same structure can seed later drafts. Give the genre, a name, the outline of units with their intents, and optionally the writing guidance a writer should follow. Creating a template from an existing draft is a separate milestone and answers NOT_IMPLEMENTED, so build the outline here instead.
  */
-export const studioUnitsPatchBlocks = (options) => (options.client ?? client).post({
+export const studioTemplatesCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10251,7 +11203,7 @@ export const studioUnitsPatchBlocks = (options) => (options.client ?? client).po
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/units/{unit}/blocks:patch',
+    url: '/studio/v1/templates',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10259,11 +11211,11 @@ export const studioUnitsPatchBlocks = (options) => (options.client ?? client).po
     }
 });
 /**
- * Read the context pack for writing one unit
+ * Delete a saved template
  *
- * Read everything a writer needs before touching one unit: the genre rules, the goal, the brief, the style, the upstream source, the reference entries this unit draws on, the synopses of the units before it, and the intent of this unit, assembled in a fixed order and measured against a token budget. Entries left out say why, so a missing detail is visible rather than silent. Same input gives the same pack, which is what makes a written result reproducible.
+ * Delete a template this organization saved. A built-in template belongs to the catalog and cannot be deleted, so this answers TEMPLATE_NOT_FOUND for one. Drafts that already started from the template are unaffected, because the template was detached when they were created. This cannot be undone.
  */
-export const studioUnitsContext = (options) => (options.client ?? client).get({
+export const studioTemplatesDelete = (options) => (options.client ?? client).delete({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10273,15 +11225,15 @@ export const studioUnitsContext = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/works/{work}/units/{unit}/context',
+    url: '/studio/v1/templates/{template}',
     ...options
 });
 /**
- * List the reference libraries of this organization
+ * Read one template
  *
- * List the reference libraries this API key organization owns, each with how many entries it holds, so you can choose the one a work draws on. Continue with next_page_token until the answer stops carrying one. A library is shared across works, so the list is the whole organization's rather than one work's.
+ * Read one template: its genre, the writing guidance it carries and the unit outline it seeds, with each unit's intent. Address a saved template by its identifier and a built-in one by its key, alone or with its genre prefix such as novel_long:three_act when two genres share a key. Read it before creating a draft from it, because the template decides the structure the draft starts with.
  */
-export const studioCodexesList = (options) => (options?.client ?? client).get({
+export const studioTemplatesGet = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10291,15 +11243,15 @@ export const studioCodexesList = (options) => (options?.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes',
+    url: '/studio/v1/templates/{template}',
     ...options
 });
 /**
- * Create a reference library
+ * List the rendition themes of a platform
  *
- * Create a reference library: a shared store of the people, places, products and facts a piece draws on, reusable across works. Attach it to a work with the work update call, and the entries it holds then reach the context packs of that work's units. A library is not private to one work, so the same brand facts can serve every piece that mentions them.
+ * List themes: the layouts a rendition is produced with, for one platform or for all of them. Pass a platform to see only the themes that platform can use. The first page starts with the built-in themes (builtin true, such as warm-card@1 for Xiaohongshu cards and plain-mono@1 for WeChat articles), which every organization can use and nobody can change or delete; your organization's own themes follow. A theme decides the page or card a rendition is built into, so read the chosen theme before creating a rendition rather than after the output looks wrong.
  */
-export const studioCodexesCreate = (options) => (options.client ?? client).post({
+export const studioThemesList = (options) => (options?.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10309,7 +11261,25 @@ export const studioCodexesCreate = (options) => (options.client ?? client).post(
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes',
+    url: '/studio/v1/themes',
+    ...options
+});
+/**
+ * Create a rendition theme
+ *
+ * Create a theme for one platform: the HTML and CSS a written piece is rendered into, plus the fixed header and footer every rendition carries. A DOCX platform takes a reference document instead of markup, and a card theme takes its aspect, width and fonts. An agent may write a theme here, which is how a new layout appears without a release.
+ */
+export const studioThemesCreate = (options) => (options.client ?? client).post({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/studio/v1/themes',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10317,11 +11287,11 @@ export const studioCodexesCreate = (options) => (options.client ?? client).post(
     }
 });
 /**
- * Delete a reference library
+ * Delete a rendition theme
  *
- * Delete a library and every entry inside it. A library attached to any work is refused with CODEX_IN_USE, because deleting it would silently strip the reference material those units draw on; detach it from the work first. This cannot be undone, so confirm which library the identifier names.
+ * Delete a theme this organization created. A built-in theme belongs to the platform and cannot be deleted, so this answers THEME_NOT_FOUND for one. Renditions already produced with the theme keep their output, because the produced file no longer depends on the theme. This cannot be undone.
  */
-export const studioCodexesDelete = (options) => (options.client ?? client).delete({
+export const studioThemesDelete = (options) => (options.client ?? client).delete({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10331,15 +11301,15 @@ export const studioCodexesDelete = (options) => (options.client ?? client).delet
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}',
+    url: '/studio/v1/themes/{theme}',
     ...options
 });
 /**
- * Read one reference library
+ * Read one rendition theme
  *
- * Read one reference library: its name, its description, its labels and how many entries it holds. Read this to confirm a library exists before attaching it to a work; the entries themselves are listed with the entry list call, because a library may hold more of them than fit in one answer.
+ * Read one theme in full: the HTML template and stylesheet it renders with, the header and footer it always carries, the reference document a DOCX rendition uses, or the card proportions a card rendition uses. Read it before creating a rendition with it, because a theme decides what the output looks like and a DOCX theme is a file rather than markup.
  */
-export const studioCodexesGet = (options) => (options.client ?? client).get({
+export const studioThemesGet = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10349,15 +11319,15 @@ export const studioCodexesGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}',
+    url: '/studio/v1/themes/{theme}',
     ...options
 });
 /**
- * Rename a reference library or change its description
+ * Change a rendition theme
  *
- * Change the library itself: its name, its description or its labels. Send update_mask naming exactly the fields you change; a field left out keeps its value. The entries inside are untouched, and a work that has the library attached keeps it attached under the new name.
+ * Change a theme: its name, its markup, its stylesheet, or the fixed fragments around every rendition. Send update_mask naming exactly the fields you change. Changing a theme does not rewrite renditions already produced with an earlier version, because each rendition records the theme version it was built from.
  */
-export const studioCodexesUpdate = (options) => (options.client ?? client).patch({
+export const studioThemesUpdate = (options) => (options.client ?? client).patch({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10367,7 +11337,7 @@ export const studioCodexesUpdate = (options) => (options.client ?? client).patch
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}',
+    url: '/studio/v1/themes/{theme}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10375,11 +11345,11 @@ export const studioCodexesUpdate = (options) => (options.client ?? client).patch
     }
 });
 /**
- * List the entries of a reference library
+ * Create a rendition of a draft for a platform
  *
- * List the entries of one library in pages, each with its type, its name, its aliases and whether it is always present in context. Use it to see what a work already knows before adding an entry, since a duplicate name is refused rather than merged. Continue with next_page_token until the answer stops carrying one.
+ * Create a rendition: the form of one draft that a platform receives, such as a Xiaohongshu card set, a DOCX file or a Markdown file. Read the platform first with the platform call and pass its versioned key; pass a theme only to override the platform's default layout. Pass render true to render in the same call and read render_state and issues in the answer; without it the rendition starts as pending and the render call produces it. Rendering a Xiaohongshu card set is billed by Browser Rendering time (meter browser_ms, product studio-render); DOCX and Markdown renditions are not billed. A draft with no body renders as invalid with a draft_empty issue, and an unavailable render service leaves render_state failed with a render_unavailable issue, so repeat the render call later. Send a request_id to make a repeated call return the first rendition instead of creating another. Next, publish the rendition to export it.
  */
-export const studioEntriesList = (options) => (options.client ?? client).get({
+export const studioRenditionsCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10389,15 +11359,19 @@ export const studioEntriesList = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}/entries',
-    ...options
+    url: '/studio/v1/works/{work}/drafts/{draft}/renditions',
+    ...options,
+    headers: {
+        'Content-Type': 'application/json',
+        ...options.headers
+    }
 });
 /**
- * Add an entry to a reference library
+ * List the renditions of a work
  *
- * Add one entry: a character, a place, a product, a source of facts. Give it the type the genre uses, the name the text will mention, and the description and facts that should reach a writer when it is mentioned. Aliases and excluded phrases keep detection honest, so a common word inside an idiom is not mistaken for the entry. A name already used in the library is refused.
+ * List the renditions of one work, each with its platform, render state, stale flag and publish state. Pass draft to see only the renditions of one draft. Use it to find the rendition to publish or to render again, and read stale before exporting: a stale rendition was built from an older draft and cannot be exported until the render call has rebuilt it. The answer is one page; keep following next_page_token while it is present.
  */
-export const studioEntriesCreate = (options) => (options.client ?? client).post({
+export const studioRenditionsList = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10407,19 +11381,15 @@ export const studioEntriesCreate = (options) => (options.client ?? client).post(
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}/entries',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/studio/v1/works/{work}/renditions',
+    ...options
 });
 /**
- * Delete a reference entry
+ * Delete a rendition
  *
- * Delete one entry from a library, which also removes the mentions and the links that pointed at it. Units that claimed it keep their text; only the reference goes away. This cannot be undone, so confirm the name of the entry before deleting it, and prefer changing its tracking setting to never when it should stop reaching writers but stay recorded.
+ * Delete a rendition and stop listing it. The draft it was built from is untouched, and a new rendition can be created from it at any time. Files already downloaded from an earlier export are not affected. Use it to clear a failed or abandoned rendition; to refresh one, call the render operation instead.
  */
-export const studioEntriesDelete = (options) => (options.client ?? client).delete({
+export const studioRenditionsDelete = (options) => (options.client ?? client).delete({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10429,15 +11399,15 @@ export const studioEntriesDelete = (options) => (options.client ?? client).delet
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}/entries/{entry}',
+    url: '/studio/v1/works/{work}/renditions/{rendition}',
     ...options
 });
 /**
- * Read one reference entry
+ * Read one rendition
  *
- * Read one entry in full: its description, its fact ledger, its relations to other entries, its detection settings and its images. Read it before changing it, because an update replaces the fields it names rather than merging them. The entry is addressed by its name in this library, or by its ent_ identifier.
+ * Read one rendition in full: its render state, the validation issues the render found, the parts (one per card page or thread post), the files it produced and its publish state. Call it after create, render or publish to see the outcome, because a render that finished invalid or failed is reported here and not as an HTTP error. stale is true when the draft has changed since source_revision; call the render operation before exporting a stale rendition.
  */
-export const studioEntriesGet = (options) => (options.client ?? client).get({
+export const studioRenditionsGet = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10447,15 +11417,15 @@ export const studioEntriesGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}/entries/{entry}',
+    url: '/studio/v1/works/{work}/renditions/{rendition}',
     ...options
 });
 /**
- * Change what a reference entry says
+ * Change the theme or settings of a rendition
  *
- * Change one entry: its type, its name, its aliases, its description, its facts, its notes, its tracking setting, its images or its relations. Send update_mask naming exactly the fields you change, because a field the mask leaves out keeps its value while a list field the mask names is replaced whole. Renaming an entry changes what the text has to mention for detection to find it.
+ * Change a rendition's theme or settings. Send update_mask naming exactly the fields you change, such as theme or settings; a field left out keeps its value. The produced files are not rebuilt by this call, so call the render operation afterwards to apply the change. A rendition whose export or publish has started is locked and answers RENDITION_PUBLISH_LOCKED; create a new rendition for new content.
  */
-export const studioEntriesUpdate = (options) => (options.client ?? client).patch({
+export const studioRenditionsUpdate = (options) => (options.client ?? client).patch({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10465,7 +11435,7 @@ export const studioEntriesUpdate = (options) => (options.client ?? client).patch
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/codexes/{codex}/entries/{entry}',
+    url: '/studio/v1/works/{work}/renditions/{rendition}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10473,11 +11443,11 @@ export const studioEntriesUpdate = (options) => (options.client ?? client).patch
     }
 });
 /**
- * List the writing styles of this organization
+ * Render a rendition again from the current draft
  *
- * List the styles this API key organization owns, each with its name and description, so you can choose the voice a work should be written in. Continue with next_page_token until the answer stops carrying one. Read one style in full before attaching it, because its samples are what actually shape the writing.
+ * Render the rendition from the draft as it is now, replacing its parts and files and clearing stale. Call it after the draft changed, after a theme or settings change, or after a failed render. The answer carries render_state: rendered, invalid when the draft has an error-level issue (for example draft_empty on a draft with no body), or failed when the render service was unavailable (issue render_unavailable; repeat later). A render does not fail the HTTP call for those outcomes, so read render_state and issues. Rendering a Xiaohongshu card set is billed by Browser Rendering time (meter browser_ms, product studio-render); DOCX and Markdown are not billed. Rendering the same rendition twice at once answers REVISION_CONFLICT; retry shortly. Next, publish the rendition to export it.
  */
-export const studioStylesList = (options) => (options?.client ?? client).get({
+export const studioRenditionsRender = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10487,15 +11457,15 @@ export const studioStylesList = (options) => (options?.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/styles',
+    url: '/studio/v1/works/{work}/renditions/{rendition}:render',
     ...options
 });
 /**
- * Create a writing style
+ * Export a rendition
  *
- * Create a style: the voice a piece is written in, held as samples rather than as adjectives. Samples matter more than a description, so paste one to five paragraphs of writing the piece should sound like, and put the words to avoid into avoid so the banned-word check uses them. Attach a style to a work, or to one draft of it, and its samples then reach every context pack.
+ * Export a rendition for the platforms that deliver a file: markdown@1, docx@1 and xiaohongshu@1 end with publish.state exported, and a card rendition gains one ZIP of its pages in files. Publishing to a platform account such as X or WeChat is not available yet and answers PLATFORM_NOT_AVAILABLE; export instead. The rendition must be rendered, not stale and without error-level issues: RENDITION_NOT_RENDERED means call the render operation first, RENDITION_STALE means the draft changed so render again, RENDITION_INVALID means fix the draft problems listed in issues and render again. Exporting the same rendition twice at once answers REVISION_CONFLICT; retry shortly. Next, call the content operation to download the file.
  */
-export const studioStylesCreate = (options) => (options.client ?? client).post({
+export const studioRenditionsPublish = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10505,19 +11475,15 @@ export const studioStylesCreate = (options) => (options.client ?? client).post({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/styles',
-    ...options,
-    headers: {
-        'Content-Type': 'application/json',
-        ...options.headers
-    }
+    url: '/studio/v1/works/{work}/renditions/{rendition}:publish',
+    ...options
 });
 /**
- * Delete a writing style
+ * Get a download URL for a rendition file
  *
- * Delete a style, which detaches it from every work and draft that used it; those units then stop receiving its samples and glossary in their context packs. This cannot be undone, so confirm the style identifier before deleting it, and read the work first when it is not certain which style it uses.
+ * Get a signed, short-lived URL to download what a rendition produced. Without part it points to the rendition's own first file: the ZIP of pages for a card rendition, the DOCX for docx@1. With part it points to that part's first file, such as one card PNG; a part that has no file, or a rendition not rendered yet, answers RENDITION_NOT_RENDERED, and an index no part has answers INVALID_PARAMS. Call it after a successful render or export, download the url before expire_time, and call again for a fresh one when it has expired. The URL is a credential: do not store or share it.
  */
-export const studioStylesDelete = (options) => (options.client ?? client).delete({
+export const studioRenditionsContentUrl = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10527,15 +11493,15 @@ export const studioStylesDelete = (options) => (options.client ?? client).delete
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/styles/{style}',
+    url: '/studio/v1/works/{work}/renditions/{rendition}/content',
     ...options
 });
 /**
- * Read one writing style
+ * List the blind review rounds of a work
  *
- * Read one style in full: its samples, the wording to use and to avoid, and its glossary of wrong-to-right terms. Read it before attaching it to a work, since samples decide the sound of the writing far more than the description does, and a glossary term also becomes a deterministic check against the text.
+ * List the review rounds of one work, newest round first, each with its draft, round number, status, decision and whether it was appealed. Pass draft to see the rounds of one draft only. Use it to find the round to read, to answer or to cancel, and to see whether the draft already has a round running before sending another: a running round answers REVIEW_IN_PROGRESS. The answer is one page; keep following next_page_token while it is present. Rounds of other organizations are not listed and a work of another organization answers WORK_NOT_FOUND.
  */
-export const studioStylesGet = (options) => (options.client ?? client).get({
+export const studioWorksReviewsList = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10545,15 +11511,15 @@ export const studioStylesGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/styles/{style}',
+    url: '/studio/v1/works/{work}/reviews',
     ...options
 });
 /**
- * Change a writing style
+ * Send a draft to blind review
  *
- * Change a style: its name, its description, its samples, its use and avoid lists, or its glossary. Send update_mask naming exactly the fields you change; a list the mask names is replaced whole. Adding a term to the glossary or to avoid also changes what the deterministic checks flag, so a work that uses this style sees new findings on its next check.
+ * Send one draft of this work to the blind review centre, which freezes the draft's content revision as it is now, draws reviewers for the work's review settings and asks them in. Use it once the draft is written; the centre chooses who reviews, and the sender only ever reads labels A, B, C, never the reviewer identities. Pass mode to narrow this round to expert reviewers, to audience reviewers or to both, which the settings do not decide. From the second round pass revision_of with the previous round's rv_ id and note with the change note that answers that round point by point. The answer is the new round in status reviewing; read it again with the review read until status becomes decided and then read decision, expert_reports and screening. Billing follows the reviewers' sessions, not the frame of this call. DRAFT_NOT_READY means the draft still has units without a body or fails a hard check, so finish it first; REVIEW_IN_PROGRESS means this draft already has a round running, so wait for it to decide or cancel it; REVIEW_ROUND_LIMIT means the work reached max_rounds and a person has to raise it in the review settings; REVIEWER_POOL_EMPTY means the reviewer library cannot fill the seats under these conditions, so a person registers or re-activates reviewers.
  */
-export const studioStylesUpdate = (options) => (options.client ?? client).patch({
+export const studioWorksReviewsCreate = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10563,7 +11529,7 @@ export const studioStylesUpdate = (options) => (options.client ?? client).patch(
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/styles/{style}',
+    url: '/studio/v1/works/{work}/reviews',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10571,11 +11537,11 @@ export const studioStylesUpdate = (options) => (options.client ?? client).patch(
     }
 });
 /**
- * List the templates a genre can start from
+ * Read one blind review round
  *
- * List templates: the built-in starting structures of each genre, followed by the ones this organization saved. Pass a genre to see only the templates that genre can use. A template is used once when a draft is created and is then detached, so changing a template never rewrites a draft that already started from it.
+ * Read one round in the sender's view: its status, the seats as labels A, B, C with the state of each, the expert reports that have come back, the screening cards, the round decision and the audience tally. Reviewers appear only as labels; who they are is never part of this answer. Call it after sending a round and repeat while status is reviewing, because reviewers answer asynchronously and a round that is not decided yet carries fewer reports. status decided gives decision and screening; cancelled means a person stopped the round; failed means it could not be completed, for example when every reviewer timed out and no replacement could be drawn. Pass view=audit to also get the assignment record, the confidential editor notes and the reviewer sessions; that block is filled only for an organization administrator, and anyone else reads the same round without it.
  */
-export const studioTemplatesList = (options) => (options?.client ?? client).get({
+export const studioWorksReviewsRetrieve = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10585,15 +11551,15 @@ export const studioTemplatesList = (options) => (options?.client ?? client).get(
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/templates',
+    url: '/studio/v1/works/{work}/reviews/{review}',
     ...options
 });
 /**
- * Save a starting structure as a template
+ * Appeal a decided review round
  *
- * Save a unit tree as a reusable template for one genre, so the same structure can seed later drafts. Give the genre, a name, the outline of units with their intents, and optionally the writing guidance a writer should follow. Creating a template from an existing draft is a separate milestone and answers NOT_IMPLEMENTED, so build the outline here instead.
+ * Appeal the outcome of a round: the centre draws one more reviewer of the same kind and puts that reviewer's answer beside the existing ones, without telling them the earlier outcome. Use it once, when the sender disagrees with the decision; the reason is recorded for the review centre, and the sender cannot choose the new reviewer. The round goes back to status reviewing and its id stays the same, so read it again afterwards. Each round can be appealed once: a second call for the same round answers REVIEW_ALREADY_APPEALED. Only a decided round can be appealed, so a round that is still reviewing or was cancelled answers REVIEW_IN_PROGRESS or stays cancelled. The extra reviewer's session is billed like any other reviewer session.
  */
-export const studioTemplatesCreate = (options) => (options.client ?? client).post({
+export const studioWorksReviewsAppeal = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10603,7 +11569,7 @@ export const studioTemplatesCreate = (options) => (options.client ?? client).pos
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/templates',
+    url: '/studio/v1/works/{work}/reviews/{review}:appeal',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10611,29 +11577,11 @@ export const studioTemplatesCreate = (options) => (options.client ?? client).pos
     }
 });
 /**
- * Delete a saved template
- *
- * Delete a template this organization saved. A built-in template belongs to the catalog and cannot be deleted, so this answers TEMPLATE_NOT_FOUND for one. Drafts that already started from the template are unaffected, because the template was detached when they were created. This cannot be undone.
- */
-export const studioTemplatesDelete = (options) => (options.client ?? client).delete({
-    security: [{
-            key: 'BearerAuth',
-            scheme: 'bearer',
-            type: 'http'
-        }, {
-            key: 'ApiKeyAuth',
-            name: 'X-API-Key',
-            type: 'apiKey'
-        }],
-    url: '/studio/v1/templates/{template}',
-    ...options
-});
-/**
- * Read one template
+ * Cancel a running review round
  *
- * Read one template: its genre, the writing guidance it carries and the unit outline it seeds, with each unit's intent. Address a saved template by its identifier and a built-in one by its key, alone or with its genre prefix such as novel_long:three_act when two genres share a key. Read it before creating a draft from it, because the template decides the structure the draft starts with.
+ * Cancel a round that is still reviewing, so its reviewers are no longer waited for and the draft can be sent again. Nothing that came back is deleted: the round stays readable with status cancelled and the reports it had. Use it when the draft changed so much that the running round is no longer about the current text, or when the round was sent by mistake; a person makes this call, and an agent calling it is refused with PERMISSION_DENIED. A round that already reached a decision answers REVIEW_IN_PROGRESS, because a decided round is answered by sending the next round with revision_of rather than by cancelling it. Reviewer sessions already started keep being billed.
  */
-export const studioTemplatesGet = (options) => (options.client ?? client).get({
+export const studioWorksReviewsCancel = (options) => (options.client ?? client).post({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10643,15 +11591,15 @@ export const studioTemplatesGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/templates/{template}',
+    url: '/studio/v1/works/{work}/reviews/{review}:cancel',
     ...options
 });
 /**
- * List the rendition themes of a platform
+ * Read the review settings of a work
  *
- * List themes: the layouts a rendition is produced with, for one platform or for all of them. Pass a platform to see only the themes that platform can use. A theme decides the page or card a rendition is built into, so read the chosen theme before creating a rendition rather than after the output looks wrong.
+ * Read how this work is reviewed: the seats that make up its review panel, each naming a reviewer kind, a tag and how many reviewers are drawn for it, the maximum number of rounds, and the revision the settings are at. Read it before sending a round, because a draft whose conditions the reviewer library cannot fill answers REVIEWER_POOL_EMPTY, and read it before changing it, because the update carries the revision it returns as its precondition. Settings are not part of the work body: they are read and written here.
  */
-export const studioThemesList = (options) => (options?.client ?? client).get({
+export const studioWorksReviewSettingsRetrieve = (options) => (options.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10661,15 +11609,15 @@ export const studioThemesList = (options) => (options?.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/themes',
+    url: '/studio/v1/works/{work}/review-settings',
     ...options
 });
 /**
- * Create a rendition theme
+ * Change the review settings of a work
  *
- * Create a theme for one platform: the HTML and CSS a written piece is rendered into, plus the fixed header and footer every rendition carries. A DOCX platform takes a reference document instead of markup, and a card theme takes its aspect, width and fonts. An agent may write a theme here, which is how a new layout appears without a release.
+ * Change the review panel of a work: the seats, the maximum number of rounds, or both. Send expected_revision with the revision this settings read returned, so two writers cannot overwrite each other silently; a mismatch answers REVISION_CONFLICT and the settings are unchanged. A person makes this change, because widening who may judge a work is the owner's decision: an agent calling it is refused with PERMISSION_DENIED, which is this operation's answer for a caller without the organization's management identity. The settings are locked while a round of this work is reviewing, which answers REVIEW_IN_PROGRESS; change them after the round decides or is cancelled. Raising max_rounds is how a draft whose rounds are used up is sent again. The changed settings apply to rounds sent from now on and never rewrite a round already sent.
  */
-export const studioThemesCreate = (options) => (options.client ?? client).post({
+export const studioWorksReviewSettingsUpdate = (options) => (options.client ?? client).patch({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10679,7 +11627,7 @@ export const studioThemesCreate = (options) => (options.client ?? client).post({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/themes',
+    url: '/studio/v1/works/{work}/review-settings',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -10687,29 +11635,11 @@ export const studioThemesCreate = (options) => (options.client ?? client).post({
     }
 });
 /**
- * Delete a rendition theme
- *
- * Delete a theme this organization created. A built-in theme belongs to the platform and cannot be deleted, so this answers THEME_NOT_FOUND for one. Renditions already produced with the theme keep their output, because the produced file no longer depends on the theme. This cannot be undone.
- */
-export const studioThemesDelete = (options) => (options.client ?? client).delete({
-    security: [{
-            key: 'BearerAuth',
-            scheme: 'bearer',
-            type: 'http'
-        }, {
-            key: 'ApiKeyAuth',
-            name: 'X-API-Key',
-            type: 'apiKey'
-        }],
-    url: '/studio/v1/themes/{theme}',
-    ...options
-});
-/**
- * Read one rendition theme
+ * List the reviewers of the organization
  *
- * Read one theme in full: the HTML template and stylesheet it renders with, the header and footer it always carries, the reference document a DOCX rendition uses, or the card proportions a card rendition uses. Read it before creating a rendition with it, because a theme decides what the output looks like and a DOCX theme is a file rather than markup.
+ * List the reviewers this organization can draw on: one entry per reviewer agent, with its kind, its display name, the tags it matches seats on, the model family it runs and whether it is active. Pass kind to see only expert or only audience reviewers. Read it before setting a work's seats, so the seat conditions match reviewers that exist, and after REVIEWER_POOL_EMPTY to see which reviewers are missing or inactive. Entries are the organization's own reviewer agents; a reviewer of another organization is never listed. The answer is one page; keep following next_page_token while it is present.
  */
-export const studioThemesGet = (options) => (options.client ?? client).get({
+export const studioReviewersList = (options) => (options?.client ?? client).get({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10719,15 +11649,15 @@ export const studioThemesGet = (options) => (options.client ?? client).get({
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/themes/{theme}',
+    url: '/studio/v1/reviewers',
     ...options
 });
 /**
- * Change a rendition theme
+ * Activate or retire a reviewer
  *
- * Change a theme: its name, its markup, its stylesheet, or the fixed fragments around every rendition. Send update_mask naming exactly the fields you change. Changing a theme does not rewrite renditions already produced with an earlier version, because each rendition records the theme version it was built from.
+ * Take one reviewer in or out of the draw: active false keeps it in the library but stops it being drawn for future seats, and active true puts it back. Use it when a reviewer should stop judging, for example when its answers are consistently unusable, and set it back once that is dealt with. A round already sent is not affected, because its assignments were made when it was sent. A person makes this change, and an agent calling it is refused with PERMISSION_DENIED. The reviewer is addressed by the agent value the reviewer list returns; an unknown one answers REVIEWER_NOT_FOUND, which is also the answer for a reviewer of another organization.
  */
-export const studioThemesUpdate = (options) => (options.client ?? client).patch({
+export const studioReviewersUpdate = (options) => (options.client ?? client).patch({
     security: [{
             key: 'BearerAuth',
             scheme: 'bearer',
@@ -10737,7 +11667,7 @@ export const studioThemesUpdate = (options) => (options.client ?? client).patch(
             name: 'X-API-Key',
             type: 'apiKey'
         }],
-    url: '/studio/v1/themes/{theme}',
+    url: '/studio/v1/reviewers/{agent}',
     ...options,
     headers: {
         'Content-Type': 'application/json',
@@ -11894,3 +12824,21 @@ export const ticketGetRepositories = (options) => (options?.client ?? client).ge
     url: '/ticket/v1/repositories',
     ...options
 });
+/**
+ * Update repositories
+ *
+ * Update repositories within the authenticated organization. Obtain resource identifiers from the corresponding list or create response. Writes complete synchronously; read the returned resource to observe the result. Service authorization applies to the verified human subject.
+ */
+export const ticketPatchRepositoriesId = (options) => (options.client ?? client).patch({
+    security: [{
+            key: 'BearerAuth',
+            scheme: 'bearer',
+            type: 'http'
+        }, {
+            key: 'ApiKeyAuth',
+            name: 'X-API-Key',
+            type: 'apiKey'
+        }],
+    url: '/ticket/v1/repositories/{id}',
+    ...options
+});