@k2b/cloud 0.25.0 → 0.27.0

package/src/ai/code-runtime-tools.ts

@@ -6,6 +6,8 @@ import type { RequestActor } from "../server";
 import { signInvocationToken } from "../services/identity/invocation-token";
 import { withActiveIdentitySigner } from "../services/identity/key-ring";
 import { LOCALE_HEADER } from "../shared/locale";
+import { TIMEZONE_COOKIE } from "../shared/time";
+import { CodeToolFailure } from "./browser-code-contracts";
 import { resolveAiCapabilityActor } from "./capability-execution";
 import { CODE_CAPABILITY_TOKEN_HEADER, codeCapabilityOperation } from "./code-capability-transport";
 import { authorizeCodeExecution } from "./code-execution";
@@ -25,6 +27,7 @@ type Context = ToolContext & {
   conversationId?: string;
   turnId?: string;
   locale?: string;
+  timeZone?: string;
   reportProgress?: (message: string) => Promise<void>;
 };
 
@@ -97,6 +100,7 @@ export const runManagedCodeTool =
       const headers = new Headers({ authorization: `Bearer ${signed.token}`, "content-type": "application/json" });
       headers.set(CODE_CAPABILITY_TOKEN_HEADER, callback.token);
       if (context.locale) headers.set(LOCALE_HEADER, context.locale);
