lua-cli 3.15.3 → 3.16.0

package/node_modules/@lua/shared-types/src/chat-history.types.ts

@@ -1,112 +0,0 @@
-/**
- * Wire-format types for `GET /chat/history/:agentId` and the VM-sandbox
- * `User.getChatHistory()` API. Both paths return the same shape.
- *
- * Shared between lua-core (HTTP controller + VM devtools) and lua-cli
- * (HTTP client typing for `lua test`). Also shared with lua-api's
- * `thread.service.ts` (admin org-thread listing) so the parser never
- * diverges across services.
- */
-
-/**
- * One content part of a chat-history message.
- *
- * `text` parts carry plain text. Media parts (`image` / `video` / `audio`
- * / `file`) carry a URL or base64 payload in `data` (or `image` / `video`
- * for legacy reasons) plus a `mediaType` MIME string.
- */
-export interface ChatHistoryContent {
-  type: 'text' | 'image' | 'video' | 'audio' | 'file';
-  text?: string;
-  image?: string;
-  video?: string;
-  data?: string;
-  mediaType?: string;
-  latitude?: number;
-  longitude?: number;
-}
-
-/**
- * One message returned by chat-history endpoints.
- *
- * Only `user` and `assistant` roles surface — system / tool messages are
- * filtered out before transport.
- */
-export interface ChatHistoryMessage {
-  id: string;
-  role: 'user' | 'assistant';
-  /** ISO-8601 timestamp string. */
-  createdAt: string;
-  content: ChatHistoryContent[];
-}
-
-/**
- * Strip `::: navigate …:::` blocks from a text string.
- *
- * Exposed because both lua-core's chat-history transform and any future
- * external transform may need it independently.
- */
-export function removeNavigateBlock(input: string): string {
-  return input.replace(/::: navigate[\s\S]*?:::/g, '').trim();
-}
-
-/**
- * Transform raw Mastra `MastraMessageContentV2.parts[]` into the
- * `ChatHistoryContent[]` wire shape.
- *
- * Single source of truth for the conversion: used by lua-core's
- * `toChatHistoryMessage` (HTTP + VM sandbox paths) and lua-api's
- * `thread.service.ts` admin org-thread listing. Any future divergence
- * starts here.
- *
- * Parts are deliberately typed `unknown` because callers may either pass
- * Mastra v5 `MastraMessagePart` instances (lua-core, via `@mastra/core`)
- * or raw JSON parsed from a SQL row (lua-api, reading `mastra_messages`
- * directly). The function only inspects `.type`, `.text`, `.data`, and
- * `.mimeType` via property access, so both shapes work.
- */
-export function transformChatHistoryContentParts(parts: unknown[] | undefined | null): ChatHistoryContent[] {
-  const content: ChatHistoryContent[] = [];
-
-  for (const rawPart of parts ?? []) {
-    const part = rawPart as { type?: string; text?: string; data?: string; mimeType?: string };
-    if (part?.type !== 'text' && part?.type !== 'file') continue;
-
-    if (part.type === 'text' && typeof part.text === 'string') {
-      const rawText = part.text || '';
-
-      // Filter out hidden text
-      if (rawText.includes('::: hide')) continue;
-
-      // Check for audio/video markdown patterns and surface as native
-      // audio/video parts (matches the ChatHistoryContent type contract).
-      const audioMatch = rawText.match(/::: audio\s*!\[(.*?)\]\((.*?)\)\s*:::/);
-      const videoMatch = rawText.match(/::: video\s*!\[(.*?)\]\((.*?)\)\s*:::/);
-
-      if (audioMatch) {
-        content.push({ type: 'audio', data: audioMatch[2], mediaType: audioMatch[1] });
-      } else if (videoMatch) {
-        content.push({ type: 'video', video: videoMatch[2], mediaType: videoMatch[1] });
-      } else {
-        // Cleanup text: de-escape \\\\\\n and strip navigate blocks
-        let text = rawText.replace(/\\\\\\n/g, '\n');
-        text = removeNavigateBlock(text);
-        content.push({ type: 'text', text });
-      }
-    } else if (part.type === 'file') {
-      const mediaType = part.mimeType || '';
-
-      if (mediaType.startsWith('image/')) {
-        content.push({ type: 'image', image: part.data, mediaType });
-      } else if (mediaType.startsWith('video/')) {
-        content.push({ type: 'video', video: part.data, mediaType });
-      } else if (mediaType.startsWith('audio/')) {
-        content.push({ type: 'audio', data: part.data, mediaType });
-      } else {
-        content.push({ type: 'file', data: part.data, mediaType });
-      }
-    }
-  }
-
-  return content;
-}

