@nfreeness/clawdbot 0.124.22101 → 0.124.22103

package/extensions/memory-lancedb/node_modules/.ignored_openai/src/resources/responses.ts

@@ -1,3 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-export * from './responses/index';

package/extensions/memory-lancedb/node_modules/.ignored_openai/src/resources/shared.ts

@@ -1,423 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-export type AllModels =
-  | (string & {})
-  | ChatModel
-  | 'o1-pro'
-  | 'o1-pro-2025-03-19'
-  | 'o3-pro'
-  | 'o3-pro-2025-06-10'
-  | 'o3-deep-research'
-  | 'o3-deep-research-2025-06-26'
-  | 'o4-mini-deep-research'
-  | 'o4-mini-deep-research-2025-06-26'
-  | 'computer-use-preview'
-  | 'computer-use-preview-2025-03-11'
-  | 'gpt-5-codex'
-  | 'gpt-5-pro'
-  | 'gpt-5-pro-2025-10-06'
-  | 'gpt-5.1-codex-max';
-
-export type ChatModel =
-  | 'gpt-5.2'
-  | 'gpt-5.2-2025-12-11'
-  | 'gpt-5.2-chat-latest'
-  | 'gpt-5.2-pro'
-  | 'gpt-5.2-pro-2025-12-11'
-  | 'gpt-5.1'
-  | 'gpt-5.1-2025-11-13'
-  | 'gpt-5.1-codex'
-  | 'gpt-5.1-mini'
-  | 'gpt-5.1-chat-latest'
-  | 'gpt-5'
-  | 'gpt-5-mini'
-  | 'gpt-5-nano'
-  | 'gpt-5-2025-08-07'
-  | 'gpt-5-mini-2025-08-07'
-  | 'gpt-5-nano-2025-08-07'
-  | 'gpt-5-chat-latest'
-  | 'gpt-4.1'
-  | 'gpt-4.1-mini'
-  | 'gpt-4.1-nano'
-  | 'gpt-4.1-2025-04-14'
-  | 'gpt-4.1-mini-2025-04-14'
-  | 'gpt-4.1-nano-2025-04-14'
-  | 'o4-mini'
-  | 'o4-mini-2025-04-16'
-  | 'o3'
-  | 'o3-2025-04-16'
-  | 'o3-mini'
-  | 'o3-mini-2025-01-31'
-  | 'o1'
-  | 'o1-2024-12-17'
-  | 'o1-preview'
-  | 'o1-preview-2024-09-12'
-  | 'o1-mini'
-  | 'o1-mini-2024-09-12'
-  | 'gpt-4o'
-  | 'gpt-4o-2024-11-20'
-  | 'gpt-4o-2024-08-06'
-  | 'gpt-4o-2024-05-13'
-  | 'gpt-4o-audio-preview'
-  | 'gpt-4o-audio-preview-2024-10-01'
-  | 'gpt-4o-audio-preview-2024-12-17'
-  | 'gpt-4o-audio-preview-2025-06-03'
-  | 'gpt-4o-mini-audio-preview'
-  | 'gpt-4o-mini-audio-preview-2024-12-17'
-  | 'gpt-4o-search-preview'
-  | 'gpt-4o-mini-search-preview'
-  | 'gpt-4o-search-preview-2025-03-11'
-  | 'gpt-4o-mini-search-preview-2025-03-11'
-  | 'chatgpt-4o-latest'
-  | 'codex-mini-latest'
-  | 'gpt-4o-mini'
-  | 'gpt-4o-mini-2024-07-18'
-  | 'gpt-4-turbo'
-  | 'gpt-4-turbo-2024-04-09'
-  | 'gpt-4-0125-preview'
-  | 'gpt-4-turbo-preview'
-  | 'gpt-4-1106-preview'
-  | 'gpt-4-vision-preview'
-  | 'gpt-4'
-  | 'gpt-4-0314'
-  | 'gpt-4-0613'
-  | 'gpt-4-32k'
-  | 'gpt-4-32k-0314'
-  | 'gpt-4-32k-0613'
-  | 'gpt-3.5-turbo'
-  | 'gpt-3.5-turbo-16k'
-  | 'gpt-3.5-turbo-0301'
-  | 'gpt-3.5-turbo-0613'
-  | 'gpt-3.5-turbo-1106'
-  | 'gpt-3.5-turbo-0125'
-  | 'gpt-3.5-turbo-16k-0613';
-
-/**
- * A filter used to compare a specified attribute key to a given value using a
- * defined comparison operation.
- */
-export interface ComparisonFilter {
-  /**
-   * The key to compare against the value.
-   */
-  key: string;
-
-  /**
-   * Specifies the comparison operator: `eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`,
-   * `nin`.
-   *
-   * - `eq`: equals
-   * - `ne`: not equal
-   * - `gt`: greater than
-   * - `gte`: greater than or equal
-   * - `lt`: less than
-   * - `lte`: less than or equal
-   * - `in`: in
-   * - `nin`: not in
-   */
-  type: 'eq' | 'ne' | 'gt' | 'gte' | 'lt' | 'lte';
-
-  /**
-   * The value to compare against the attribute key; supports string, number, or
-   * boolean types.
-   */
-  value: string | number | boolean | Array<string | number>;
-}
-
-/**
- * Combine multiple filters using `and` or `or`.
- */
-export interface CompoundFilter {
-  /**
-   * Array of filters to combine. Items can be `ComparisonFilter` or
-   * `CompoundFilter`.
-   */
-  filters: Array<ComparisonFilter | unknown>;
-
-  /**
-   * Type of operation: `and` or `or`.
-   */
-  type: 'and' | 'or';
-}
-
-/**
- * The input format for the custom tool. Default is unconstrained text.
- */
-export type CustomToolInputFormat = CustomToolInputFormat.Text | CustomToolInputFormat.Grammar;
-
-export namespace CustomToolInputFormat {
-  /**
-   * Unconstrained free-form text.
-   */
-  export interface Text {
-    /**
-     * Unconstrained text format. Always `text`.
-     */
-    type: 'text';
-  }
-
-  /**
-   * A grammar defined by the user.
-   */
-  export interface Grammar {
-    /**
-     * The grammar definition.
-     */
-    definition: string;
-
-    /**
-     * The syntax of the grammar definition. One of `lark` or `regex`.
-     */
-    syntax: 'lark' | 'regex';
-
-    /**
-     * Grammar format. Always `grammar`.
-     */
-    type: 'grammar';
-  }
-}
-
-export interface ErrorObject {
-  code: string | null;
-
-  message: string;
-
-  param: string | null;
-
-  type: string;
-}
-
-export interface FunctionDefinition {
-  /**
-   * The name of the function to be called. Must be a-z, A-Z, 0-9, or contain
-   * underscores and dashes, with a maximum length of 64.
-   */
-  name: string;
-
-  /**
-   * A description of what the function does, used by the model to choose when and
-   * how to call the function.
-   */
-  description?: string;
-
-  /**
-   * The parameters the functions accepts, described as a JSON Schema object. See the
-   * [guide](https://platform.openai.com/docs/guides/function-calling) for examples,
-   * and the
-   * [JSON Schema reference](https://json-schema.org/understanding-json-schema/) for
-   * documentation about the format.
-   *
-   * Omitting `parameters` defines a function with an empty parameter list.
-   */
-  parameters?: FunctionParameters;
-
-  /**
-   * Whether to enable strict schema adherence when generating the function call. If
-   * set to true, the model will follow the exact schema defined in the `parameters`
-   * field. Only a subset of JSON Schema is supported when `strict` is `true`. Learn
-   * more about Structured Outputs in the
-   * [function calling guide](https://platform.openai.com/docs/guides/function-calling).
-   */
-  strict?: boolean | null;
-}
-
-/**
- * The parameters the functions accepts, described as a JSON Schema object. See the
- * [guide](https://platform.openai.com/docs/guides/function-calling) for examples,
- * and the
- * [JSON Schema reference](https://json-schema.org/understanding-json-schema/) for
- * documentation about the format.
- *
- * Omitting `parameters` defines a function with an empty parameter list.
- */
-export type FunctionParameters = { [key: string]: unknown };
-
-/**
- * Set of 16 key-value pairs that can be attached to an object. This can be useful
- * for storing additional information about the object in a structured format, and
- * querying for objects via API or the dashboard.
- *
- * Keys are strings with a maximum length of 64 characters. Values are strings with
- * a maximum length of 512 characters.
- */
-export type Metadata = { [key: string]: string };
-
-/**
- * **gpt-5 and o-series models only**
- *
- * Configuration options for
- * [reasoning models](https://platform.openai.com/docs/guides/reasoning).
- */
-export interface Reasoning {
-  /**
-   * Constrains effort on reasoning for
-   * [reasoning models](https://platform.openai.com/docs/guides/reasoning). Currently
-   * supported values are `none`, `minimal`, `low`, `medium`, `high`, and `xhigh`.
-   * Reducing reasoning effort can result in faster responses and fewer tokens used
-   * on reasoning in a response.
-   *
-   * - `gpt-5.1` defaults to `none`, which does not perform reasoning. The supported
-   *   reasoning values for `gpt-5.1` are `none`, `low`, `medium`, and `high`. Tool
-   *   calls are supported for all reasoning values in gpt-5.1.
-   * - All models before `gpt-5.1` default to `medium` reasoning effort, and do not
-   *   support `none`.
-   * - The `gpt-5-pro` model defaults to (and only supports) `high` reasoning effort.
-   * - `xhigh` is supported for all models after `gpt-5.1-codex-max`.
-   */
-  effort?: ReasoningEffort | null;
-
-  /**
-   * @deprecated **Deprecated:** use `summary` instead.
-   *
-   * A summary of the reasoning performed by the model. This can be useful for
-   * debugging and understanding the model's reasoning process. One of `auto`,
-   * `concise`, or `detailed`.
-   */
-  generate_summary?: 'auto' | 'concise' | 'detailed' | null;
-
-  /**
-   * A summary of the reasoning performed by the model. This can be useful for
-   * debugging and understanding the model's reasoning process. One of `auto`,
-   * `concise`, or `detailed`.
-   *
-   * `concise` is supported for `computer-use-preview` models and all reasoning
-   * models after `gpt-5`.
-   */
-  summary?: 'auto' | 'concise' | 'detailed' | null;
-}
-
-/**
- * Constrains effort on reasoning for
- * [reasoning models](https://platform.openai.com/docs/guides/reasoning). Currently
- * supported values are `none`, `minimal`, `low`, `medium`, `high`, and `xhigh`.
- * Reducing reasoning effort can result in faster responses and fewer tokens used
- * on reasoning in a response.
- *
- * - `gpt-5.1` defaults to `none`, which does not perform reasoning. The supported
- *   reasoning values for `gpt-5.1` are `none`, `low`, `medium`, and `high`. Tool
- *   calls are supported for all reasoning values in gpt-5.1.
- * - All models before `gpt-5.1` default to `medium` reasoning effort, and do not
- *   support `none`.
- * - The `gpt-5-pro` model defaults to (and only supports) `high` reasoning effort.
- * - `xhigh` is supported for all models after `gpt-5.1-codex-max`.
- */
-export type ReasoningEffort = 'none' | 'minimal' | 'low' | 'medium' | 'high' | 'xhigh' | null;
-
-/**
- * JSON object response format. An older method of generating JSON responses. Using
- * `json_schema` is recommended for models that support it. Note that the model
- * will not generate JSON without a system or user message instructing it to do so.
- */
-export interface ResponseFormatJSONObject {
-  /**
-   * The type of response format being defined. Always `json_object`.
-   */
-  type: 'json_object';
-}
-
-/**
- * JSON Schema response format. Used to generate structured JSON responses. Learn
- * more about
- * [Structured Outputs](https://platform.openai.com/docs/guides/structured-outputs).
- */
-export interface ResponseFormatJSONSchema {
-  /**
-   * Structured Outputs configuration options, including a JSON Schema.
-   */
-  json_schema: ResponseFormatJSONSchema.JSONSchema;
-
-  /**
-   * The type of response format being defined. Always `json_schema`.
-   */
-  type: 'json_schema';
-}
-
-export namespace ResponseFormatJSONSchema {
-  /**
-   * Structured Outputs configuration options, including a JSON Schema.
-   */
-  export interface JSONSchema {
-    /**
-     * The name of the response format. Must be a-z, A-Z, 0-9, or contain underscores
-     * and dashes, with a maximum length of 64.
-     */
-    name: string;
-
-    /**
-     * A description of what the response format is for, used by the model to determine
-     * how to respond in the format.
-     */
-    description?: string;
-
-    /**
-     * The schema for the response format, described as a JSON Schema object. Learn how
-     * to build JSON schemas [here](https://json-schema.org/).
-     */
-    schema?: { [key: string]: unknown };
-
-    /**
-     * Whether to enable strict schema adherence when generating the output. If set to
-     * true, the model will always follow the exact schema defined in the `schema`
-     * field. Only a subset of JSON Schema is supported when `strict` is `true`. To
-     * learn more, read the
-     * [Structured Outputs guide](https://platform.openai.com/docs/guides/structured-outputs).
-     */
-    strict?: boolean | null;
-  }
-}
-
-/**
- * Default response format. Used to generate text responses.
- */
-export interface ResponseFormatText {
-  /**
-   * The type of response format being defined. Always `text`.
-   */
-  type: 'text';
-}
-
-/**
- * A custom grammar for the model to follow when generating text. Learn more in the
- * [custom grammars guide](https://platform.openai.com/docs/guides/custom-grammars).
- */
-export interface ResponseFormatTextGrammar {
-  /**
-   * The custom grammar for the model to follow.
-   */
-  grammar: string;
-
-  /**
-   * The type of response format being defined. Always `grammar`.
-   */
-  type: 'grammar';
-}
-
-/**
- * Configure the model to generate valid Python code. See the
- * [custom grammars guide](https://platform.openai.com/docs/guides/custom-grammars)
- * for more details.
- */
-export interface ResponseFormatTextPython {
-  /**
-   * The type of response format being defined. Always `python`.
-   */
-  type: 'python';
-}
-
-export type ResponsesModel =
-  | (string & {})
-  | ChatModel
-  | 'o1-pro'
-  | 'o1-pro-2025-03-19'
-  | 'o3-pro'
-  | 'o3-pro-2025-06-10'
-  | 'o3-deep-research'
-  | 'o3-deep-research-2025-06-26'
-  | 'o4-mini-deep-research'
-  | 'o4-mini-deep-research-2025-06-26'
-  | 'computer-use-preview'
-  | 'computer-use-preview-2025-03-11'
-  | 'gpt-5-codex'
-  | 'gpt-5-pro'
-  | 'gpt-5-pro-2025-10-06'
-  | 'gpt-5.1-codex-max';

