@alvera-ai/platform-sdk 0.10.0-rc.20 → 0.10.0-rc.22

package/.agent/ai_agents.md

@@ -28,7 +28,7 @@ const { data: created } = await api.aiAgents.create(
     name: 'Contact Us Triage Categorizer',
     description: 'Triages inbound submissions into appointment / job / spam',
 
-    tool_id: chatCompletionToolId,                  // see §2 — must be a tool with intent: 'chat_completion'
+    tool_id: chatCompletionToolId,                  // see §2 — must be a tool with intent: 'llm_enrichment'
 
     model: 'llama3.2:3b',                            // provider-specific model identifier
     data_access: 'unregulated',                      // 'unregulated' | 'regulated' (compliance gate)
@@ -76,7 +76,7 @@ Respond with JSON: {"category": "..."}`,
 
 ### `tool_id` must point to a chat-completion tool
 
-The bound tool's `intent` MUST be `chat_completion`. Tools with
+The bound tool's `intent` MUST be `llm_enrichment`. Tools with
 any other intent (`sms`, `data_exchange`, `status_poller`, …)
 are rejected at create time as a 422 on `/tool_id`.
 
@@ -256,7 +256,7 @@ reference via `additional_context.<slug>`.
 ```
 name                  required string
 description           optional string
-tool_id               required UUID  — must be intent: chat_completion
+tool_id               required UUID  — must be intent: llm_enrichment
 model                 required string — provider-specific identifier
 data_access           required enum  — 'unregulated' | 'regulated'
 temperature           required number
@@ -275,7 +275,7 @@ Standard JSON:API envelopes per `errors.md`. Common rejections:
 
 | `source.pointer`                | Cause                                              |
 |---------------------------------|----------------------------------------------------|
-| `/tool_id`                      | tool's intent isn't `chat_completion`              |
+| `/tool_id`                      | tool's intent isn't `llm_enrichment`              |
 | `/llm_response_schema`          | missing or not a valid JSON Schema object          |
 | `/input_schema`                 | missing or not a valid JSON Schema object          |
 | `/prompt_config/body`           | references a field absent from `input_schema`      |
@@ -390,7 +390,7 @@ with `{ status: 'skipped' }` and no per-agent entries.
    the schema means no structured output and downstream decision
    templates can't reference the agent's fields.
 
-2. **`tool_id` must reference an `intent: 'chat_completion'`
+2. **`tool_id` must reference an `intent: 'llm_enrichment'`
    tool.** Other intents are rejected at create. The chat
    completion tool is typically `tool_body_type: 'rest_api'`
    against an OpenAI-compatible endpoint; the platform appends

package/.agent/connected_apps.md

@@ -229,17 +229,22 @@ and can be retried via `.syncRoutes`.
 ### Sync routes
 
 ```typescript
-const { data: app } = await api.connectedApps.syncRoutes(
+const { data: ack } = await api.connectedApps.syncRoutes(
   tenantSlug, datalakeSlug, appId,
 )
-// app.status            — 'synced' or 'error'
-// app.routes            — refreshed from the primary URL's manifest
-// app.last_synced_at    — refreshed when status is 'synced'
+// 202 Accepted — the sync runs in a background worker:
+// ack.status            — 'enqueued'
+// ack.job_id            — background job id
+// ack.connected_app_id  — echo of the app id
+// ack.enqueued_at       — enqueue timestamp
 ```
 
-This is the explicit "re-fetch and save" verb. Use it after
-deploying a new manifest, fixing a primary URL outage, or
-recovering from `status: 'error'`.
+This is the explicit "re-fetch and save" verb — asynchronous. The
+202 acknowledgement proves the app id resolved and a sync job was
+accepted; the worker then refreshes `routes` + `last_synced_at` and
+lands `status: 'synced'` (or `'error'`) on the app row. Poll
+`.get()` for the outcome. Use it after deploying a new manifest,
+fixing a primary URL outage, or recovering from `status: 'error'`.
 
 Discovery failure modes the platform handles explicitly — each
 leaves the row at `status: 'error'` with `error` populated:

package/.agent/cookbook/appointment-review-sms-workflow.md

@@ -482,7 +482,7 @@ leaves `:pending`. A `:partial` status is expected and fine here:
 one row passed and one was filtered.
 
 ```typescript
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `ra.batch_id IN ('${ctx.batchFulfilled}', '${ctx.batchCancelled}')`,
   mode: 'live',
   manual_override: false,
@@ -493,7 +493,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 120_000
 let status: string | null = null
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   status = log.status ?? null
   if (status && status !== 'pending') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -514,7 +514,7 @@ filtered — would mean the filter is not actually evaluating the
 appointment status.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )
@@ -604,7 +604,7 @@ if (!fulfilledAppointmentId) {
   throw new Error('fulfilled appointment not found via unregulated search')
 }
 
-const { data: execResp } = await api.workflows.execute(tenantSlug, ctx.workflowSlug, {
+const { data: execResp } = await api.workflows.execute(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   dataset_id: fulfilledAppointmentId,
   decision_key: 'send_appointment_review_sms',
   manual_override: true,
@@ -614,7 +614,7 @@ ctx.execWelId = execResp.workflow_execution_log_id!
 const deadline = Date.now() + 60_000
 let welStatus: string | null = null
 while (Date.now() < deadline) {
-  const { data: wel } = await api.workflows.workflowLogs.get(tenantSlug, ctx.workflowSlug, ctx.execWelId)
+  const { data: wel } = await api.workflows.workflowLogs.get(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.execWelId)
   welStatus = (wel as { status?: string }).status ?? null
   if (welStatus && welStatus !== 'pending' && welStatus !== 'executing') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -639,6 +639,7 @@ closing the SMS → reply loop end-to-end.
 ```typescript
 const { data: regulatedWel } = await api.workflows.workflowLogs.get(
   tenantSlug,
+  datalakeSlug,
   ctx.workflowSlug,
   ctx.execWelId,
   { dataAccessMode: 'regulated' },
@@ -655,7 +656,7 @@ if (!tokenMatch) {
 }
 const shortPath = tokenMatch[1]!
 
-const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, ctx.connectedAppSlug, {
+const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: shortPath,
   user_agent: 'cookbook-doctest/appointment-review',
 })
@@ -664,7 +665,7 @@ if (resolved.route_path !== '/forms/review') {
 }
 
 const now = new Date().toISOString()
-const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, ctx.connectedAppSlug, {
+const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: shortPath,
   opened_at: now,
   form_submitted_at: now,

package/.agent/cookbook/birthday-greeting-sms-trigger.md

@@ -393,7 +393,7 @@ life of the run. So this step polls on `total_wels` (every per-row job
 has produced a WEL) rather than waiting for the run to conclude.
 
 ```typescript
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `rle.batch_id IN ('${ctx.batchBirthday}', '${ctx.batchNoDob}')`,
   mode: 'live',
   manual_override: false,
@@ -404,7 +404,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 60_000
 let totalWels = 0
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   if (log.status === 'failed') throw new Error('workflow run reached :failed')
   totalWels = typeof log.total_wels === 'number' ? log.total_wels : 0
   if (totalWels >= 2) break
@@ -424,7 +424,7 @@ old shallow version of this cookbook could never catch that because
 it never ran the workflow at all.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )
@@ -475,7 +475,7 @@ const { data: search } = await api.datasets.search(tenantSlug, datalakeSlug, 'le
 const birthdayLegalEntityId = (search.data?.[0] as { id?: string } | undefined)?.id
 if (!birthdayLegalEntityId) throw new Error('birthday row legal_entity not found via search')
 
-const { data: execResp } = await api.workflows.execute(tenantSlug, ctx.workflowSlug, {
+const { data: execResp } = await api.workflows.execute(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   dataset_id: birthdayLegalEntityId,
   decision_key: 'send_happy_birthday_sms',
   manual_override: true,
@@ -486,7 +486,7 @@ ctx.forceExecWelId = execResp.workflow_execution_log_id!
 const deadline = Date.now() + 60_000
 let welStatus: string | null = null
 while (Date.now() < deadline) {
-  const { data: wel } = await api.workflows.workflowLogs.get(tenantSlug, ctx.workflowSlug, ctx.forceExecWelId)
+  const { data: wel } = await api.workflows.workflowLogs.get(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.forceExecWelId)
   welStatus = (wel as { status?: string }).status ?? null
   if (welStatus && welStatus !== 'pending' && welStatus !== 'executing') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -541,6 +541,7 @@ the page, closing the SMS → reply loop end-to-end.
 ```typescript
 const { data: regulatedWel } = await api.workflows.workflowLogs.get(
   tenantSlug,
+  datalakeSlug,
   ctx.workflowSlug,
   ctx.forceExecWelId,
   { dataAccessMode: 'regulated' },
@@ -557,7 +558,7 @@ if (!tokenMatch) {
 }
 const shortPath = tokenMatch[1]!
 
-const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, ctx.connectedAppSlug, {
+const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: shortPath,
   user_agent: 'cookbook-doctest/birthday-greeting',
 })
@@ -566,7 +567,7 @@ if (resolved.route_path !== '/forms/birthday-greeting') {
 }
 
 const now = new Date().toISOString()
-const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, ctx.connectedAppSlug, {
+const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: shortPath,
   opened_at: now,
   form_submitted_at: now,

package/.agent/cookbook/contact-us-triage-with-llm.md

@@ -159,7 +159,7 @@ toolId = smsToolResp.data.id!
 ## 003 — create the LLM tool
 
 The Triage agent calls a chat-completion endpoint to classify each
-row. The tool's `intent: 'chat_completion'` distinguishes it from
+row. The tool's `intent: 'llm_enrichment'` distinguishes it from
 the SMS tool above; `tool_body_type: 'rest_api'` plus an
 OpenAI-compatible `base_url` lets the platform route Ollama,
 Anthropic, OpenAI, or any other compatible inference server
@@ -174,7 +174,7 @@ discriminated-union schema even though Ollama ignores the header.
 const llmToolResp = await api.tools.create(tenantSlug, datalakeSlug, {
   name: `Cookbook LLM Tool ${runSuffix}`,
   description: 'Ollama-backed chat-completion endpoint for Contact Us triage classification.',
-  intent: 'chat_completion',
+  intent: 'llm_enrichment',
   status: 'active',
   datalake_id: ctx.datalakeId,
   body: {
@@ -454,7 +454,7 @@ const submissionIds = [
 ]
 const idList = submissionIds.map((id) => `'${id}'`).join(', ')
 
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `submission_id IN (${idList})`,
   mode: 'live',
   manual_override: true,
@@ -465,7 +465,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 240_000
 let status: string | null = null
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   status = log.status ?? null
   if (status && status !== 'pending') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -489,7 +489,7 @@ would mean the agent's output did not actually steer the decision;
 this step fails loudly in that case.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )

package/.agent/cookbook/dunning-sms-for-delinquent.md

@@ -401,7 +401,7 @@ leaves `:pending`. A `:partial` status is expected and fine here:
 one row passed and one was filtered.
 
 ```typescript
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `ra.batch_id IN ('${ctx.batchVerified}', '${ctx.batchUnverified}')`,
   mode: 'live',
   manual_override: false,
@@ -412,7 +412,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 120_000
 let status: string | null = null
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   status = log.status ?? null
   if (status && status !== 'pending') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -433,7 +433,7 @@ passed — or both were filtered — would mean the filter is not
 actually evaluating both `customer.phone` and `customer.tax_id`.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )
@@ -511,7 +511,7 @@ the connected-app frontend does when the customer opens the
 payment portal, closing the SMS → reply loop end-to-end.
 
 ```typescript
-const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, ctx.connectedAppSlug, {
+const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: ctx.dunningShortPath,
   user_agent: 'cookbook-doctest/dunning-sms',
 })
@@ -523,7 +523,7 @@ if (!(resolved.message?.body ?? '').includes('needs your attention')) {
 }
 
 const now = new Date().toISOString()
-const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, ctx.connectedAppSlug, {
+const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: ctx.dunningShortPath,
   opened_at: now,
   form_submitted_at: now,

package/.agent/cookbook/kyc-notification-on-account-activation.md

@@ -399,7 +399,7 @@ leaves `:pending`. A `:partial` status is expected and fine here:
 one row passed and one was filtered.
 
 ```typescript
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `rpa.batch_id IN ('${ctx.batchActive}', '${ctx.batchSuspended}')`,
   mode: 'live',
   manual_override: false,
@@ -410,7 +410,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 120_000
 let status: string | null = null
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   status = log.status ?? null
   if (status && status !== 'pending') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -431,7 +431,7 @@ filtered — would mean the filter is not actually evaluating
 `payment_account.status`.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )
@@ -509,7 +509,7 @@ the connected-app frontend does when the account holder opens the
 KYC portal, closing the SMS → reply loop end-to-end.
 
 ```typescript
-const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, ctx.connectedAppSlug, {
+const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: ctx.kycShortPath,
   user_agent: 'cookbook-doctest/kyc-notification',
 })
@@ -521,7 +521,7 @@ if (!(resolved.message?.body ?? '').includes('Alvera PR notification')) {
 }
 
 const now = new Date().toISOString()
-const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, ctx.connectedAppSlug, {
+const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: ctx.kycShortPath,
   opened_at: now,
   form_submitted_at: now,

package/.agent/cookbook/sanctions-screening-with-agent-review.md

@@ -106,7 +106,7 @@ toolId = smsToolResp.data.id!
 
 The Sanctions Review agent calls a chat-completion endpoint to
 disambiguate each gray-zone screening. The tool's
-`intent: 'chat_completion'` distinguishes it from the SMS tool
+`intent: 'llm_enrichment'` distinguishes it from the SMS tool
 above; `tool_body_type: 'rest_api'` plus an OpenAI-compatible
 `base_url` lets the platform route Ollama, Anthropic, OpenAI, or
 any other compatible inference server through the same wire
@@ -119,7 +119,7 @@ though Ollama ignores the header.
 const llmToolResp = await api.tools.create(tenantSlug, datalakeSlug, {
   name: `Cookbook LLM Tool ${runSuffix}`,
   description: 'Ollama-backed chat-completion endpoint for sanctions-screening disambiguation.',
-  intent: 'chat_completion',
+  intent: 'llm_enrichment',
   status: 'active',
   datalake_id: ctx.datalakeId,
   body: {
@@ -487,7 +487,7 @@ is generous because the gray-zone row's enrichment is a live LLM
 inference call.
 
 ```typescript
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `rcs.batch_id IN ('${ctx.batchGrayZone}', '${ctx.batchAutoClear}')`,
   mode: 'live',
   manual_override: false,
@@ -498,7 +498,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 240_000
 let status: string | null = null
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   status = log.status ?? null
   if (status && status !== 'pending') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -525,7 +525,7 @@ The pass-branch WEL carries exactly **two** action execution logs
 the decision rather than firing every action.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )

package/.agent/cookbook/score-leads-with-llm-categorization.md

@@ -169,7 +169,7 @@ toolId = smsToolResp.data.id!
 ## 003 — create the LLM tool
 
 The Score Lead agent calls a chat-completion endpoint to classify each
-row. The tool's `intent: 'chat_completion'` distinguishes it from the
+row. The tool's `intent: 'llm_enrichment'` distinguishes it from the
 SMS tool above; `tool_body_type: 'rest_api'` plus an OpenAI-compatible
 `base_url` lets the platform route Ollama, Anthropic, OpenAI, or any
 other compatible inference server through the same wire format. Local
@@ -182,7 +182,7 @@ Ollama itself ignores the header.
 const llmToolResp = await api.tools.create(tenantSlug, datalakeSlug, {
   name: `Cookbook LLM Tool ${runSuffix}`,
   description: 'Ollama-backed chat-completion endpoint for Score Lead classification.',
-  intent: 'chat_completion',
+  intent: 'llm_enrichment',
   status: 'active',
   datalake_id: ctx.datalakeId,
   body: {
@@ -459,7 +459,7 @@ live LLM inference call.
 const regulatedTable = `regulated_${ctx.gtName}`
 const batchList = (ctx.leadBatchIds as string[]).map((b) => `'${b}'`).join(', ')
 
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `${regulatedTable}.batch_id IN (${batchList})`,
   mode: 'live',
   manual_override: true,
@@ -470,7 +470,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 240_000
 let status: string | null = null
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   status = log.status ?? null
   if (status && status !== 'pending') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -495,7 +495,7 @@ would mean the agent's output did not actually steer the decision;
 this step fails loudly in that case.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )

package/.agent/cookbook/welcome-sms-for-customers.md

@@ -388,7 +388,7 @@ leaves `:pending`. A `:partial` status is expected and fine here:
 one row passed and one was filtered.
 
 ```typescript
-const runResp = await api.workflows.run(tenantSlug, ctx.workflowSlug, {
+const runResp = await api.workflows.run(tenantSlug, datalakeSlug, ctx.workflowSlug, {
   sql_where_clause: `ra.batch_id IN ('${ctx.batchWithPhone}', '${ctx.batchNoPhone}')`,
   mode: 'live',
   manual_override: false,
@@ -399,7 +399,7 @@ ctx.runBatchId = runResp.data.batch_id!
 const deadline = Date.now() + 120_000
 let status: string | null = null
 while (Date.now() < deadline) {
-  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, ctx.workflowSlug, ctx.runLogId)
+  const { data: log } = await api.workflows.batchLogs.refresh(tenantSlug, datalakeSlug, ctx.workflowSlug, ctx.runLogId)
   status = log.status ?? null
   if (status && status !== 'pending') break
   await new Promise((r) => setTimeout(r, 2_000))
@@ -420,7 +420,7 @@ filtered — would mean the filter is not actually evaluating
 `customer.phone`.
 
 ```typescript
-const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, ctx.workflowSlug)
+const { data: wfLogs } = await api.workflows.workflowLogs.list(tenantSlug, datalakeSlug, ctx.workflowSlug)
 const ourWels = (wfLogs.data ?? []).filter(
   (w) => (w as { batch_id?: string }).batch_id === ctx.runBatchId,
 )
@@ -498,7 +498,7 @@ the connected-app frontend does when the customer opens the
 billing portal, closing the SMS → reply loop end-to-end.
 
 ```typescript
-const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, ctx.connectedAppSlug, {
+const { data: resolved } = await api.connectedApps.resolvePage(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: ctx.welcomeShortPath,
   user_agent: 'cookbook-doctest/welcome-sms',
 })
@@ -510,7 +510,7 @@ if (!(resolved.message?.body ?? '').includes('welcome to Alvera Billing')) {
 }
 
 const now = new Date().toISOString()
-const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, ctx.connectedAppSlug, {
+const { data: tracked } = await api.connectedApps.updateMessageTracking(tenantSlug, datalakeSlug, ctx.connectedAppSlug, {
   short_path: ctx.welcomeShortPath,
   opened_at: now,
   form_submitted_at: now,

package/.agent/tools.md

@@ -103,13 +103,12 @@ create time:
    voice          →  rest_api (Twilio Voice, etc.)
    export         →  s3, aws_lambda
    status_poller  →  cloud_watch_log_group, rest_api
-   chat_completion → rest_api (against an OpenAI-compatible
-                                LLM endpoint; the platform appends
-                                /chat/completions to base_url)
-   context_extraction → rest_api (same OpenAI-compatible endpoint
-                                  shape as chat_completion; used by
-                                  AI agents for structured row
-                                  enrichment vs free-form chat)
+   llm_enrichment → rest_api (against an OpenAI-compatible LLM
+                              endpoint; the platform appends
+                              /chat/completions to base_url; the
+                              tool is the complete LLM provider
+                              adapter and AI agents bind it for
+                              structured row enrichment)
 ```
 
 A misaligned pair (e.g. `intent: sms` + `tool_body_type: sftp`)