package/node_modules/@lua/shared-types/src/chat-stream.types.ts

@@ -1,18 +0,0 @@
-/**
- * Wire-format contract for `type: 'error'` chunks emitted by lua-core's chat
- * stream. Single source of truth — consumed by lua-whatsapp and any other
- * service that reads the NDJSON chat stream.
- *
- * `code` carries the structural classification across the wire so the
- * consumer (lua-whatsapp et al.) can replicate the same WARN-vs-ERROR
- * policy lua-core applies at its emit site. Currently only set when the
- * underlying error originated from customer-supplied VM-sandbox code
- * (`USER_CODE_ERROR`). Optional — chunks predating LUA-340 omit it.
- */
-export interface ChatErrorChunk {
-  type: 'error';
-  textDelta: string;
-  error: string;
-  code?: 'USER_CODE_ERROR';
-  timestamp: number;
-}

package/node_modules/@lua/shared-types/src/client-tools.types.ts

@@ -1,47 +0,0 @@
-/**
- * Client-Injected Tools
- *
- * Lets a chat client (Lua Desktop, custom front-ends, future surfaces) declare
- * tools that the agent can call but the *client* renders/handles. Mirrors the
- * pattern used by Claude Code, OpenAI Apps SDK, and Anthropic's MCP — the
- * surface the user sees gets to add capabilities to the agent without changing
- * the agent itself.
- *
- * Tool calls flow through Mastra's existing `tool-call` stream chunks; the
- * server registers the tool with a no-op `execute` (returns `{ ok: true,
- * clientHandled: true }`) so the model sees a clean ack and can continue. The
- * actual rendering / side-effect happens on the client when it sees the
- * tool-call chunk.
- *
- * Tool names are namespaced server-side as `client__<name>` to avoid collisions
- * with built-in tools (skills, MCP, devices, voice). Same pattern as device
- * tools (`device__<name>__<command>`).
- */
-export interface ClientToolDef {
-  /** Unprefixed tool name as the client refers to it (e.g. "create_artifact"). Server prefixes with `client__`. */
-  name: string;
-
-  /** Human/LLM-readable description of when to call this tool. */
-  description: string;
-
-  /**
-   * JSON Schema for the tool's input. Hydrated server-side into a Zod schema
-   * via the shared `jsonSchemaToZod` util. Same subset supported as device
-   * tools — object with string/number/boolean/array properties, `required`,
-   * `default`, `description`, `enum`.
-   */
-  parameters: Record<string, unknown>;
-}
-
-/**
- * Server-side prefix for client tool names. Keeps client tools from
- * shadowing skills, MCP tools, devices (`device__`), or voice tools.
- */
-export const CLIENT_TOOL_PREFIX = 'client__';
-
-/**
- * Maximum number of client tools accepted per request. Keeps the model's
- * tool list bounded — at this many tools the model starts losing precision
- * picking the right one anyway.
- */
-export const CLIENT_TOOLS_MAX = 20;

package/node_modules/@lua/shared-types/src/device.types.ts

