maka-agent 0.2.0-dev.62.20260928 → 0.2.0-dev.67.20261002

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/05-ai-sdk-rsc/02-streaming-react-components.mdx

@@ -38,14 +38,14 @@ At a high level, the `streamUI` works like other AI SDK Core functions: you can
 
 ```tsx
 const result = await streamUI({
-  model: openai('gpt-4o'),
+  model: openai('gpt-6-astra'),
   prompt: 'Get the weather for San Francisco',
   text: ({ content }) => <div>{content}</div>,
   tools: {},
 });
 ```
 
-This example calls the `streamUI` function using OpenAI's `gpt-4o` model, passes a prompt, specifies how the model's plain text response (`content`) should be rendered, and then provides an empty object for tools. Even though this example does not define any tools, it will stream the model's response as a `div` rather than plain text.
+This example calls the `streamUI` function using OpenAI's `gpt-6-astra` model, passes a prompt, specifies how the model's plain text response (`content`) should be rendered, and then provides an empty object for tools. Even though this example does not define any tools, it will stream the model's response as a `div` rather than plain text.
 
 ### Adding A Tool
 
@@ -60,7 +60,7 @@ Let's expand the previous example to add a tool.
 
 ```tsx highlight="6-14"
 const result = await streamUI({
-  model: openai('gpt-4o'),
+  model: openai('gpt-6-astra'),
   prompt: 'Get the weather for San Francisco',
   text: ({ content }) => <div>{content}</div>,
   tools: {
@@ -138,7 +138,7 @@ const WeatherComponent = (props: WeatherProps) => (
 
 export async function streamComponent() {
   const result = await streamUI({
-    model: openai('gpt-4o'),
+    model: openai('gpt-6-astra'),
     prompt: 'Get the weather for San Francisco',
     text: ({ content }) => <div>{content}</div>,
     tools: {
@@ -166,7 +166,7 @@ The `getWeather` tool should look familiar as it is identical to the example in
 2. Next, define a `getWeather` function that will timeout for 2 seconds (to simulate fetching the weather externally) before returning the "weather" for a `location`. Note: you could run any asynchronous TypeScript code here.
 3. Finally, define a `WeatherComponent` which takes in `location` and `weather` as props, which are then rendered within a `div`.
 
-Your Server Action is an asynchronous function called `streamComponent` that takes no inputs, and returns a `ReactNode`. Within the action, you call the `streamUI` function, specifying the model (`gpt-4o`), the prompt, the component that should be rendered if the model chooses to return text, and finally, your `getWeather` tool. Last but not least, you return the resulting component generated by the model with `result.value`.
+Your Server Action is an asynchronous function called `streamComponent` that takes no inputs, and returns a `ReactNode`. Within the action, you call the `streamUI` function, specifying the model (`gpt-6-astra`), the prompt, the component that should be rendered if the model chooses to return text, and finally, your `getWeather` tool. Last but not least, you return the resulting component generated by the model with `result.value`.
 
 To call this Server Action and display the resulting React Component, you will need a page.
 

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/05-ai-sdk-rsc/04-multistep-interfaces.mdx

@@ -82,7 +82,7 @@ export async function submitUserMessage(input: string) {
   'use server';
 
   const ui = await streamUI({
-    model: openai('gpt-4o'),
+    model: openai('gpt-6-astra'),
     instructions: 'you are a flight booking assistant',
     prompt: input,
     text: async ({ content }) => <div>{content}</div>,
@@ -219,7 +219,7 @@ This page pulls in the current UI State using the `useUIState` hook, which is th
 
 In this example, to call the next tool, the user must respond with plain text. **Given you are streaming a React component, you can add a button to trigger the next step in the conversation**.
 
-To add user interaction, you will have to convert the component into a client component and use the `useAction` hook to trigger the next step in the conversation.
+To add user interaction, you will have to convert the component into a client component and use the `useActions` hook to trigger the next step in the conversation.
 
 ```tsx filename="components/flights.tsx"
 'use client';

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/05-ai-sdk-rsc/06-loading-state.mdx