package/extensions/memory-lancedb/node_modules/.ignored_openai/src/resources/uploads/index.ts

@@ -1,4 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-export { Parts, type UploadPart, type PartCreateParams } from './parts';
-export { Uploads, type Upload, type UploadCreateParams, type UploadCompleteParams } from './uploads';

package/extensions/memory-lancedb/node_modules/.ignored_openai/src/resources/uploads/parts.ts

@@ -1,66 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { APIResource } from '../../core/resource';
-import { APIPromise } from '../../core/api-promise';
-import { type Uploadable } from '../../core/uploads';
-import { RequestOptions } from '../../internal/request-options';
-import { multipartFormRequestOptions } from '../../internal/uploads';
-import { path } from '../../internal/utils/path';
-
-export class Parts extends APIResource {
-  /**
-   * Adds a
-   * [Part](https://platform.openai.com/docs/api-reference/uploads/part-object) to an
-   * [Upload](https://platform.openai.com/docs/api-reference/uploads/object) object.
-   * A Part represents a chunk of bytes from the file you are trying to upload.
-   *
-   * Each Part can be at most 64 MB, and you can add Parts until you hit the Upload
-   * maximum of 8 GB.
-   *
-   * It is possible to add multiple Parts in parallel. You can decide the intended
-   * order of the Parts when you
-   * [complete the Upload](https://platform.openai.com/docs/api-reference/uploads/complete).
-   */
-  create(uploadID: string, body: PartCreateParams, options?: RequestOptions): APIPromise<UploadPart> {
-    return this._client.post(
-      path`/uploads/${uploadID}/parts`,
-      multipartFormRequestOptions({ body, ...options }, this._client),
-    );
-  }
-}
-
-/**
- * The upload Part represents a chunk of bytes we can add to an Upload object.
- */
-export interface UploadPart {
-  /**
-   * The upload Part unique identifier, which can be referenced in API endpoints.
-   */
-  id: string;
-
-  /**
-   * The Unix timestamp (in seconds) for when the Part was created.
-   */
-  created_at: number;
-
-  /**
-   * The object type, which is always `upload.part`.
-   */
-  object: 'upload.part';
-
-  /**
-   * The ID of the Upload object that this Part was added to.
-   */
-  upload_id: string;
-}
-
-export interface PartCreateParams {
-  /**
-   * The chunk of bytes for this Part.
-   */
-  data: Uploadable;
-}
-
-export declare namespace Parts {
-  export { type UploadPart as UploadPart, type PartCreateParams as PartCreateParams };
-}