@@ -1,190 +0,0 @@
-/**
- * Device Gateway Types
- *
- * Types for bidirectional communication between AI agents and external devices.
- * Used across lua-api (gateway), lua-core (runtime), and lua-cli (compilation).
- */
-
-// =============================================================================
-// COMMAND (Agent → Device)
-// =============================================================================
-
-/** Command message sent from the server to a device */
-export interface DeviceCommandMessage {
-  /** Unique identifier for this command (UUID). Used for idempotency. */
-  commandId: string;
-  /** Command name (must match a command defined in defineDevice) */
-  command: string;
-  /** Command payload (validated against inputSchema if defined) */
-  payload: any;
-  /** Timeout in milliseconds (defaults to 30000) */
-  timeout?: number;
-}
-
-/** Response message sent from a device back to the server */
-export interface DeviceResponseMessage {
-  /** Must match the commandId of the original command */
-  commandId: string;
-  /** Whether the command executed successfully on the device */
-  success: boolean;
-  /** Response data (present when success=true) */
-  data?: any;
-  /** Error message (present when success=false) */
-  error?: string;
-}
-
-// =============================================================================
-// TRIGGER (Device → Agent)
-// =============================================================================
-
-/** Trigger message sent from a device to the server */
-export interface DeviceTriggerMessage {
-  /** Trigger name (must match a trigger defined in defineDevice) */
-  triggerName: string;
-  /** Trigger payload (validated against payloadSchema if defined) */
-  payload: any;
-}
-
-/** Acknowledgment sent from the server back to the device after receiving a trigger */
-export interface DeviceTriggerAckMessage {
-  /** Server-generated unique identifier for this trigger event */
-  triggerId: string;
-  /** Whether the trigger was received and queued for processing */
-  received: boolean;
-  /** Error details if the trigger was rejected */
-  error?: string;
-}
-
-// =============================================================================
-// STATE
-// =============================================================================
-
-/** Device connection status */
-export type DeviceStatus = 'online' | 'offline' | 'registered' | 'disabled';
-
-/** State of a command in the Valkey state machine */
-export type CommandState =
-  | 'PENDING' // Command written to stream, not yet consumed
-  | 'SENT' // Consumed by target pod, emitted to socket
-  | 'ACK' // Device acknowledged receipt via Socket.IO ack
-  | 'COMPLETED' // Device responded successfully
-  | 'FAILED' // Device responded with error, or validation failed
-  | 'TIMED_OUT'; // No response within timeout period
-
-// =============================================================================
-// DEVICE INFO
-// =============================================================================
-
-/** Device information returned by API endpoints */
-export interface DeviceInfo {
-  /** Unique device name within the agent */
-  name: string;
-  /** Agent this device belongs to */
-  agentId: string;
-  /** Current connection status */
-  status: DeviceStatus;
-  /** Device group (optional, for fan-out commands) */
-  group?: string;
-  /** Device capabilities */
-  capabilities: string[];
-  /** Free-form device metadata */
-  metadata: Record<string, any>;
-  /** Last time the device was seen (heartbeat or connect) */
-  lastSeenAt: Date | null;
-}
-
-// =============================================================================
-// VALKEY STREAM ENTRIES
-// =============================================================================
-
-/** Entry written to the device command stream */
-export interface CommandStreamEntry {
-  commandId: string;
-  command: string;
-  payload: string; // JSON-serialized
-  originPodId: string;
-  agentId: string;
-  deviceName: string;
-}
-
-/** Entry written to the device response stream */
-export interface ResponseStreamEntry {
-  commandId: string;
-  success: string; // 'true' or 'false' (Redis streams store strings)
-  data?: string; // JSON-serialized
-  error?: string;
-}
-
-/** Entry written to the device trigger stream */
-export interface TriggerStreamEntry {
-  triggerId: string;
-  agentId: string;
-  deviceName: string;
-  deviceId: string;
-  triggerName: string;
-  payload: string; // JSON-serialized
-  timestamp: string;
-}
-
-// =============================================================================
-// VALKEY COMMAND HASH
-// =============================================================================
-
-/** Data stored in the Valkey hash for a command's state */
-export interface CommandHashData {
-  status: CommandState;
-  agentId: string;
-  deviceName: string;
-  originPodId: string;
-  timestamp: number;
-}
-
-// =============================================================================
-// DEVICE DEFINITION (stored in lua-agents, cached in Redis)
-// =============================================================================
-
-/** Device definition as stored in Redis cache */
-export interface CachedDeviceDefinition {
-  name: string;
-  description?: string;
-  group?: string;
-  commands: CachedDeviceCommand[];
-  triggers: CachedDeviceTrigger[];
-  /** Compressed (gzip + base64) compiled artifact containing trigger handlers */
-  artifact: string;
-  /** Environment variables for the device */
-  env: Record<string, string>;
-}
-
-export interface CachedDeviceCommand {
-  name: string;
-  description: string;
-  inputSchema?: Record<string, any>; // JSON Schema
-  retry?: { maxAttempts: number; backoffMs: number };
-  timeoutMs?: number;
-}
-
-export interface CachedDeviceTrigger {
-  name: string;
-  description: string;
-  payloadSchema?: Record<string, any>; // JSON Schema
-  hasExecute: boolean;
-}
-
-/** Command definition sent by a device at connect time (self-describing) */
-export interface DeviceCommandDefinition {
-  name: string;
-  description: string;
-  inputSchema?: Record<string, any>;
-  timeoutMs?: number;
-  retry?: { maxAttempts: number; backoffMs: number };
-}
-
-/** Standalone device trigger definition (compiled agent-side primitive) */
-export interface CachedDeviceTriggerDefinition {
-  name: string;
-  description: string;
-  payloadSchema?: Record<string, any>;
-  artifact: string; // Compressed execute handler
-  env: Record<string, string>;
-}