+      if (context.timeZone) headers.set("cookie", `${TIMEZONE_COOKIE}=${encodeURIComponent(context.timeZone)}`);
       const response = await fetch(new URL(`/_internal/assistant/tools/${name}`, app.baseUrl), {
         method: "POST",
         headers,
@@ -160,7 +164,12 @@ export async function waitForManagedCodeCall(
       seen.add(approval.id);
       if (approval.decision === null) await request({ id: approval.id, approved });
     }
-    if (state.status === "done") return z.json().parse(state.result);
+    if (state.status === "done") {
+      // Nessi records a thrown error as a failed tool result the model can act on.
+      const failure = CodeToolFailure.safeParse(state.result);
+      if (failure.success) throw new Error([failure.data.error, failure.data.guidance].filter(Boolean).join(" "));
+      return z.json().parse(state.result);
+    }
     if (state.status === "lost")
       throw new Error("The isolated code host was lost. The call was not replayed; inspect saved data before starting a new run.");
     await new Promise<void>((resolve, reject) => {

package/src/ai/code-source-contracts.ts

@@ -48,7 +48,53 @@ const CodeWriteInput = Id.extend({
     .max(64),
 });
 
+const DbName = z
+  .string()
+  .regex(/^[A-Za-z][A-Za-z0-9_]*$/)
+  .max(63);
+const DbColumn = z
+  .object({
+    name: DbName.refine(
+      (name) => !["id", "created_at", "updated_at", "created_by", "updated_by"].includes(name.toLowerCase()),
+      "Omit Cloud-managed columns.",
+    ),
+    type: z.enum(["text", "integer", "real", "boolean", "json", "date", "datetime"]),
+    not_null: z.boolean().optional(),
+    unique: z.boolean().optional(),
+    index: z.boolean().optional(),
+  })
+  .strict();
+const TableWrite = z.enum(["everyone", "own", "managers"]);
+const DatabaseSchemaInput = z.discriminatedUnion("operation", [
+  Id.extend({
+    operation: z.literal("tables.create"),
+    name: DbName,
+    columns: z.array(DbColumn).min(1).max(1000),
+    write: TableWrite.default("everyone"),
+  }),
+  Id.extend({
+    operation: z.literal("tables.update"),
+    table: DbName,
+    changes: z
+      .object({
+        write: TableWrite.optional(),
+        rename: DbName.optional(),
+        add_columns: z.array(DbColumn).optional(),
+        drop_columns: z.array(DbName).optional(),
+        rename_columns: z.record(DbName, DbName).optional(),
+      })
+      .strict(),
+  }),
+  Id.extend({ operation: z.literal("schema.get"), table: DbName }),
+  Id.extend({ operation: z.literal("tables.list") }),
+]);
+
 export const CODE_SOURCE_TOOLS = {
+  code_database: {
+    description:
+      "Manage app tables and schema. Manage permission required. Table write rules are everyone (default), own (only creators update/delete), or managers. Cloud sets created_by/updated_by from trusted identity. Schema belongs here, never in runtime scripts.",
+    input: DatabaseSchemaInput,
+  },
   code_files: {
     description:
       "List authorized files in one explicit chat, Project or App shared store. Returns locations, metadata and nextAfter. Use code_file_stat to obtain the opaque version before copying; does not load bytes into model context.",
@@ -118,18 +164,20 @@ export const CODE_SOURCE_TOOLS = {
   },
   code_storage_list: {
     description:
-      "Inspect an App's shared files or JSON keys for administration. Manage required. Returns storageRevision, counts and a page of key/bytes/mediaType/version metadata; no file contents. Follow nextAfter.",
+      "Inspect shared files/JSON with Manage, or only your personal JSON with scope user and Use. Returns storageRevision, counts and a page of key/bytes/mediaType/version metadata; no file contents. Follow nextAfter.",
     input: Id.extend({
+      scope: z.enum(["shared", "user"]).default("shared").describe("user shows only the signed-in viewer’s personal JSON data."),
       area: z.enum(["files", "kv"]),
       after: z.string().max(240).default(""),
       limit: z.number().int().min(1).max(1000).default(100),
-    }),
+    }).refine((input) => input.scope !== "user" || input.area === "kv", "Personal storage supports JSON keys only."),
   },
   code_storage_delete: {
     description:
-      "Delete one shared file/JSON key, or clear an explicit storage area, with fresh user review. Manage required. Source, publications and database are preserved. Read code_storage_list first.",
+      "Delete one shared file/JSON key or clear an area with fresh review and Manage. Scope user deletes only your personal JSON and requires Use. Source, publications and database are preserved. Read code_storage_list first.",
     review: true,
     input: Id.extend({
+      scope: z.enum(["shared", "user"]).default("shared"),
       area: z.enum(["files", "kv", "all"]),
       key: z.string().min(1).max(240).optional().describe("Delete this exact key; omit to clear the entire area. Not valid with area all."),
       expectedStorageRevision: z
@@ -137,7 +185,9 @@ export const CODE_SOURCE_TOOLS = {
         .int()
         .positive()
         .describe("storageRevision from code_storage_list; concurrent writes invalidate the review."),
-    }).refine((input) => input.area !== "all" || input.key === undefined, "all clears both areas and cannot select a key"),
+    })
+      .refine((input) => input.area !== "all" || input.key === undefined, "all clears both areas and cannot select a key")
+      .refine((input) => input.scope !== "user" || input.area === "kv", "Personal storage supports JSON keys only."),
   },
   code_access_read: {
     description:

package/src/ai/code-source-tools.ts

@@ -27,6 +27,7 @@ const WRITE_TOOLS = new Set([
   "code_publish",
   "code_restore",
   "code_database_export",
+  "code_database",
   ...Object.entries(CODE_SOURCE_TOOLS)
     .filter(([, definition]) => "review" in definition && definition.review)
     .map(([name]) => name),
@@ -62,12 +63,17 @@ export function createCodeSourceTool(name: CodeSourceToolName) {
       code_database_clear: "clear",
       code_database_reset: "reset",
     };
-    const databaseOperation = databaseOperations[name];
+    const databaseOperation =
+      name === "code_database" ? z.object({ operation: z.string() }).parse(input).operation : databaseOperations[name];
     let authorizeDatabase: (() => Promise<void>) | undefined;
     if (context.turnId && databaseOperation) {
       const config = await aiConversations.getTurnRunConfig({ conversationId: context.conversationId, turnId: context.turnId });
       if (config?.kind !== "compact" && config?.background) {
-        const { id } = z.object({ id: z.string() }).parse(input);
+        const {
+          id,
+          table,
+          name: tableName,
+        } = z.object({ id: z.string(), table: z.string().optional(), name: z.string().optional() }).parse(input);
         const conversationId = context.conversationId,
           turnId = context.turnId;
         authorizeDatabase = async () => {
@@ -76,7 +82,7 @@ export function createCodeSourceTool(name: CodeSourceToolName) {
           await aiChatTasks.authorizeRuntime({
             mandate: config.mandate,
             kind: "database",
-            input: { resourceId: id, operation: databaseOperation },
+            input: { resourceId: id, operation: databaseOperation, table: table ?? tableName },
           });
         };
       }
@@ -163,6 +169,7 @@ export const createCodeSourceTools = () => [
   createCodeSourceTool("code_file_stat"),
   createCodeSourceTool("code_file_copy"),
   createCodeSourceTool("code_database_export"),
+  createCodeSourceTool("code_database"),
   createCodeSourceTool("code_manage_read"),
   createCodeSourceTool("code_delete"),
   createCodeSourceTool("code_database_read"),

package/src/ai/credentials.ts

@@ -1,6 +1,7 @@
 import { sql } from "bun";
 import { toPgTextArray } from "../services/postgres";
 import { decryptValue, encryptValue } from "../services/settings/crypto";
+import type { AiRequestHeaderPatch } from "./request-headers";
 
 type SqlClient = typeof sql;
 
@@ -90,7 +91,12 @@ export const pruneAiCredentials = async (keepProfileIds: readonly string[], db:
  */
 export const splitAiProfileCredentials = (
   rawValue: unknown,
-): { profilesJson: string; credentials: Array<{ profileId: string; secret: string }>; profileIds: string[] } | null => {
+): {
+  profilesJson: string;
+  credentials: Array<{ profileId: string; secret: string }>;
+  profileIds: string[];
+  requestHeaders: AiRequestHeaderPatch[];
+} | null => {
   if (typeof rawValue !== "string") return null;
   const text = rawValue;
   let parsed: unknown;
@@ -104,21 +110,29 @@ export const splitAiProfileCredentials = (
   const profiles: unknown[] = [];
   const credentials: Array<{ profileId: string; secret: string }> = [];
   const profileIds: string[] = [];
+  const requestHeaders: AiRequestHeaderPatch[] = [];
 
   for (const entry of parsed) {
     if (!entry || typeof entry !== "object") {
       profiles.push(entry);
       continue;
     }
-    const { apiKey, credentialSetting: _legacy, ...profile } = entry as Record<string, unknown>;
+    const {
+      apiKey,
+      requestHeaders: headerPatch,
+      requestHeaderNames: _headerNames,
+      credentialSetting: _legacy,
+      ...profile
+    } = entry as Record<string, unknown>;
     const profileId = typeof profile.id === "string" ? profile.id.trim() : "";
     if (profileId) {
       profile.id = profileId;
       profileIds.push(profileId);
+      if (headerPatch !== undefined) requestHeaders.push({ profileId, patch: headerPatch });
       if (typeof apiKey === "string" && apiKey.trim()) credentials.push({ profileId, secret: apiKey.trim() });
     }
     profiles.push(profile);
   }
 
-  return { profilesJson: JSON.stringify(profiles), credentials, profileIds };
+  return { profilesJson: JSON.stringify(profiles), credentials, profileIds, requestHeaders };
 };

package/src/ai/data-analysis-skill.ts

@@ -2,9 +2,9 @@
 import type { AiSkillTemplate } from "./skills";
 export const ASSISTANT_DATA_ANALYSIS_SKILL = {
   "key": "assistant:data-analysis",
-  "version": 6,
+  "version": 7,
   "name": "assistant-data-analysis",
   "description": "Analyze source data, explain metrics and comparisons, and build evidence-backed reports or interactive dashboards in Assistant Code Mode. Use for multi-step analysis, data exploration, and dashboards; a simple chart only needs the Code Mode charts reference.",
-  "instructions": "# Analyze data and deliver an inspectable result\n\nStart with the question the reader needs to answer. Choose a direct answer,\nan interactive visualization in this chat, an exported file, or a reusable Studio app accordingly.\nFor a one-time visual analysis, prefer a chat visualization; filters and buttons\ndo not by themselves require a Studio App.\nLoad `assistant-code-mode` for execution and read its `references/analytics.md`\nfor the built-in UI. Loading this skill does not install a library or grant access.\n\n## Keep a working plan\n\nFor work with several real steps, use `todo_write` to keep a short chat plan.\nReplace the full `todos` list each time; give each item a stable `id`, actionable\n`content`, and `status` (`pending`, `in_progress`, `completed`, or `cancelled`).\nAt most one step is active. Update as work changes, including user corrections;\nmark a step completed only after doing and checking it. Preserve exact commands\nwhen they matter. Skip this tool for a simple calculation or conversational reply.\n\nFor analysis, useful steps are reconcile source data, build the analysis, and\nverify totals, filters and conclusions. A rendered dashboard alone is not proof\nthat its numbers are correct. Keep blocked source work open and explain why.\n\n## Establish the data\n\nIdentify the actual source, unit of observation, time window, timezone, and\nlatest complete period. Read files or discover the relevant Cloud capabilities\nbefore selecting fields. External APIs use `http.fetch`; credentials are entered\nonly through the trusted `code_secret` dialog.\n\nInspect a bounded sample, missing values, duplicate keys, types, and coverage.\nReconcile totals and join cardinalities before drawing conclusions. Keep raw\nnumbers separate from display formatting. Distinguish zero from unavailable data;\nstate exclusions and denominator choices. Do not substitute fixture data for a\nblocked source unless the user requested a mockup.\n\nKeep the source query or transformation in the saved source or an accompanying\nfile so another run can reproduce the result. Preserve the source identity and\nretrieval timestamp, without credentials or credential-bearing URLs.\n\n## Build one consistent analysis\n\nDerive charts, metrics, and tables from the same reviewed data. Aggregate large\ninputs before crossing the UI bridge. Chart Explorer rows identify selectable\nentities with stable string keys; derived bins and groups need explicit mark\nmappings. Shared keys across charts mean the same entity, not equal values.\n\nChoose the simplest chart that answers the question. Use tables for exact\nrecords, bars for category comparisons, lines for ordered trends, and distributions\nfor spread. State units, comparison windows, and whether a percent is a fraction\nor an already scaled number. Do not imply causation from correlation.\n\nLead reports with the finding, then supporting evidence and limitations.\nLead dashboards with the important measurements, then trends and diagnostic\nbreakdowns. Use shared filters only when they affect all claimed views. Keep the\ninitial view useful without interaction. Avoid unrelated metrics added merely to\nfill a grid.\n\nAttach source context to Explorer data: `mode`, `asOf`, `sources`, and relevant\n`status`/`note`. A timestamp records when the data was retrieved; it does not prove\nthat the upstream source is complete. Label partial or fixture data visibly.\n\n## Validate before delivery\n\nRun the actual source with `code_run`. Inspect the result; use `code_interact`\nwith structured UI events to test filters, chart/table switching, selection,\nempty results, and recovery from a failed load. Reconcile displayed values with\nthe reviewed totals and check that filters describe the data actually displayed.\nA successful schema validation does not establish analytical correctness.\n\nValidate the actual presented source (the saved revision for Apps), rather than pasting its formulas into a\nsecond test script. Keep an independent expectation from the input data: row\ncounts, unmatched joins, totals and representative boundary cases. For targets,\nstate their grain (for example month × region) and aggregate each target once;\nmultiple selected regions must sum their distinct targets. Compare inspected raw\nKPI values and plotted series with independent expectations. A formatted value\nmatching after rounding does not validate the raw ratio. Never round fractions\nbefore passing them to percent-formatted controls. Preserve precision\nuntil display formatting. Test reset, one/multiple/all selections, empty results,\nand complete versus partial periods. A newly generated timestamp is not source\nfreshness: keep the real retrieval or file-snapshot timestamp stable.\n\nFor a Studio App data snapshot, export the validated dataset with `files.save` and\n`code_export`, then copy its exact path/version into the resource with\n`code_write({id,expectedRevision,files:[{path:\"data.json\",fromFile:reference}]})`.\nObtain the exact reference with `code_file_stat`; importing private files into\nApp source receives fresh review.\nImport that file in the app. Never rebuild a truncated dataset by copying tool\noutput. Keep transformations and source identity alongside the snapshot.\n\nHuman approval and uncertain HTTP outcomes follow the Code Mode HTTP contract.\nDo not replay an external mutation to refresh a chart. Separate local filtering\nfrom external loading; an Apply button can avoid a request for every slider move.\n\n## Save, share, and hand off\n\nFor chat visualizations, test `code_run` and relevant `code_interact` controls,\nthen deliver with `code_present({runId,title})`. A successful run alone is not\nvisible to the user. Retain source identity, reviewed input data and their real\nretrieval timestamp. Put writes and external reloads behind explicit buttons;\nopening an old result must not repeat earlier actions. The user can download the\ncurrent view as PDF/HTML or an individual chart as SVG.\n\nFor reusable Studio Apps, reuse one Cloud resource for later revisions of the same report or dashboard.\nSave its source, test that revision, and use the normal Code Mode publication\nworkflow when publication is requested. Publishing a version and granting reader\naccess are separate operations. Preserve existing access; a dashboard request\ndoes not authorize broadening it. Personal secrets are never copied to readers.\n\nA published source version is not automatically a frozen data snapshot. A frozen\nreport must retain the reviewed data explicitly in its authorized resource or\noutput file. A live app must implement its loader and display the retrieval time;\nloading once is not continuous monitoring. No background refresh exists unless\nimplemented through an appropriate supported workflow.\n\nPresent the chat visualization, resource link or exported file, the data timestamp, and material\ncoverage limitations. Say whether it is a snapshot or reloads from its sources.\nIf publication fails, retain the tested resource and report the failed stage;\ndo not claim success or create a different public destination. Sites-specific\nhosting, access policies, and editor storage are not part of this Cloud workflow.",
+  "instructions": "# Analyze data and deliver an inspectable result\n\nStart with the question the reader needs to answer. Choose a direct answer,\nan interactive visualization in this chat, an exported file, or a reusable Studio app accordingly.\nFor a one-time visual analysis, prefer a chat visualization; filters and buttons\ndo not by themselves require a Studio App.\nLoad `assistant-code-mode` for execution and read its `references/analytics.md`\nfor the built-in UI. Loading this skill does not install a library or grant access.\n\n## Keep a working plan\n\nFor work with several real steps, use `todo_write` to keep a short chat plan.\nReplace the full `todos` list each time; give each item a stable `id`, actionable\n`content`, and `status` (`pending`, `in_progress`, `completed`, or `cancelled`).\nAt most one step is active. Update as work changes, including user corrections;\nmark a step completed only after doing and checking it. Preserve exact commands\nwhen they matter. Skip this tool for a simple calculation or conversational reply.\n\nFor analysis, useful steps are reconcile source data, build the analysis, and\nverify totals, filters and conclusions. A rendered dashboard alone is not proof\nthat its numbers are correct. Keep blocked source work open and explain why.\n\n## Establish the data\n\nIdentify the actual source, unit of observation, time window, timezone, and\nlatest complete period. Read files or discover the relevant Cloud capabilities\nbefore selecting fields. External APIs use `cloud.http.fetch`; credentials are entered\nonly through the trusted `code_secret` dialog.\n\nInspect a bounded sample, missing values, duplicate keys, types, and coverage.\nReconcile totals and join cardinalities before drawing conclusions. Keep raw\nnumbers separate from display formatting. Distinguish zero from unavailable data;\nstate exclusions and denominator choices. Do not substitute fixture data for a\nblocked source unless the user requested a mockup.\n\nKeep the source query or transformation in the saved source or an accompanying\nfile so another run can reproduce the result. Preserve the source identity and\nretrieval timestamp, without credentials or credential-bearing URLs.\n\n## Build one consistent analysis\n\nDerive charts, metrics, and tables from the same reviewed data. Aggregate large\ninputs before crossing the UI bridge. Chart Explorer rows identify selectable\nentities with stable string keys; derived bins and groups need explicit mark\nmappings. Shared keys across charts mean the same entity, not equal values.\n\nChoose the simplest chart that answers the question. Use tables for exact\nrecords, bars for category comparisons, lines for ordered trends, and distributions\nfor spread. State units, comparison windows, and whether a percent is a fraction\nor an already scaled number. Do not imply causation from correlation.\n\nLead reports with the finding, then supporting evidence and limitations.\nLead dashboards with the important measurements, then trends and diagnostic\nbreakdowns. Use shared filters only when they affect all claimed views. Keep the\ninitial view useful without interaction. Avoid unrelated metrics added merely to\nfill a grid.\n\nAttach source context to Explorer data: `mode`, `asOf`, `sources`, and relevant\n`status`/`note`. A timestamp records when the data was retrieved; it does not prove\nthat the upstream source is complete. Label partial or fixture data visibly.\n\n## Validate before delivery\n\nRun the actual source with `code_run`. Inspect the result; use `code_interact`\nwith structured UI events to test filters, chart/table switching, selection,\nempty results, and recovery from a failed load. Reconcile displayed values with\nthe reviewed totals and check that filters describe the data actually displayed.\nA successful schema validation does not establish analytical correctness.\n\nValidate the actual presented source (the saved revision for Apps), rather than pasting its formulas into a\nsecond test script. Keep an independent expectation from the input data: row\ncounts, unmatched joins, totals and representative boundary cases. For targets,\nstate their grain (for example month × region) and aggregate each target once;\nmultiple selected regions must sum their distinct targets. Compare inspected raw\nKPI values and plotted series with independent expectations. A formatted value\nmatching after rounding does not validate the raw ratio. Never round fractions\nbefore passing them to percent-formatted controls. Preserve precision\nuntil display formatting. Test reset, one/multiple/all selections, empty results,\nand complete versus partial periods. A newly generated timestamp is not source\nfreshness: keep the real retrieval or file-snapshot timestamp stable.\n\nFor a Studio App data snapshot, export the validated dataset with `cloud.download` and\n`code_export`, then copy its exact path/version into the resource with\n`code_write({id,expectedRevision,files:[{path:\"data.json\",fromFile:reference}]})`.\nObtain the exact reference with `code_file_stat`; importing private files into\nApp source receives fresh review.\nImport that file in the app. Never rebuild a truncated dataset by copying tool\noutput. Keep transformations and source identity alongside the snapshot.\n\nHuman approval and uncertain HTTP outcomes follow the Code Mode HTTP contract.\nDo not replay an external mutation to refresh a chart. Separate local filtering\nfrom external loading; an Apply button can avoid a request for every slider move.\n\n## Save, share, and hand off\n\nFor chat visualizations, test `code_run` and relevant `code_interact` controls,\nthen deliver with `code_present({runId,title})`. A successful run alone is not\nvisible to the user. Retain source identity, reviewed input data and their real\nretrieval timestamp. Put writes and external reloads behind explicit buttons;\nopening an old result must not repeat earlier actions. The user can download the\ncurrent view as PDF/HTML or an individual chart as SVG.\n\nFor reusable Studio Apps, reuse one Cloud resource for later revisions of the same report or dashboard.\nSave its source, test that revision, and use the normal Code Mode publication\nworkflow when publication is requested. Publishing a version and granting reader\naccess are separate operations. Preserve existing access; a dashboard request\ndoes not authorize broadening it. Personal secrets are never copied to readers.\n\nA published source version is not automatically a frozen data snapshot. A frozen\nreport must retain the reviewed data explicitly in its authorized resource or\noutput file. A live app must implement its loader and display the retrieval time;\nloading once is not continuous monitoring. No background refresh exists unless\nimplemented through an appropriate supported workflow.\n\nPresent the chat visualization, resource link or exported file, the data timestamp, and material\ncoverage limitations. Say whether it is a snapshot or reloads from its sources.\nIf publication fails, retain the tested resource and report the failed stage;\ndo not claim success or create a different public destination. Sites-specific\nhosting, access policies, and editor storage are not part of this Cloud workflow.",
   "extraFrontmatter": {}
 } satisfies AiSkillTemplate;

package/src/ai/default-tools.ts

@@ -110,7 +110,7 @@ export const createCloudAiCodeTools = () => [
   defineAiTool({
     name: "code_secret",
     description:
-      "Open a trusted Secret input dialog. The user enters the value directly into encrypted Assistant storage; only configured/name returns. Never ask for a credential in chat, survey, app controls or code_interact. Personal secrets are scoped to this chat or resource and bound to the exact HTTPS origin, header and prefix. Use secret(name,{prefix}) in http.fetch headers; load assistant-code-mode for HTTP details. Web UI required for secret entry; stored secrets also work from CLI.",
+      "Open a trusted Secret input dialog. The user enters the value directly into encrypted Assistant storage; only configured/name returns. Never ask for a credential in chat, survey, app controls or code_interact. Personal secrets are scoped to this chat or resource and bound to the exact HTTPS origin, header and prefix. Use cloud.http.secret(name,{prefix}) in cloud.http.fetch headers; load assistant-code-mode for HTTP details. Web UI required for secret entry; stored secrets also work from CLI.",
     inputSchema: CodeSecretInput,
     outputSchema: z.object({ configured: z.boolean(), name: z.string() }),
     approval: "never",
@@ -128,7 +128,7 @@ export const createCloudAiCodeTools = () => [
     promptHint:
       "For file analysis, data transformations or combining Cloud data, run a short one-off script with code_run. Load assistant-code-mode for its runtime APIs; no saved app is required.",
     description:
-      "Run a saved resource id OR one-off code in the isolated worker. Optional resourceId binds one-off code to existing app data (Manage required), without editing its source. Includes capabilities.run(name,input) to chain Cloud capabilities in JavaScript; load assistant-code-mode for its runtime APIs. Scripts accept current chat inputPaths; app test runs use them only as explicit picker fixtures. Returns output, logs and UI state for agent inspection only; use code_present to show a one-off visualization to the user. Local test storage is temporary; shared data, database writes and capability effects are real and keep normal permissions and approvals.",
+      "Run a saved resource id OR one-off code in the isolated worker. Optional resourceId binds one-off code to existing app data (Manage required), without editing its source. Includes cloud.capabilities.run(name,input) to chain Cloud capabilities in JavaScript; load assistant-code-mode for its runtime APIs. Scripts accept current chat inputPaths; app test runs use them only as explicit picker fixtures. Returns output, logs and UI state for agent inspection only; use code_present to show a one-off visualization to the user. Test runs use the app’s real shared and personal data; database writes and capability effects keep normal permissions and approvals.",
     inputSchema: CodeRunInput,
     outputSchema: z.json(),
     approval: "never",