package/extensions/memory-lancedb/node_modules/.ignored_openai/src/resources/uploads/uploads.ts

@@ -1,195 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { APIResource } from '../../core/resource';
-import * as FilesAPI from '../files';
-import * as PartsAPI from './parts';
-import { PartCreateParams, Parts, UploadPart } from './parts';
-import { APIPromise } from '../../core/api-promise';
-import { RequestOptions } from '../../internal/request-options';
-import { path } from '../../internal/utils/path';
-
-export class Uploads extends APIResource {
-  parts: PartsAPI.Parts = new PartsAPI.Parts(this._client);
-
-  /**
-   * Creates an intermediate
-   * [Upload](https://platform.openai.com/docs/api-reference/uploads/object) object
-   * that you can add
-   * [Parts](https://platform.openai.com/docs/api-reference/uploads/part-object) to.
-   * Currently, an Upload can accept at most 8 GB in total and expires after an hour
-   * after you create it.
-   *
-   * Once you complete the Upload, we will create a
-   * [File](https://platform.openai.com/docs/api-reference/files/object) object that
-   * contains all the parts you uploaded. This File is usable in the rest of our
-   * platform as a regular File object.
-   *
-   * For certain `purpose` values, the correct `mime_type` must be specified. Please
-   * refer to documentation for the
-   * [supported MIME types for your use case](https://platform.openai.com/docs/assistants/tools/file-search#supported-files).
-   *
-   * For guidance on the proper filename extensions for each purpose, please follow
-   * the documentation on
-   * [creating a File](https://platform.openai.com/docs/api-reference/files/create).
-   */
-  create(body: UploadCreateParams, options?: RequestOptions): APIPromise<Upload> {
-    return this._client.post('/uploads', { body, ...options });
-  }
-
-  /**
-   * Cancels the Upload. No Parts may be added after an Upload is cancelled.
-   */
-  cancel(uploadID: string, options?: RequestOptions): APIPromise<Upload> {
-    return this._client.post(path`/uploads/${uploadID}/cancel`, options);
-  }
-
-  /**
-   * Completes the
-   * [Upload](https://platform.openai.com/docs/api-reference/uploads/object).
-   *
-   * Within the returned Upload object, there is a nested
-   * [File](https://platform.openai.com/docs/api-reference/files/object) object that
-   * is ready to use in the rest of the platform.
-   *
-   * You can specify the order of the Parts by passing in an ordered list of the Part
-   * IDs.
-   *
-   * The number of bytes uploaded upon completion must match the number of bytes
-   * initially specified when creating the Upload object. No Parts may be added after
-   * an Upload is completed.
-   */
-  complete(uploadID: string, body: UploadCompleteParams, options?: RequestOptions): APIPromise<Upload> {
-    return this._client.post(path`/uploads/${uploadID}/complete`, { body, ...options });
-  }
-}
-
-/**
- * The Upload object can accept byte chunks in the form of Parts.
- */
-export interface Upload {
-  /**
-   * The Upload unique identifier, which can be referenced in API endpoints.
-   */
-  id: string;
-
-  /**
-   * The intended number of bytes to be uploaded.
-   */
-  bytes: number;
-
-  /**
-   * The Unix timestamp (in seconds) for when the Upload was created.
-   */
-  created_at: number;
-
-  /**
-   * The Unix timestamp (in seconds) for when the Upload will expire.
-   */
-  expires_at: number;
-
-  /**
-   * The name of the file to be uploaded.
-   */
-  filename: string;
-
-  /**
-   * The object type, which is always "upload".
-   */
-  object: 'upload';
-
-  /**
-   * The intended purpose of the file.
-   * [Please refer here](https://platform.openai.com/docs/api-reference/files/object#files/object-purpose)
-   * for acceptable values.
-   */
-  purpose: string;
-
-  /**
-   * The status of the Upload.
-   */
-  status: 'pending' | 'completed' | 'cancelled' | 'expired';
-
-  /**
-   * The `File` object represents a document that has been uploaded to OpenAI.
-   */
-  file?: FilesAPI.FileObject | null;
-}
-
-export interface UploadCreateParams {
-  /**
-   * The number of bytes in the file you are uploading.
-   */
-  bytes: number;
-
-  /**
-   * The name of the file to upload.
-   */
-  filename: string;
-
-  /**
-   * The MIME type of the file.
-   *
-   * This must fall within the supported MIME types for your file purpose. See the
-   * supported MIME types for assistants and vision.
-   */
-  mime_type: string;
-
-  /**
-   * The intended purpose of the uploaded file.
-   *
-   * See the
-   * [documentation on File purposes](https://platform.openai.com/docs/api-reference/files/create#files-create-purpose).
-   */
-  purpose: FilesAPI.FilePurpose;
-
-  /**
-   * The expiration policy for a file. By default, files with `purpose=batch` expire
-   * after 30 days and all other files are persisted until they are manually deleted.
-   */
-  expires_after?: UploadCreateParams.ExpiresAfter;
-}
-
-export namespace UploadCreateParams {
-  /**
-   * The expiration policy for a file. By default, files with `purpose=batch` expire
-   * after 30 days and all other files are persisted until they are manually deleted.
-   */
-  export interface ExpiresAfter {
-    /**
-     * Anchor timestamp after which the expiration policy applies. Supported anchors:
-     * `created_at`.
-     */
-    anchor: 'created_at';
-
-    /**
-     * The number of seconds after the anchor time that the file will expire. Must be
-     * between 3600 (1 hour) and 2592000 (30 days).
-     */
-    seconds: number;
-  }
-}
-
-export interface UploadCompleteParams {
-  /**
-   * The ordered list of Part IDs.
-   */
-  part_ids: Array<string>;
-
-  /**
-   * The optional md5 checksum for the file contents to verify if the bytes uploaded
-   * matches what you expect.
-   */
-  md5?: string;
-}
-
-Uploads.Parts = Parts;
-
-export declare namespace Uploads {
-  export {
-    type Upload as Upload,
-    type UploadCreateParams as UploadCreateParams,
-    type UploadCompleteParams as UploadCompleteParams,
-  };
-
-  export { Parts as Parts, type UploadPart as UploadPart, type PartCreateParams as PartCreateParams };
-}

package/extensions/memory-lancedb/node_modules/.ignored_openai/src/resources/uploads.ts

@@ -1,3 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-export * from './uploads/index';