package/node_modules/@lua/shared-types/src/index.ts

@@ -1,15 +0,0 @@
-export * from './channel.type';
-export * from './persona-text.type';
-export * from './unstructured-types';
-export * from './ai-generate.types';
-export * from './ai-generate.utils';
-export * from './agent-invocation.types';
-export * from './chat-history.types';
-export * from './sandbox-contract';
-export * from './device.types';
-export * from './client-tools.types';
-export * from './model-registry';
-export * from './agent-config.types';
-export * from './persona-defaults';
-export * from './vm-execution-log.types';
-export * from './chat-stream.types';

package/node_modules/@lua/shared-types/src/model-registry.ts

@@ -1,26 +0,0 @@
-/**
- * Shared type definitions for the model registry.
- *
- * Runtime data (provider configs, context windows, approved model list) lives
- * exclusively in the MongoDB `approvedModels` collection. lua-core loads it at
- * startup via initModelRegistry() in mastra/common/model-registry.ts.
- */
-
-export interface ApprovedModelDef {
-  provider: string;
-  /** Full user-facing model string, e.g. "zhipuai/glm-5". */
-  code: string;
-  /** Model ID portion for display, e.g. "glm-5". */
-  model: string;
-  description: string;
-  /** Advertised input token context window (raw, from provider docs). */
-  contextWindow?: number;
-  /** If set, route requests through a gateway instead of calling the provider directly. */
-  gateway?: { via: string; modelPrefix: string };
-  /**
-   * For Vertex models, pins this model to a specific region instead of the
-   * round-robin pool from GOOGLE_VERTEX_LOCATION. Use `"global"` for Gemini 3.x
-   * (global-only). Falls back to round-robin when unset.
-   */
-  vertexLocation?: string;
-}

package/node_modules/@lua/shared-types/src/persona-defaults.ts