@@ -214,7 +214,7 @@ import { streamUI } from '@ai-sdk/rsc';
 
 export async function generateResponse(prompt: string) {
   const result = await streamUI({
-    model: openai('gpt-4o'),
+    model: openai('gpt-6-astra'),
     prompt,
     text: async function* ({ content }) {
       yield <div>loading...</div>;

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/05-ai-sdk-rsc/10-migrating-to-ui.mdx

@@ -47,7 +47,7 @@ export async function sendMessage(message: string) {
   messages.update([...messages.get(), { role: 'user', content: message }]);
 
   const { value: stream } = await streamUI({
-    model: openai('gpt-4o'),
+    model: openai('gpt-6-astra'),
     instructions: 'you are a friendly assistant!',
     messages: messages.get(),
     text: async function* ({ content, done }) {
@@ -187,7 +187,7 @@ import { getWeather } from '@/utils/queries';
 import { Weather } from '@/components/weather';
 
 const { value: stream } = await streamUI({
-  model: openai('gpt-4o'),
+  model: openai('gpt-6-astra'),
   instructions: 'you are a friendly assistant!',
   messages,
   text: async function* ({ content, done }) {
@@ -399,7 +399,7 @@ import { openai } from '@ai-sdk/openai';
 import { streamUI } from '@ai-sdk/rsc';
 
 const { value: stream } = await streamUI({
-  model: openai('gpt-4o'),
+  model: openai('gpt-6-astra'),
   instructions: 'you are a friendly assistant!',
   messages,
   initial: <div>Loading...</div>,

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/06-advanced/02-stopping-streams.mdx

@@ -205,6 +205,14 @@ export async function POST(req: Request) {
 
 The `consumeStream` function is necessary for proper abort handling in UI message streams. It ensures that the stream is properly consumed even when aborted, preventing potential memory leaks or hanging connections.
 
+The `onEnd` callback distinguishes consumer cancellation from an observed
+abort. When the consumer cancels the UI message stream before an outcome is
+declared, such as during a client disconnect, `isCancelled` is `true`,
+`outcome.status` remains `'unknown'`, and `isAborted` remains `false`. When the
+stream observes an `abort` part first, `outcome.status` is `'aborted'`,
+`isAborted` is `true`, and `isCancelled` is absent. Check both flags when the
+same cleanup should run for either case.
+
 ## AI SDK RSC
 
 <Note type="warning">

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/06-advanced/04-caching.mdx

@@ -30,6 +30,7 @@ const redis = new Redis({
 });
 
 export const cacheMiddleware: LanguageModelV4Middleware = {
+  specificationVersion: 'v4',
   wrapGenerate: async ({ doGenerate, params }) => {
     const cacheKey = JSON.stringify(params);
 
@@ -117,7 +118,7 @@ export const cacheMiddleware: LanguageModelV4Middleware = {
   replayed from the cache on later requests.
 </Note>
 
-`LanguageModelV4Middleware` has two methods: `wrapGenerate` and `wrapStream`. `wrapGenerate` is called when using [`generateText`](/docs/reference/ai-sdk-core/generate-text), while `wrapStream` is called when using [`streamText`](/docs/reference/ai-sdk-core/stream-text).
+`LanguageModelV4Middleware` has the `wrapGenerate` and `wrapStream` wrapping methods, plus the optional `transformParams` method. `wrapGenerate` is called when using [`generateText`](/docs/reference/ai-sdk-core/generate-text), while `wrapStream` is called when using [`streamText`](/docs/reference/ai-sdk-core/stream-text).
 
 For `wrapGenerate`, you can cache the response directly. Instead, for `wrapStream`, you cache an array of the stream parts, which can then be used with [`simulateReadableStream`](/docs/ai-sdk-core/testing#simulate-ui-message-stream-responses) function to create a simulated `ReadableStream` that returns the cached response. In this way, the cached response is returned chunk-by-chunk as if it were being generated by the model. You can control the initial delay and delay between chunks by adjusting the `initialDelayInMs` and `chunkDelayInMs` parameters of `simulateReadableStream`.
 

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/06-advanced/11-secure-url-fetching.mdx

@@ -45,6 +45,45 @@ When the SDK fetches a URL taken from a provider response, it:
 
 A blocked URL surfaces as a `DownloadError`.
 
+## Fetching untrusted URLs directly
+
+For custom integrations using `@ai-sdk/provider-utils`, use `fetchUntrustedUrl`
+when the URL comes from a response or other untrusted input. It validates URLs
+and redirects and withholds credentials and unknown custom headers on the first
+request unless the URL matches a configured origin:
+
+```ts
+import { fetchUntrustedUrl } from '@ai-sdk/provider-utils';
+
+const response = await fetchUntrustedUrl({
+  url: result.downloadUrl,
+  headers: {
+    authorization: `Bearer ${apiKey}`,
+    accept: 'image/*',
+  },
+  credentialedOrigin: providerBaseURL,
+});
+```
+
+Here, `Authorization` is sent only when the initial URL has the same origin as
+`providerBaseURL`. Otherwise, only allowlisted metadata such as `Accept`,
+`Range`, and `User-Agent` is sent. A cross-origin redirect drops all caller
+headers except `User-Agent`, and credentials are never reattached on later hops.
+
+`credentialedOrigin` must come from your configuration, never from the response
+URL. It does not disable URL validation. For a configured private endpoint, pass
+`trustedOrigin` as well; if `credentialedOrigin` is omitted, `fetchUntrustedUrl`
+uses `trustedOrigin` as the origin allowed to receive credentials. Extra protocol
+metadata can be allowed with `untrustedFirstHopHeaders: ['x-protocol-version']`.
+Only list headers that are safe to disclose to any destination; use a configured
+origin for credentials.
+
+The existing `fetchWithValidatedRedirects` helper preserves its first-request
+behavior: it sanitizes risky headers but still forwards authentication and
+custom headers. Switch to `fetchUntrustedUrl` to opt into first-request
+credential isolation. Existing calls to `getFromApi` also retain their behavior;
+pass `credentialedOrigin` when fetching response-supplied URLs with credentials.
+
 ## Self-hosted and local endpoints
 
 URLs that are same-origin with the provider endpoint **you configured** (e.g. a
@@ -60,7 +99,13 @@ On Node.js, the default validated download fetch uses `node:dns` and an
 The connector uses those exact results, closing both hostname-to-private-IP and
 DNS-rebinding bypasses.
 
-If you inject or globally replace `fetch`, it is responsible for equivalent DNS
+Wrapping or replacing global `fetch` does not disable this protection: the
+default Node.js download transport is independent of global `fetch`.
+
+Bun, Deno, Cloudflare Workers, and framework edge runtimes use their platform
+fetch, even when they expose a Node-compatible `process` object.
+
+If you explicitly inject a custom `fetch`, it is responsible for equivalent DNS
 validation and connection pinning. Other runtimes do not expose Node's
 DNS/socket hooks, so server deployments on those runtimes should restrict
 network egress to private, loopback, link-local, and cloud-metadata ranges.
@@ -78,7 +123,7 @@ code.
 
 ### 2. Harden an injected `fetch`
 
-The Node.js default is already pinned. If you inject or globally replace
+The Node.js default is already pinned. If you explicitly inject a custom
 `fetch`, back it with an `undici`
 `Agent` whose `connect.lookup` validates the resolved IP and lets the socket
 connect only to a safe address — closing both the hostname-to-private and the

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/01-generate-text.mdx

@@ -40,7 +40,7 @@ To see `generateText` in action, check out [these examples](#examples).
     {
       name: 'model',
       type: 'LanguageModel',
-      description: "The language model to use. Example: openai('gpt-4o')",
+      description: "The language model to use. Example: openai('gpt-6-astra')",
     },
     {
       name: 'instructions',
@@ -929,6 +929,13 @@ To see `generateText` in action, check out [these examples](#examples).
               description:
                 'The error that occurred while parsing the tool call.',
             },
+            {
+              name: 'abortSignal',
+              type: 'AbortSignal',
+              isOptional: true,
+              description:
+                'An optional signal for cancelling the tool call repair.',
+            },
           ],
         },
       ],
@@ -1064,7 +1071,7 @@ To see `generateText` in action, check out [these examples](#examples).
               name: 'Output.json()',
               type: 'Output',
               description:
-                'Output specification for unstructured JSON generation. When the model generates a text response, it will return a JSON object.',
+                'Output specification for unstructured JSON generation. When the model generates a text response, it will return any valid JSON value.',
               properties: [
                 {
                   type: 'Options',
@@ -1110,7 +1117,8 @@ To see `generateText` in action, check out [these examples](#examples).
             {
               name: 'modelId',
               type: 'string',
-              description: 'The specific model identifier (e.g., "gpt-4o").',
+              description:
+                'The specific model identifier (e.g., "gpt-6-astra").',
             },
             {
               name: 'instructions',
@@ -1262,7 +1270,8 @@ To see `generateText` in action, check out [these examples](#examples).
             {
               name: 'modelId',
               type: 'string',
-              description: 'The specific model identifier (e.g., "gpt-4o").',
+              description:
+                'The specific model identifier (e.g., "gpt-6-astra").',
             },
             {
               name: 'instructions',

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/02-stream-text.mdx

@@ -42,7 +42,7 @@ To see `streamText` in action, check out [these examples](#examples).
     {
       name: 'model',
       type: 'LanguageModel',
-      description: "The language model to use. Example: openai('gpt-4.1')",
+      description: "The language model to use. Example: openai('gpt-6-astra')",
     },
     {
       name: 'instructions',
@@ -980,6 +980,13 @@ To see `streamText` in action, check out [these examples](#examples).
               description:
                 'The error that occurred while parsing the tool call.',
             },
+            {
+              name: 'abortSignal',
+              type: 'AbortSignal',
+              isOptional: true,
+              description:
+                'An optional signal for cancelling the tool call repair.',
+            },
           ],
         },
       ],
@@ -2124,7 +2131,8 @@ To see `streamText` in action, check out [these examples](#examples).
             {
               name: 'modelId',
               type: 'string',
-              description: 'The specific model identifier (e.g., "gpt-4o").',
+              description:
+                'The specific model identifier (e.g., "gpt-6-astra").',
             },
             {
               name: 'instructions',
@@ -2276,7 +2284,8 @@ To see `streamText` in action, check out [these examples](#examples).
             {
               name: 'modelId',
               type: 'string',
-              description: 'The specific model identifier (e.g., "gpt-4o").',
+              description:
+                'The specific model identifier (e.g., "gpt-6-astra").',
             },
             {
               name: 'instructions',
@@ -4075,13 +4084,13 @@ To see `streamText` in action, check out [these examples](#examples).
             },
             {
               name: 'onEnd',
-              type: '(options: { messages: UIMessage[]; isContinuation: boolean; responseMessage: UIMessage; isAborted: boolean; outcome: UIMessageStreamOutcome; finishReason?: FinishReason; }) => PromiseLike<void> | void',
+              type: '(options: { messages: UIMessage[]; isContinuation: boolean; responseMessage: UIMessage; isAborted: boolean; isCancelled?: true; outcome: UIMessageStreamOutcome; finishReason?: FinishReason; }) => PromiseLike<void> | void',
               isOptional: true,
-              description: 'Callback function called when the stream ends. Provides the updated messages, continuation and abort state, model finish reason, and operation-level outcome.',
+              description: 'Callback function called when the stream ends. Provides the updated messages, continuation, abort and consumer-cancellation state, model finish reason, and operation-level outcome.',
             },
             {
               name: 'onFinish',
-              type: '(options: { messages: UIMessage[]; isContinuation: boolean; responseMessage: UIMessage; isAborted: boolean; outcome: UIMessageStreamOutcome; finishReason?: FinishReason; }) => PromiseLike<void> | void',
+              type: '(options: { messages: UIMessage[]; isContinuation: boolean; responseMessage: UIMessage; isAborted: boolean; isCancelled?: true; outcome: UIMessageStreamOutcome; finishReason?: FinishReason; }) => PromiseLike<void> | void',
               isOptional: true,
               description: 'Deprecated alias for `onEnd`.',
             },
@@ -4124,7 +4133,7 @@ To see `streamText` in action, check out [these examples](#examples).
               type: '(error: unknown) => string',
               isOptional: true,
               description:
-                'Process an error, e.g. to log it. Returns error message to include in the data stream. Defaults to () => "An error occurred."',
+                'Process an error, e.g. to log it. Returns the error message to include in the data stream. Defaults to () => "An error occurred." Tool execution errors marked providerExecuted: true bypass this callback: strings pass through unchanged and other values are JSON-stringified to preserve provider error data for model-message round trips and harness runtime error messages. Stream errors and invalid tool calls still use this callback.',
             },
             {
               name: 'consumeSseStream',

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/06-rerank.mdx

@@ -14,7 +14,7 @@ import { cohere } from '@ai-sdk/cohere';
 import { rerank } from 'ai';
 
 const { ranking } = await rerank({
-  model: cohere.reranking('rerank-v3.5'),
+  model: cohere.reranking('rerank-v4.0-pro'),
   documents: ['sunny day at the beach', 'rainy afternoon in the city'],
   query: 'talk about rain',
 });
@@ -34,7 +34,7 @@ const { ranking } = await rerank({
       name: 'model',
       type: 'RerankingModel',
       description:
-        "The reranking model to use. Example: cohere.reranking('rerank-v3.5')",
+        "The reranking model to use. Example: cohere.reranking('rerank-v4.0-pro')",
     },
     {
       name: 'documents',
@@ -262,7 +262,7 @@ import { cohere } from '@ai-sdk/cohere';
 import { rerank } from 'ai';
 
 const { ranking, rerankedDocuments } = await rerank({
-  model: cohere.reranking('rerank-v3.5'),
+  model: cohere.reranking('rerank-v4.0-pro'),
   documents: [
     'sunny day at the beach',
     'rainy afternoon in the city',
@@ -302,7 +302,7 @@ const documents = [
 ];
 
 const { ranking } = await rerank({
-  model: cohere.reranking('rerank-v3.5'),
+  model: cohere.reranking('rerank-v4.0-pro'),
   documents,
   query: 'Which pricing did we get from Oracle?',
   topN: 1,
@@ -319,7 +319,7 @@ import { cohere } from '@ai-sdk/cohere';
 import { rerank } from 'ai';
 
 const { ranking } = await rerank({
-  model: cohere.reranking('rerank-v3.5'),
+  model: cohere.reranking('rerank-v4.0-pro'),
   documents: ['sunny day at the beach', 'rainy afternoon in the city'],
   query: 'talk about rain',
   providerOptions: {

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/11-transcribe.mdx

@@ -13,7 +13,7 @@ import { openai } from '@ai-sdk/openai';
 import { readFile } from 'fs/promises';
 
 const { text: transcript } = await transcribe({
-  model: openai.transcription('whisper-1'),
+  model: openai.transcription('gpt-4o-transcribe'),
   audio: await readFile('audio.mp3'),
 });
 

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/12-generate-speech.mdx

@@ -12,7 +12,7 @@ import { generateSpeech } from 'ai';
 import { openai } from '@ai-sdk/openai';
 
 const { audio } = await generateSpeech({
-  model: openai.speech('tts-1'),
+  model: openai.speech('gpt-4o-mini-tts'),
   text: 'Hello from the AI SDK!',
   voice: 'alloy',
 });
@@ -29,7 +29,7 @@ import { generateSpeech } from 'ai';
 import { openai } from '@ai-sdk/openai';
 
 const { audio } = await generateSpeech({
-  model: openai.speech('tts-1'),
+  model: openai.speech('gpt-4o-mini-tts'),
   text: 'Hello from the AI SDK!',
   voice: 'alloy',
 });
@@ -79,7 +79,7 @@ const { audio } = await generateSpeech({
       type: 'string',
       isOptional: true,
       description:
-        'The output format to use for the speech e.g. "mp3", "wav", etc.',
+        'The output format to use for the speech, such as "mp3", "wav", or headerless "audio/l16", "audio/mulaw", and "audio/alaw". Supported formats and defaults vary by provider and model.',
     },
     {
       name: 'instructions',

package/node_modules/ai/docs/07-reference/01-ai-sdk-core/14-evaluate.mdx

@@ -0,0 +1,74 @@
+---
+title: experimental_evaluate
+description: Evaluate typed questions against shared state with an evaluation model.
+---
+
+# `experimental_evaluate()`
+
+```ts
+import { experimental_evaluate } from 'ai';
+```
+
+Evaluates a nonempty map of `choice`, `score`, and `boolean` questions against one
+state. See [Evaluation](/docs/ai-sdk-core/evaluation) for examples and semantics.
+
+## Parameters
+
+| Parameter         | Type                                               | Description                                                                                                                                 |
+| ----------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `model`           | `Experimental_EvaluationModel`                     | Required experimental v4 model instance or a string ID resolved by Gateway or an explicitly configured evaluation-capable default provider. |
+| `state`           | `string \| object \| array`                        | Required JSON-compatible shared state.                                                                                                      |
+| `questions`       | `Record<string, Experimental_EvaluationQuestion>`  | Required nonempty question map.                                                                                                             |
+| `maxRetries`      | `number`                                           | Nonnegative integer; defaults to 2.                                                                                                         |
+| `abortSignal`     | `AbortSignal`                                      | Cancels evaluation.                                                                                                                         |
+| `headers`         | `Record<string, string>`                           | Additional HTTP headers.                                                                                                                    |
+| `providerOptions` | `ProviderOptions`                                  | Provider-specific options.                                                                                                                  |
+| `telemetry`       | `TelemetryOptions`                                 | Telemetry configuration, including per-call integrations, input/output recording, and a function ID.                                        |
+| `runtimeContext`  | `Record<string, unknown>`                          | Context available to lifecycle callbacks and selectively included in telemetry with `telemetry.includeRuntimeContext`.                      |
+| `onStart`         | `(event: Experimental_EvaluateStartEvent) => void` | Called when the evaluation operation begins.                                                                                                |
+| `onEnd`           | `(event: Experimental_EvaluateEndEvent) => void`   | Called when the evaluation operation completes successfully.                                                                                |
+
+See [Lifecycle Callbacks](/docs/ai-sdk-core/lifecycle-callbacks#experimental_evaluate)
+for the complete `onStart` and `onEnd` event fields.
+
+## Result
+
+Returns `Promise<Experimental_EvaluationResult<QUESTIONS>>`:
+
+- `answers`: One typed answer per question ID, with literal Choice option inference.
+- `usage`: `inputTokens`, `outputTokens`, and `totalTokens`, each possibly undefined.
+- `warnings`: Provider warnings, also passed to the SDK warning logger.
+- `rounding`: Optional provider-declared decimal precision for probabilities and scores.
+- `providerMetadata`: Optional provider-specific metadata.
+- `response`: Timestamp, model ID, and optional response ID, headers, and body.
+
+## Provider specification
+
+`Experimental_EvaluationModelV4` is exported from `@ai-sdk/provider` and declares
+`specificationVersion: 'v4'`, `provider`, `modelId`, `supportedQuestionTypes`, and
+`doEvaluate(options)`. Evaluation is isolated from stable `ProviderV4`.
+
+The public core types are `Experimental_EvaluationModel`,
+`Experimental_EvaluationQuestion`, `Experimental_EvaluationAnswer`, and
+`Experimental_EvaluationResult`. All evaluation-specific classes use the
+`Evaluation` prefix, with `Experimental_` aliases at package boundaries.
+
+## Errors
+
+Unsupported types throw `Experimental_EvaluationUnsupportedQuestionTypeError`
+before provider I/O. Invalid inputs throw `InvalidArgumentError`; malformed
+answers throw `InvalidResponseDataError`. Invalid answers are not retried.
+Neither partial results nor missing probability synthesis are supported.
+
+## Model resolution
+
+Use `registry.evaluationModel('provider:model')` or
+`customProvider({ evaluationModels: { alias: model } }).evaluationModel('alias')`
+to resolve models. Strings passed directly to `experimental_evaluate` use
+`globalThis.AI_SDK_DEFAULT_PROVIDER.evaluationModel(id)`, when available. Evaluation
+never implicitly falls back to Gateway.
+
+Resolution errors use the existing `NoSuchModelError` and `NoSuchProviderError`
+classes with `modelType: 'evaluationModel'`. Model instances and resolved models
+must implement v4; other versions throw `UnsupportedModelVersionError`.
+See [model resolution examples](/docs/ai-sdk-core/evaluation#model-aliases-and-registries).

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/16-tool-loop-agent.mdx

@@ -172,7 +172,8 @@ To see `ToolLoopAgent` in action, check out [these examples](#examples).
             {
               name: 'modelId',
               type: 'string',
-              description: 'The specific model identifier (e.g., "gpt-4o").',
+              description:
+                'The specific model identifier (e.g., "gpt-6-astra").',
             },
             {
               name: 'instructions',
@@ -319,7 +320,8 @@ To see `ToolLoopAgent` in action, check out [these examples](#examples).
             {
               name: 'modelId',
               type: 'string',
-              description: 'The specific model identifier (e.g., "gpt-4o").',
+              description:
+                'The specific model identifier (e.g., "gpt-6-astra").',
             },
             {
               name: 'instructions',

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/20-start-batch.mdx

@@ -20,7 +20,7 @@ const batch = await startBatch({
     {
       id: 'france',
       type: 'text',
-      model: 'gpt-4.1-nano',
+      model: 'gpt-5.4-nano',
       prompt: 'What is the capital of France?',
     },
   ],

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/20-tool.mdx

@@ -65,6 +65,13 @@ export const weatherTool = tool({
               description:
                 'Information about the purpose of the tool including details on how and when it can be used by the model. Provide a string for a fixed description, or a function to derive the description from the tool-specific context and optional experimental sandbox before each model call.',
             },
+            {
+              name: 'deferLoading',
+              isOptional: true,
+              type: 'boolean',
+              description:
+                "Keep this tool out of the model context until toolSearch discovers it. Supports direct calling or code mode with toolDiscovery: 'conversation'. Discovered tools become available on the next model step. Defaults to false.",
+            },
             {
               name: 'title',
               isOptional: true,

package/node_modules/{@maka/runtime/node_modules/ai → ai}/docs/07-reference/01-ai-sdk-core/22-dynamic-tool.mdx

@@ -58,6 +58,13 @@ export const customTool = dynamicTool({
               description:
                 'Information about the purpose of the tool including details on how and when it can be used by the model. Provide a string for a fixed description, or a function to derive the description from the tool-specific context and optional experimental sandbox before each model call.'
             },
+            {
+              name: 'deferLoading',
+              isOptional: true,
+              type: 'boolean',
+              description:
+                "Keep this tool out of the model context until toolSearch discovers it. Supports direct calling or code mode with toolDiscovery: 'conversation'. Discovered tools become available on the next model step. Defaults to false.",
+            },
             {
               name: 'title',
               isOptional: true,

package/node_modules/ai/docs/07-reference/01-ai-sdk-core/23-tool-search.mdx

@@ -0,0 +1,76 @@
+---
+title: toolSearch
+description: Search deferred tools and load their definitions on demand for direct calling or code mode.
+---
+
+# `toolSearch()`
+
+Creates a tool that searches the surrounding generation's deferred tools by name
+and description. The factory takes no arguments. Use it with `generateText`,
+`streamText`, `ToolLoopAgent`, or `WorkflowAgent` from `@ai-sdk/workflow`.
+`WorkflowAgent` supports direct tool calling. The other APIs also support code
+mode configured with `toolDiscovery: 'conversation'`.
+
+```ts
+import { toolSearch } from 'ai';
+
+const search = toolSearch();
+```
+
+See the [Tool Search guide](/docs/ai-sdk-core/tool-search) for direct-calling and
+code mode examples, including how code mode preserves the tool-definition cache.
+
+## Model Input
+
+The model supplies the following input to the search tool:
+
+```json
+{ "query": "weather forecast" }
+```
+
+`query` is a required, nonempty string of search keywords. Search is local and
+case-insensitive, matching words in tool names and descriptions. Camel-case names
+are split into words. Name matches rank above description matches; equal scores
+preserve registration order. Function descriptions are resolved with the current
+tool context and sandbox. No embedding service or additional model call is used.
+
+## Output
+
+```ts
+{
+  tools: [
+    { name: 'getForecast', description: 'Get the weather forecast for a city.' },
+  ],
+}
+```
+
+Results contain at most five matching tools, with their names and optional
+descriptions. They do not include schemas. No matches returns `{ tools: [] }`.
+Every returned match is queued for discovery. Newly discovered tools can only be
+called on the next model step, after their definitions have been provided. A
+parallel call in the same response as the search cannot use a newly discovered
+tool. For code mode, finish the current execution and wait for the capability
+update.
+
+## Discovery Lifecycle
+
+Before the next model step, the SDK makes discovered tools available through
+their configured callers:
+
+- **Direct calling:** the provider receives the updated tool definitions.
+- **Code mode:** the SDK appends a user message containing the updated capability
+  catalog. The provider-visible code mode definition stays unchanged. Existing
+  catalogs remain in the conversation; the latest catalog describes the complete
+  currently available tool set.
+
+Actual prompt-cache reuse depends on the provider. Code mode search still requires
+`toolDiscovery: 'conversation'`; description discovery and provider callers are
+not supported.
+
+Discovered tools remain loaded for the rest of the generation, subject to
+`activeTools`. Search cannot discover tools excluded by `activeTools`. Discovery
+state is isolated between generation calls, including calls that reuse the same
+agent or tool instances.
+
+Set a multi-step `stopWhen` condition with `generateText` and `streamText` so the
+model can search, use the discovered tools, and answer.