@leaflow/sdk 0.26.0 → 0.28.0

package/dist/assistant/v1/schema.d.ts

@@ -934,6 +934,8 @@ export interface components {
         ContextResource: {
             /** Format: int64 */
             compactAt: number | null;
+            /** @description What kinds of input the model behind this conversation accepts, as modality names: text, image. A client uses this to decide whether a control exists — an attach button on a model that cannot read pictures is a control whose only outcome is a refusal, and the refusal arrives after somebody has chosen a file. An empty list is not a claim that the model reads nothing: it means this deployment has not stated the modalities, or the conversation names a model that has since been retired. Treat empty as unknown and keep the control, because hiding one for a reason nobody can see is worse than a refusal that says why. */
+            inputModalities: string[];
             model: string;
             /** Format: int64 */
             used: number | null;
@@ -1197,7 +1199,7 @@ export interface components {
         };
         /** @description The function object from the OpenAI tools format. */
         ClientFunctionRequest: {
-            /** @description What the action does, written for the model. An action without one can only be guessed at from its name. */
+            /** @description What the action does, written for the model. An action without one can only be guessed at from its name. The 1024 ceiling is OpenAI's own limit on `tools[].function.description`, not a number chosen here: over it the upstream call fails with `string_above_max_length`, and refusing at submission is the clearer of the two places to refuse. It was 500, which ran out at about six enumerated entries — an action that must list what it accepts had nowhere to put the list. */
             description: string;
             /** @description The MCP and Anthropic spelling of `parameters`. Give one or the other, not both. */
             inputSchema?: {

package/dist/billing/v1/index.d.ts

@@ -0,0 +1,38 @@
+export type { paths, components, operations, webhooks } from "./schema.js";
+import type { operations } from "./schema.js";
+/** `GET /account/v1/billing-accounts` 成功时的响应体。 */
+export type ListBillingAccountsResult = operations["list-billing-accounts"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts` 成功时的响应体。 */
+export type CreateBillingAccountResult = operations["create-billing-account"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts` 的请求体。 */
+export type CreateBillingAccountBody = NonNullable<operations["create-billing-account"]["requestBody"]>["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/balance` 成功时的响应体。 */
+export type ReadBillingAccountBalanceResult = operations["read-billing-account-balance"]["responses"][200]["content"]["application/json"];
+/** `PUT /account/v1/billing-accounts/{accountKey}/projects/{projectId}` 成功时的响应体。 */
+export type BindProjectToBillingAccountResult = operations["bind-project-to-billing-account"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts/{accountKey}/top-ups` 成功时的响应体。 */
+export type StartTopUpResult = operations["start-top-up"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts/{accountKey}/top-ups` 的请求体。 */
+export type StartTopUpBody = NonNullable<operations["start-top-up"]["requestBody"]>["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/charges` 成功时的响应体。 */
+export type ListChargesResult = operations["list-charges"]["responses"][200]["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/invoices` 成功时的响应体。 */
+export type ListInvoicesResult = operations["list-invoices"]["responses"][200]["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/invoices/{invoiceId}` 成功时的响应体。 */
+export type GetInvoiceResult = operations["get-invoice"]["responses"][200]["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/subscription` 成功时的响应体。 */
+export type ReadSubscriptionResult = operations["read-subscription"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts/{accountKey}/subscription/cancel` 成功时的响应体。 */
+export type CancelSubscriptionResult = operations["cancel-subscription"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts/{accountKey}/subscription/cancel` 的查询参数。 */
+export type CancelSubscriptionQuery = operations["cancel-subscription"]["parameters"]["query"];
+/** `GET /account/v1/billing-accounts/{accountKey}/top-ups/{paymentId}` 成功时的响应体。 */
+export type ReadTopUpResult = operations["read-top-up"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts/{accountKey}/card` 成功时的响应体。 */
+export type StartCardSetupResult = operations["start-card-setup"]["responses"][200]["content"]["application/json"];
+/** `GET /account/v1/billing-accounts/{accountKey}/offers` 成功时的响应体。 */
+export type ListOffersResult = operations["list-offers"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts/{accountKey}/offers/{offerKey}/purchase` 成功时的响应体。 */
+export type PurchaseOfferResult = operations["purchase-offer"]["responses"][200]["content"]["application/json"];
+/** `POST /account/v1/billing-accounts/{accountKey}/offers/{offerKey}/purchase` 的查询参数。 */
+export type PurchaseOfferQuery = operations["purchase-offer"]["parameters"]["query"];

package/dist/billing/v1/index.js

@@ -0,0 +1,5 @@
+// 由 scripts/generate-ts.mjs 生成，不要手改。
+//
+// 别名把 operations[...] 那串下标换成一个名字。原始的 paths / components / operations 也
+// 一并导出：paths 是给 openapi-fetch 的 createClient<paths>() 用的。
+export {};