@@ -1,59 +0,0 @@
-const AGENT_NAME_TOKEN = '[Your Agent Name]';
-
-/**
- * Structured persona guide template for newly created agents.
- * Each section teaches the developer what to write, with a brief example.
- */
-const DEFAULT_PERSONA_GUIDE = `# ${AGENT_NAME_TOKEN} - Persona
-
-This is a starting template to help you think about your agent's persona.
-Use it as-is, rearrange it, or replace it entirely with your own format — whatever works best for your use case.
-The sections below are suggestions, not requirements.
-
-## Identity & Role
-Who is your agent? What's their name and core purpose?
-- Give it a name and a clear one-line role
-- e.g. a customer support rep, a shopping assistant, an internal ops copilot, a scheduling bot
-
-## Business Context
-What company, product, or service does the agent represent? What does the business do?
-- Describe the business in a sentence or two so the agent understands the world it operates in
-- Include industry, value proposition, and anything the agent should "know" about the brand
-
-## Tone & Communication Style
-How should the agent sound?
-- Formal or casual? Concise or detailed? Empathetic or matter-of-fact?
-- Should it match a specific brand voice or adapt to the user's tone?
-- Any language or cultural considerations (e.g. greetings, local expressions)?
-
-## Target Audience
-Who will the agent be talking to?
-- Describe the typical user: consumers, business customers, internal team members, etc.
-- What do they usually need help with? What matters most to them?
-
-## Capabilities
-What can the agent help with? List the main things it should handle.
-- e.g. answering product questions, placing orders, looking up account info, scheduling meetings
-- Be specific — this shapes which skills and tools the agent will use
-
-## Boundaries
-What should the agent NOT do? When should it escalate to a human?
-- e.g. cannot process refunds, should not give medical/legal advice
-- Define when to hand off: frustrated user, request outside scope, sensitive data
-
-## Guidelines
-Any rules for how the agent behaves?
-- Response length limits (e.g. keep messages under 300 words)
-- Formatting preferences (e.g. use bullet points, avoid jargon)
-- Things to always or never do (e.g. always confirm before changes, never share internal IDs)
-
----
-Feel free to add, remove, or rename sections. Your persona can be a single paragraph or a detailed playbook — whatever gives your agent the context it needs.
-`;
-
-/**
- * Build a default persona guide with the agent name filled in.
- */
-export function buildDefaultPersona(agentName: string): string {
-  return DEFAULT_PERSONA_GUIDE.replace(AGENT_NAME_TOKEN, () => agentName || 'My Agent');
-}

package/node_modules/@lua/shared-types/src/persona-text.type.ts

@@ -1,92 +0,0 @@
-/**
- * Polymorphic shape used by `LuaAgent.persona`. String form is the legacy
- * single-channel persona; object form lets the customer split prose per
- * channel (`base` always rendered; `voice` appended on voice; `text`
- * appended on text channels).
- */
-export type PersonaText = string | { base?: string; voice?: string; text?: string };
-
-/**
- * Same shape as `PersonaText`, exported separately because skill `context`
- * and agent `persona` play different semantic roles. Sharing the structural
- * shape today keeps the runtime lean; future divergence is a one-line change.
- */
-export type SkillContextText = string | { base?: string; voice?: string; text?: string };
-
-export function isPersonaTextObject(value: unknown): value is { base?: string; voice?: string; text?: string } {
-  if (value === null || typeof value !== 'object' || Array.isArray(value)) return false;
-  const obj = value as Record<string, unknown>;
-  for (const k of Object.keys(obj)) {
-    if (k !== 'base' && k !== 'voice' && k !== 'text') return false;
-    if (obj[k] !== undefined && typeof obj[k] !== 'string') return false;
-  }
-  return true;
-}
-
-/**
- * Flatten `PersonaText` or `SkillContextText` to a plain string suitable for
- * LLM prompt injection. `base` is always emitted; `voice` is appended on
- * voice channels and `text` on text channels. Strict — missing channel keys
- * render nothing (no cross-channel fallback).
- */
-export function flattenPersonaText(input: PersonaText | SkillContextText | null | undefined, isVoice = false): string {
-  if (input == null) return '';
-  if (typeof input === 'string') return input;
-  const parts: string[] = [];
-  if (input.base) parts.push(input.base);
-  const channelText = isVoice ? input.voice : input.text;
-  if (channelText) parts.push(channelText);
-  return parts.join('\n\n');
-}
-
-/**
- * Channel-agnostic flatten — concatenates every non-empty channel's content
- * (base + voice + text) for paths that aren't a render-time prompt injection,
- * e.g. AI persona enhancement (storytelling, instructions, website-derived).
- * Use this whenever the call has no channel context but still wants the full
- * persona content — `flattenPersonaText` would silently drop voice or text
- * branches because it defaults to text-channel rendering.
- */
-export function flattenPersonaTextAll(input: PersonaText | SkillContextText | null | undefined): string {
-  if (input == null) return '';
-  if (typeof input === 'string') return input;
-  const parts: string[] = [];
-  if (input.base) parts.push(input.base);
-  if (input.voice) parts.push(input.voice);
-  if (input.text) parts.push(input.text);
-  return parts.join('\n\n');
-}
-
-/**
- * True when the persona has ANY non-empty content on any channel. Used at
- * push/skip boundaries where channel context is not yet known.
- */
-export function hasPersonaTextContent(input: PersonaText | SkillContextText | null | undefined): boolean {
-  if (input == null) return false;
-  if (typeof input === 'string') return input.trim().length > 0;
-  return Boolean(input.base?.trim() || input.voice?.trim() || input.text?.trim());
-}
-
-/**
- * Convert a PersonaText into a TypeScript source-code literal suitable
- * for ts-morph setInitializer or template rendering.
- *
- * - String form → `"..."` (double-quoted) or template literal (when newlines present)
- * - Object form → `{ base: ..., voice: ..., text: ... }` with same per-key rule
- */
-export function personaToLiteral(persona: PersonaText): string {
-  const formatValue = (v: string): string => {
-    if (v.includes('\n')) {
-      return '`' + v.replace(/\\/g, '\\\\').replace(/`/g, '\\`').replace(/\$/g, '\\$') + '`';
-    }
-    return '"' + v.replace(/\\/g, '\\\\').replace(/"/g, '\\"') + '"';
-  };
-
-  if (typeof persona === 'string') return formatValue(persona);
-
-  const parts: string[] = [];
-  if (persona.base !== undefined) parts.push(`base: ${formatValue(persona.base)}`);
-  if (persona.voice !== undefined) parts.push(`voice: ${formatValue(persona.voice)}`);
-  if (persona.text !== undefined) parts.push(`text: ${formatValue(persona.text)}`);
-  return `{ ${parts.join(', ')} }`;
-}

package/node_modules/@lua/shared-types/src/sandbox-contract.ts

@@ -1,63 +0,0 @@
-/**
- * Sandbox contract: defines what every sandbox MUST expose.
- * Both lua-cli and lua-core test against this contract.
- * Update this file when adding new globals or primitives.
- */
-
-// Required primitive shim names (both class-based and function-based)
-export const REQUIRED_PRIMITIVE_SHIMS = [
-  // Class-based
-  'LuaTool',
-  'LuaSkill',
-  'LuaJob',
-  'LuaWebhook',
-  'PreProcessor',
-  'LuaPreprocessor',
-  'PostProcessor',
-  'LuaPostprocessor',
-  'LuaMCPServer',
-  // Function-based
-  'defineTool',
-  'defineSkill',
-  'defineJob',
-  'defineWebhook',
-  'definePreProcessor',
-  'definePostProcessor',
-  'defineMCPServer',
-] as const;
-
-// Required platform API globals with their expected methods
-export const REQUIRED_PLATFORM_APIS = {
-  User: ['get', 'getChatHistory'],
-  Products: ['get', 'create', 'delete', 'search', 'getById'],
-  Baskets: [
-    'create',
-    'get',
-    'addItem',
-    'removeItem',
-    'clear',
-    'updateStatus',
-    'updateMetadata',
-    'placeOrder',
-    'getById',
-  ],
-  Orders: ['create', 'updateStatus', 'updateData', 'get', 'getById'],
-  Data: ['create', 'get', 'getEntry', 'update', 'search', 'delete'],
-  Jobs: ['create', 'getJob', 'getAll'],
-  AI: ['generate'],
-  CDN: ['upload', 'get'],
-} as const;
-
-export const REQUIRED_NESTED_APIS = {
-  Templates: { whatsapp: ['list', 'get', 'send'] },
-  Lua: { request: ['channel'] },
-} as const;
-
-// Required enums with expected keys
-export const REQUIRED_ENUMS = {
-  BasketStatus: ['ACTIVE', 'CHECKED_OUT', 'ABANDONED', 'EXPIRED'],
-  OrderStatus: ['PENDING', 'CONFIRMED', 'FULFILLED', 'CANCELLED'],
-} as const;
-
-// Required utility functions
-export const REQUIRED_UTILITIES = ['env'] as const;