lua-cli 3.15.3 → 3.16.0

package/dist/cli/command-definitions.js

@@ -1,943 +0,0 @@
-/**
- * Command Definitions
- * Centralized command structure for the CLI
- */
-import { configureCommand, initCommand, destroyCommand, apiKeyCommand, compileCommand, testCommand, pushCommand, deployCommand, chatCommand, chatClearCommand, envCommand, personaCommand, productionCommand, resourcesCommand, adminCommand, evalsCommand, docsCommand, channelsCommand, logsCommand, completionCommand, skillsCommand, webhooksCommand, devicesCommand, jobsCommand, featuresCommand, preprocessorsCommand, postprocessorsCommand, marketplaceCommand, mcpCommand, syncCommand, integrationsCommand, agentsCommand, updateCommand, telemetryCommand, governanceCommand, modelsCommand, statusCommand, } from '../commands/index.js';
-import { sourceListCommand, sourceRollbackCommand } from '../commands/source.js';
-import { writeError } from '../utils/cli.js';
-/**
- * Sets up authentication-related commands.
- *
- * Commands:
- * - `lua auth configure` - Set up API key
- * - `lua auth logout` - Delete stored API key
- * - `lua auth key` - Display current API key
- *
- * @param program - Commander program instance
- */
-export function setupAuthCommands(program) {
-    const authCommand = program
-        .command('auth')
-        .description('🔐 Authentication management')
-        .addHelpText('after', `
-Examples:
-  $ lua auth configure                           Interactive setup (choose API key or email)
-  $ lua auth configure --api-key "lk_xxx..."     Set API key directly (non-interactive)
-  $ lua auth configure --email user@example.com  Request OTP via email
-  $ lua auth configure --email user@example.com --otp 123456  Complete OTP verification
-  $ lua auth key                                 View your current API key (prompts for confirmation)
-  $ lua auth key --force                         View your current API key without confirmation
-  $ lua auth logout                              Remove stored credentials (prompts for confirmation)
-  $ lua auth logout --force                      Remove stored credentials without confirmation
-`);
-    authCommand
-        .command('configure')
-        .description('Set up your API key')
-        .option('--api-key <key>', 'Set API key directly (non-interactive)')
-        .option('--email <email>', 'Email address for OTP authentication')
-        .option('--otp <code>', 'OTP code received via email (use with --email)')
-        .addHelpText('after', `
-Non-Interactive Modes:
-  --api-key <key>                  Set API key directly (for CI/CD or when you have a key from dashboard)
-  --email <email>                  Request OTP to be sent to email (step 1 of OTP flow)
-  --email <email> --otp <code>     Verify OTP and generate API key (step 2 of OTP flow)
-
-Examples:
-  $ lua auth configure                                      Interactive setup
-  $ lua auth configure --api-key "lk_abc123..."             Direct API key setup
-  $ lua auth configure --email user@example.com             Request OTP (check email)
-  $ lua auth configure --email user@example.com --otp 123456  Complete OTP flow
-`)
-        .action(configureCommand);
-    authCommand
-        .command('logout')
-        .description('Delete your stored API key')
-        .option('--force', 'Skip confirmation prompt')
-        .action(destroyCommand);
-    authCommand
-        .command('key')
-        .description('Display your stored API key')
-        .option('--force', 'Skip confirmation prompt')
-        .action(apiKeyCommand);
-}
-/**
- * Sets up marketplace commands.
- *
- * @param program - Commander program instance
- */
-export function setupMarketplaceCommands(program) {
-    program
-        .command('marketplace [role] [action]')
-        .description('🛍️  Browse, install, and manage marketplace skills')
-        .option('--skill-name <name>', 'Skill name (for creator list, installer update/uninstall)')
-        .option('--display-name <name>', 'Display name (for creator list/update)')
-        .option('--marketplace-id <id>', 'Marketplace skill ID')
-        .option('--version-id <id>', 'Version ID (for publish/install)')
-        .option('--changelog <text>', 'Changelog for version (for publish)')
-        .option('--env-vars-json <json>', 'JSON string with env var metadata (for creator publish)')
-        .option('--env-vars <pairs>', 'Comma-separated key=value pairs (for installer)')
-        .option('--query <text>', 'Search query (for search)')
-        .option('--page <n>', 'Page number (for search)')
-        .option('--limit <n>', 'Results per page (for search)')
-        .option('--json', 'Output as JSON')
-        .option('--force', 'Skip confirmation prompts')
-        .addHelpText('after', `
-Arguments:
-  role                   Optional: 'create' or 'install' (prompts if not provided)
-  action                 Optional: specific action for non-interactive mode
-
-Creator Actions:
-  list      --skill-name <name> --display-name <name>
-  publish   --marketplace-id <id> --version-id <id> [--changelog <text>] [--env-vars-json <json>]
-  update    --marketplace-id <id> --display-name <name>
-  unlist    --marketplace-id <id> --force
-  unpublish --marketplace-id <id> --version-id <id> --force
-  view      [--json]
-
-Installer Actions:
-  search    [--query <text>] [--page <n>] [--limit <n>] [--json]
-  view      --marketplace-id <id> [--json]
-  install   --marketplace-id <id> --version-id <id> [--env-vars <k=v,...>] --force
-  update    --skill-name <name> [--version-id <id>] [--env-vars <k=v,...>]
-  uninstall --skill-name <name> --force
-  installed [--json]
-
-Examples:
-  $ lua marketplace                                              Interactive selection
-  $ lua marketplace create                                       Creator menu
-  $ lua marketplace install                                      Installer menu
-  $ lua marketplace create view                                  View my listed skills
-  $ lua marketplace create list --skill-name mySkill --display-name "My Skill"
-  $ lua marketplace create publish --marketplace-id xyz --version-id v1
-  $ lua marketplace create unlist --marketplace-id xyz --force
-  $ lua marketplace install search --query "CRM"
-  $ lua marketplace install view --marketplace-id xyz --json
-  $ lua marketplace install install --marketplace-id xyz --version-id v1 --force
-  $ lua marketplace install installed --json
-`)
-        .action(marketplaceCommand);
-}
-/**
- * Sets up skill management commands.
- *
- * @param program - Commander program instance
- */
-export function setupSkillCommands(program) {
-    // Project Setup
-    program
-        .command('init')
-        .description('🚀 Initialize a new Lua skill project')
-        .option('--with-examples', 'Include example skills, tools, jobs, and webhooks')
-        .option('--agent-id <id>', 'Use existing agent by ID (non-interactive)')
-        .option('--agent-name <name>', 'Name for new agent (requires --org-id or --org-name)')
-        .option('--org-id <id>', 'Use existing organization by ID')
-        .option('--org-name <name>', 'Create new organization with this name')
-        .option('--model <model>', "LLM model code to use (e.g. 'openai/gpt-4o')")
-        .option('--force', 'Skip confirmations / overwrite existing project')
-        .option('--restore-sources', 'Restore project source files from backup (with --agent-id)')
-        .option('--from-agent-id <id>', 'Duplicate an existing agent into a new one (with project backup restored)')
-        .option('--include-resources', 'Include resources + RAG when duplicating')
-        .option('--include-custom-data', 'Include custom data when duplicating')
-        .option('--include-inquiry-form', 'Include inquiry forms when duplicating')
-        .option('--include-devices', 'Include device + trigger definitions when duplicating')
-        .option('--include-ecommerce-catalog', 'Include ecommerce catalog when duplicating')
-        .option('--promo-code <code>', 'Apply a promo code for bonus credits')
-        .addHelpText('after', `
-Non-Interactive Mode:
-  --agent-id <id>                              Use existing agent
-  --agent-name <name> --org-id <id>            Create agent in existing org
-  --agent-name <name> --org-name <name>        Create agent + new org
-  --from-agent-id <id>                         Duplicate agent + scaffold project
-  --from-agent-id <id> --org-id <id>           Cross-org duplicate
-  --model <model>                              Set LLM model (e.g. openai/gpt-4o)
-  --force                                      Override existing project
-  --restore-sources                            Auto-restore sources from backup
-
-Examples:
-  $ lua init                                                   Interactive setup
-  $ lua init --with-examples                                   Include example code
-  $ lua init --agent-id abc123                                 Use existing agent
-  $ lua init --agent-id abc123 --restore-sources               Use agent + restore backup
-  $ lua init --agent-name "My Bot" --org-id org456             Create in existing org
-  $ lua init --agent-name "My Bot" --org-name "Acme"           Create agent + org
-  $ lua init --agent-id abc123 --force                         Override existing project
-  $ lua init --agent-id abc123 --with-examples                 Use agent + include examples
-  $ lua init --agent-name "My Bot" --org-name "Acme" --model openai/gpt-4o  Create with model
-  $ lua init --from-agent-id baseAgent_agent_xxx                  Duplicate agent + scaffold project
-  $ lua init --from-agent-id baseAgent_agent_xxx --org-id <id>    Cross-org duplicate
-`)
-        .action(initCommand);
-    // Development Commands
-    program
-        .command('compile')
-        .description('📦 Compile skill to deployable format')
-        .option('--verbose', 'Show detailed progress output')
-        .option('--debug', 'Enable debug mode with extra verbose logging and temp file preservation')
-        .option('--sync', 'Run drift detection check before compiling')
-        .action((opts) => compileCommand({ ...opts, topLevel: true }));
-    program
-        .command('sync')
-        .description('🔄 Sync local code with server state')
-        .option('--check', 'Check for drift only, exit code 1 if drift found')
-        .option('--pull', 'Pull server state to local without prompting')
-        .option('--accept', 'Alias for --pull (kept for backwards compatibility)')
-        .option('--push', 'Push local changes to server without prompting')
-        .option('--force', 'Skip the local-changes conflict check (use with --pull / --accept)')
-        .addHelpText('after', `
-Detects drift between server-deployed state and local code.
-Resolves drift by syncing in either direction.
-
-Syncs name, persona, model, and all primitives (skills, webhooks, jobs,
-preprocessors, postprocessors, MCP servers). Source-bearing primitives are
-pulled from the source snapshot in S3; primitives without snapshot coverage
-are reported honestly so you know what's missing.
-
-Before --pull overwrites local files, the conflict guard refuses if any
-file has been modified since your last \`lua push backup\`. Pass --force
-to bypass (destructive — cannot be undone).
-
-Options:
-  --check          Check for drift only (CI validation, exits with code 1 if drift found)
-  --pull           Pull: Update local code from server state (source is restored from snapshot)
-  --accept         Alias for --pull
-  --push           Push: Push local changes to server (see "lua push all --force" for full push)
-  --force          Skip the local-changes conflict check (use with --pull / --accept)
-
-Examples:
-  $ lua sync              Interactive drift resolution (choose push or pull per item)
-  $ lua sync --check      CI: Fail if drift detected
-  $ lua sync --pull       CI: Pull server state to local (guarded)
-  $ lua sync --pull --force  Pull unconditionally (overwrites local changes)
-  $ lua sync --push       CI: Push local changes to server
-`)
-        .action((opts) => syncCommand({ ...opts, accept: opts.pull || opts.accept }));
-    program
-        .command('test [type]')
-        .description('🧪 Test skills, webhooks, or jobs interactively')
-        .option('--name <name>', 'Entity name to test')
-        .option('--input <json>', 'JSON input string for testing')
-        .option('--json', 'Output result as raw JSON (useful for scripting and piping)')
-        .addHelpText('after', `
-Arguments:
-  type                   Optional: 'skill', 'webhook', or 'job' (prompts if not provided)
-
-Options:
-  --name <name>          Entity name to test (non-interactive selection)
-  --input <json>         JSON input string for testing (non-interactive input)
-  --json                 Output result as raw JSON instead of formatted inspect output
-
-Examples:
-  $ lua test                                          Interactive selection
-  $ lua test skill                                    Test a skill/tool directly
-  $ lua test webhook                                  Test a webhook with query/headers/body
-  $ lua test job                                      Test a job by executing it
-  $ lua test skill --name mySkill --input '{}'        Test skill with JSON input
-  $ lua test webhook --name myWebhook --input '{...}' Test webhook with data
-  $ lua test job --name myJob                         Test job execution
-  $ lua test skill --name mySkill --json              Output raw JSON for scripting
-`)
-        .action(testCommand);
-    // Deployment Commands
-    program
-        .command('push [type]')
-        .description('☁️  Push skill, agent, webhook, job, MCP server, or backup to server')
-        .option('--force', 'Skip all confirmation prompts (auto-confirm)')
-        .option('--auto-deploy', 'Automatically deploy to production after push')
-        .option('--name <name>', 'Entity name to push')
-        .option('--set-version <version>', 'Version to set (e.g., 1.0.5)')
-        // `--fresh` is only meaningful for `lua push backup`. The auto-backup
-        // hook always uses fresh=true internally; this flag exposes the same
-        // behavior to users who hit the manual `lua push backup` path and
-        // want to capture out-of-band file changes (e.g. Builder writes) that
-        // a stale dist-v2/manifest.json would silently miss.
-        .option('--fresh', 'Build backup manifest from disk instead of compiled manifest.json (push backup only)')
-        // Default ON. The post-push source attach is non-fatal — a failure logs
-        // a warning but doesn't fail the push.
-        .option('--no-include-source', 'Skip the per-skill source attach after push (default: attach, so admin Builder UI sees CLI edits)')
-        .addHelpText('after', `
-Arguments:
-  type                   Optional: 'skill', 'agent', 'persona', 'webhook', 'job', 'preprocessor', 'postprocessor', 'mcp', 'backup', or 'all' (prompts if not provided)
-
-Options:
-  --force                Skip all confirmation prompts
-  --auto-deploy          Automatically deploy to production after push
-  --name <name>          Entity name to push (non-interactive selection)
-  --set-version <ver>    Version to set (e.g., 1.0.5)
-  --fresh                (push backup) Walk disk for the manifest instead of trusting dist-v2/manifest.json
-  --no-include-source    Skip the per-skill source attach after push (default: attach, so admin Builder UI reflects CLI edits)
-
-Examples:
-  $ lua push                                                Interactive selection
-  $ lua push skill                                          Push a skill directly
-  $ lua push agent                                          Push agent config (persona, model)
-  $ lua push agent --force                                  Push agent config without prompts
-  $ lua push webhook                                        Push a webhook directly
-  $ lua push job                                            Push a job directly
-  $ lua push mcp                                            Push an MCP server directly
-  $ lua push backup                                         Push project source backup
-  $ lua push backup --fresh                                 Push backup, building manifest from disk
-  $ lua push all --force                                    Push all components without prompts
-  $ lua push all --force --auto-deploy                      Push and deploy all to production
-  $ lua push skill --name mySkill --set-version 1.0.5      Push skill with specific version
-  $ lua push webhook --name myWebhook --set-version 2.0.0  Push webhook with version
-`)
-        .action(pushCommand);
-    program
-        .command('deploy [type]')
-        .description('🚀 Deploy a version to production')
-        .option('--name <name>', 'Entity name to deploy (non-interactive selection)')
-        .option('--set-version <ver>', "Version to deploy, or 'latest' for newest version")
-        .option('--force', 'Skip confirmation prompt')
-        // Deprecated aliases kept for backward compatibility
-        .option('--skill-name <name>', 'Deprecated: use --name')
-        .option('--skill-version <ver>', 'Deprecated: use --set-version')
-        .addHelpText('after', `
-Arguments:
-  type    Optional: skill | webhook | job | preprocessor | postprocessor | persona | all (prompts if not provided)
-
-Options:
-  --name <name>         Entity name to deploy (non-interactive selection)
-  --set-version <ver>   Version to deploy, or 'latest' for newest version
-  --force               Skip confirmation prompt
-
-Examples:
-  $ lua deploy                                                        Interactive selection
-  $ lua deploy skill                                                  Deploy a skill version
-  $ lua deploy webhook                                                Deploy a webhook version
-  $ lua deploy job                                                    Deploy a job version
-  $ lua deploy persona                                                Deploy a persona version
-  $ lua deploy all --force                                            Deploy latest version of all
-  $ lua deploy skill --name mySkill --set-version 1.0.5 --force      Deploy specific version
-  $ lua deploy webhook --name myWebhook --set-version latest --force  Deploy latest webhook version
-`)
-        .action(deployCommand);
-    // Chat Commands
-    const chatCmd = program
-        .command('chat')
-        .description('💬 Interactive chat with your agent')
-        .option('-e, --env <environment>', 'Environment: sandbox or production')
-        .option('-m, --message <text>', 'Message to send (non-interactive mode)')
-        .option('-b, --batch <messages...>', 'Send multiple messages concurrently to test batching')
-        .option('-d, --delay <ms>', 'Delay between batch messages in ms (default: 100)')
-        .option('-t, --thread [id]', 'Thread ID for conversation scoping. If no ID is provided, a UUID is auto-generated. Displayed at session start so you can reuse it later.')
-        .option('--clear', 'Automatically clear chat history when session ends (clears thread if -t is used, otherwise clears all history)')
-        .option('--clear-thread', 'Alias for --clear')
-        .addHelpText('after', `
-Examples:
-  $ lua chat                                     Start interactive chat session
-  $ lua chat clear                               Clear all conversation history
-  $ lua chat --clear                             Start chat and clear history on exit
-  $ lua chat -e sandbox -m "hello"               Send message to sandbox
-  $ lua chat -e production -m "test"             Send message to production
-  $ lua chat -m "message"                        Send message to sandbox (default)
-  $ lua chat --thread my-test                    Chat scoped to thread "my-test"
-  $ lua chat -t                                  Chat scoped to a new auto-generated thread
-  $ lua chat -t my-test --clear                  Chat in "my-test" thread, clear on exit
-  $ lua chat -m "test" -t my-test --clear        Non-interactive: isolated thread, clear after
-  $ lua chat -b "Hello" "What is the weather?" "Tell me a joke" -d 2000 -e sandbox  Batch test
-`)
-        .action(chatCommand);
-    chatCmd
-        .command('clear')
-        .description('Clear conversation history')
-        .option('--user <identifier>', 'User ID, email, or mobile number of the user whose history to clear')
-        .option('-t, --thread <id>', "Clear a specific thread's history instead of all history")
-        .option('--force', 'Skip confirmation prompt')
-        .addHelpText('after', `
-Examples:
-  $ lua chat clear                                   Clear history
-  $ lua chat clear --force                           Clear history without confirmation
-  $ lua chat clear --user <userId>                   Clear user's history by user ID
-  $ lua chat clear --user <email>                    Clear user's history by email
-  $ lua chat clear --user <mobile>                   Clear user's history by mobile number
-  $ lua chat clear --user <userId> --force           Clear user's history without confirmation
-  $ lua chat clear --thread <threadId>               Clear a specific thread's history
-  $ lua chat clear --thread <threadId> --force       Clear a specific thread's history without confirmation
-
-Notes:
-  - User identifier can be UUID, email address, or mobile number
-  - Mobile numbers should be in international format without + (e.g., 919876543210)
-`)
-        .action(chatClearCommand);
-    // Configuration Commands
-    program
-        .command('env [environment]')
-        .description('⚙️  Manage environment variables')
-        .option('-k, --key <name>', 'Environment variable key')
-        .option('-v, --value <value>', 'Environment variable value')
-        .option('-d, --delete', 'Delete the specified key')
-        .option('--list', 'List all environment variables')
-        .addHelpText('after', `
-Arguments:
-  environment            Optional: 'sandbox', 'staging', or 'production' (prompts if not provided)
-
-Examples:
-  $ lua env                                    Interactive selection
-  $ lua env sandbox                            Manage sandbox env vars directly
-  $ lua env staging                            Manage staging env vars (alias for sandbox)
-  $ lua env production                         Manage production env vars directly
-  $ lua env sandbox --list                     List sandbox variables
-  $ lua env production --list                  List production variables
-  $ lua env sandbox -k TEST_KEY -v "value"    Set sandbox variable
-  $ lua env production -k API_KEY -v "secret" Set production variable
-  $ lua env production -k OLD_KEY --delete     Delete production variable
-`)
-        .action(envCommand);
-    program
-        .command('persona [env] [action]')
-        .description('🤖 Manage agent persona')
-        .option('--persona-version <version>', "Version number or 'latest' for deploy")
-        .option('--force', 'Skip confirmation prompt')
-        .addHelpText('after', `
-Arguments:
-  env                      Optional: 'sandbox', 'staging', or 'production' (prompts if not provided)
-  action                   Optional (production only): 'view', 'versions', 'deploy'
-
-Options:
-  --persona-version <ver>  Version number or 'latest' for deploy action
-  --force                  Skip confirmation prompt
-
-Examples:
-  $ lua persona                                                 Interactive selection
-  $ lua persona sandbox                                         Manage sandbox persona interactively
-  $ lua persona production                                      Manage production persona interactively
-  $ lua persona production view                                 View current deployed persona
-  $ lua persona production versions                             List all persona versions
-  $ lua persona production deploy --persona-version 5           Deploy version 5
-  $ lua persona production deploy --persona-version latest --force Deploy latest without prompt
-`)
-        .action(personaCommand);
-    program
-        .command('production [action]')
-        .description('🚀 View and manage production environment')
-        .addHelpText('after', `
-Arguments:
-  action                 Optional: 'overview', 'persona', 'skills', 'env' (prompts if not provided)
-
-Examples:
-  $ lua production              Interactive management
-  $ lua production overview     Show production summary
-  $ lua production persona      View current persona
-  $ lua production skills       View deployed skills
-  $ lua production env          List environment variables
-`)
-        .action(productionCommand);
-    program
-        .command('resources [action]')
-        .description('📚 Manage agent resources and knowledge base')
-        .option('--resource-name <name>', 'Resource name')
-        .addHelpText('after', `
-Arguments:
-  action                   Optional: 'list', 'view', 'delete' (prompts if not provided)
-
-Options:
-  --resource-name <name>   Resource name (required for view/delete actions)
-
-Note: 'create' and 'update' require interactive mode.
-
-Examples:
-  $ lua resources                                  Interactive management
-  $ lua resources list                             List all resources
-  $ lua resources view --resource-name "FAQ Doc"   View resource content
-  $ lua resources delete --resource-name "Old Doc" Delete a resource
-`)
-        .action(resourcesCommand);
-    program.command('admin').description('🔧 Open Lua Admin Dashboard in browser').action(adminCommand);
-    program.command('evals').description('📊 Open Lua Evaluations Dashboard in browser').action(evalsCommand);
-    program.command('docs').description('📖 Open Lua documentation in browser').action(docsCommand);
-    program
-        .command('channels [action]')
-        .description('📡 Manage agent communication channels')
-        .addHelpText('after', `
-Arguments:
-  action                 Optional: 'list' (prompts if not provided)
-
-Note: Channel creation requires interactive mode due to complex multi-step input.
-
-Examples:
-  $ lua channels              Interactive management
-  $ lua channels list         List all channels
-`)
-        .action(channelsCommand);
-    program
-        .command('logs')
-        .description('📊 View agent and skill logs')
-        .option('--type <type>', 'Filter by type: all, skill, job, webhook, preprocessor, postprocessor, user_message, agent_response, mcp, mastra')
-        .option('--name <name>', 'Entity name to filter (requires --type)')
-        .option('--user-id <userId>', 'Filter logs by user ID')
-        .option('--agent-id <agentId>', 'View logs for a specific agent ID (admin access required)')
-        .option('--limit <n>', 'Number of logs to show (default: 20)')
-        .option('--page <n>', 'Page number for pagination')
-        .option('--json', 'Output as JSON (for scripting)')
-        .addHelpText('after', `
-Options:
-  --type <type>          Filter by type: all, skill, job, webhook, preprocessor, postprocessor, user_message, agent_response, mcp, mastra
-  --name <name>          Entity name to filter (requires --type, not for message types)
-  --user-id <userId>     Filter logs by user ID
-  --agent-id <agentId>   View logs for a specific agent ID (admin access required, overrides the agent in lua.config.yaml)
-  --limit <n>            Number of logs to show (default: 20)
-  --page <n>             Page number for pagination
-  --json                 Output as JSON for scripting
-
-Examples:
-  $ lua logs                                      Interactive selection
-  $ lua logs --type all --limit 50                Last 50 logs
-  $ lua logs --type skill --name mySkill --limit 10  Skill-specific logs
-  $ lua logs --type job --name healthCheck --json JSON output for CI
-  $ lua logs --type mcp                           View MCP tool execution logs
-  $ lua logs --type mastra                        View Mastra AI runtime logs
-  $ lua logs --user-id user-123                   View all logs for a user
-  $ lua logs --user-id user-123 --type skill      View skill logs for a user
-  $ lua logs --user-id user-123 --json > user-logs.json  Export user logs
-  $ lua logs --agent-id agent-abc123              Logs for a different agent you admin
-  $ lua logs --agent-id agent-abc123 --type skill Skill logs for another agent
-`)
-        .action(logsCommand);
-    program
-        .command('skills [actionOrEnv] [action]')
-        .description('⚙️  Manage and view skills')
-        .option('--skill-name <name>', 'Skill name')
-        .option('--skill-version <version>', "Version for deploy action (or 'latest')")
-        .addHelpText('after', `
-Arguments:
-  actionOrEnv              Optional: environment ('sandbox', 'production') or action ('view', 'versions', 'deploy', 'delete')
-
-Options:
-  --skill-name <name>      Skill name (for versions/deploy/delete actions)
-  --skill-version <ver>    Version for deploy action, or 'latest'
-
-Examples:
-  $ lua skills                                                 Interactive selection
-  $ lua skills sandbox                                         View sandbox skills
-  $ lua skills production                                      Manage production skills
-  $ lua skills view                                            List all production skills
-  $ lua skills versions --skill-name mySkill                   View skill versions
-  $ lua skills deploy --skill-name mySkill --skill-version 1.0.3   Deploy specific version
-  $ lua skills deploy --skill-name mySkill --skill-version latest  Deploy latest version
-  $ lua skills delete --skill-name mySkill                     Delete a skill from server
-`)
-        .action(skillsCommand);
-    program
-        .command('webhooks [action]')
-        .description('🪝 Manage and view webhooks')
-        .option('--webhook-name <name>', 'Webhook name')
-        .option('--webhook-version <version>', "Version for deploy action (or 'latest')")
-        .option('--event <eventType>', 'Event type for subscribe/unsubscribe (e.g. message.delivered)')
-        .addHelpText('after', `
-Arguments:
-  action                   Optional: 'view', 'versions', 'deploy', 'activate', 'deactivate', 'delete',
-                           'list-events', 'subscribe', 'unsubscribe' (prompts if not provided)
-
-Options:
-  --webhook-name <name>    Webhook name (required for most actions)
-  --webhook-version <ver>  Version for deploy action, or 'latest'
-  --event <eventType>      Event type for subscribe/unsubscribe (e.g. message.delivered)
-
-Examples:
-  $ lua webhooks                                                   Interactive management
-  $ lua webhooks view                                              List all webhooks
-  $ lua webhooks activate --webhook-name myWebhook                 Activate a webhook
-  $ lua webhooks deactivate --webhook-name myWebhook               Deactivate a webhook
-  $ lua webhooks delete --webhook-name myWebhook                   Delete a webhook
-  $ lua webhooks versions --webhook-name myWebhook                 View webhook versions
-  $ lua webhooks deploy --webhook-name myWebhook --webhook-version 1.0.3   Deploy specific version
-  $ lua webhooks deploy --webhook-name myWebhook --webhook-version latest  Deploy latest version
-  $ lua webhooks list-events                                       List available event types
-  $ lua webhooks subscribe --webhook-name myWebhook --event message.delivered    Subscribe to event
-  $ lua webhooks unsubscribe --webhook-name myWebhook --event message.delivered  Unsubscribe from event
-`)
-        .action(webhooksCommand);
-    program
-        .command('devices [action]')
-        .description('📡 Manage connected devices')
-        .option('--device-name <name>', 'Device name')
-        .option('--group <group>', 'Filter by device group')
-        .option('--payload <json>', 'JSON payload for test/test-trigger', '{}')
-        .option('--timeout <ms>', 'Timeout in milliseconds', '30000')
-        .option('--force', 'Skip confirmation prompts')
-        .addHelpText('after', `
-Arguments:
-  action                   Optional: list, status, enable, disable, remove, test, test-trigger
-
-Options:
-  --device-name <name>     Device name (required for most actions, prompted if not provided)
-  --group <group>          Filter device list by group
-  --payload <json>         JSON payload for test command or test-trigger
-  --timeout <ms>           Command timeout in milliseconds (default: 30000)
-  --force                  Skip confirmation prompts
-
-Examples:
-  $ lua devices                                                     Interactive management
-  $ lua devices list                                                List all devices
-  $ lua devices list --group printers                               List devices in group
-  $ lua devices status --device-name label-printer                  Check device status
-  $ lua devices enable --device-name label-printer                  Enable a device
-  $ lua devices disable --device-name label-printer                 Disable a device
-  $ lua devices remove --device-name label-printer                  Remove a device
-  $ lua devices remove --device-name label-printer --force          Remove without confirmation
-  $ lua devices test --device-name label-printer                    Test a command interactively
-  $ lua devices test-trigger --device-name label-printer            Test a trigger
-`)
-        .action(devicesCommand);
-    program
-        .command('jobs [action]')
-        .description('⏰ Manage and view scheduled jobs')
-        .option('-i, --job-name <name>', 'Job name')
-        .option('-v, --job-version <version>', "Version for deploy action (or 'latest')")
-        .addHelpText('after', `
-Arguments:
-  action               Optional: view, versions, deploy, activate, deactivate, trigger, history, delete
-
-Options:
-  -i, --job-name <name>    Job name (required for most actions)
-  -v, --job-version <ver>  Version for deploy action, or 'latest'
-
-Examples:
-  $ lua jobs                                           Interactive management
-  $ lua jobs view                                      List all jobs
-  $ lua jobs trigger -i healthCheck                    Trigger a job
-  $ lua jobs activate -i myJob                         Activate a job
-  $ lua jobs deactivate -i myJob                       Deactivate a job
-  $ lua jobs delete -i myJob                           Delete a job
-  $ lua jobs deploy -i myJob -v 1.0.3                  Deploy specific version
-  $ lua jobs deploy -i myJob -v latest                 Deploy latest version
-  $ lua jobs versions -i myJob                         View job versions
-  $ lua jobs history -i myJob                          View execution history
-`)
-        .action(jobsCommand);
-    program
-        .command('features [action]')
-        .description('🎯 Manage agent features (RAG, webSearch, inquiry)')
-        .option('--feature-name <name>', 'Feature name')
-        .addHelpText('after', `
-Arguments:
-  action                   Optional: 'list', 'enable', 'disable', 'view' (prompts if not provided)
-
-Options:
-  --feature-name <name>    Feature name (required for enable/disable/view actions)
-
-Examples:
-  $ lua features                                Interactive management
-  $ lua features list                           List all features
-  $ lua features enable --feature-name rag  Enable a feature
-  $ lua features disable --feature-name rag     Disable a feature
-  $ lua features view --feature-name webSearch  View feature details
-`)
-        .action(featuresCommand);
-    program
-        .command('preprocessors [action]')
-        .description('📥 Manage message preprocessors')
-        .option('--preprocessor-name <name>', 'PreProcessor name')
-        .option('--preprocessor-version <version>', "Version for deploy action (or 'latest')")
-        .addHelpText('after', `
-Arguments:
-  action                       Optional: 'view', 'versions', 'deploy', 'activate', 'deactivate', 'delete' (prompts if not provided)
-
-Options:
-  --preprocessor-name <name>   PreProcessor name (required for most actions)
-  --preprocessor-version <ver> Version for deploy action, or 'latest'
-
-Examples:
-  $ lua preprocessors                                                      Interactive management
-  $ lua preprocessors view                                                 List all preprocessors
-  $ lua preprocessors activate --preprocessor-name myPre                   Activate a preprocessor
-  $ lua preprocessors deactivate --preprocessor-name myPre                 Deactivate a preprocessor
-  $ lua preprocessors versions --preprocessor-name myPre                   View preprocessor versions
-  $ lua preprocessors deploy --preprocessor-name myPre --preprocessor-version 1.0.3   Deploy specific version
-  $ lua preprocessors deploy --preprocessor-name myPre --preprocessor-version latest  Deploy latest version
-  $ lua preprocessors delete --preprocessor-name oldPre                    Delete a preprocessor
-`)
-        .action(preprocessorsCommand);
-    program
-        .command('postprocessors [action]')
-        .description('📤 Manage response postprocessors')
-        .option('--postprocessor-name <name>', 'PostProcessor name')
-        .option('--postprocessor-version <version>', "Version for deploy action (or 'latest')")
-        .addHelpText('after', `
-Arguments:
-  action                        Optional: 'view', 'versions', 'deploy', 'activate', 'deactivate', 'delete' (prompts if not provided)
-
-Options:
-  --postprocessor-name <name>   PostProcessor name (required for most actions)
-  --postprocessor-version <ver> Version for deploy action, or 'latest'
-
-Examples:
-  $ lua postprocessors                                                        Interactive management
-  $ lua postprocessors view                                                   List all postprocessors
-  $ lua postprocessors activate --postprocessor-name myPost                   Activate a postprocessor
-  $ lua postprocessors deactivate --postprocessor-name myPost                 Deactivate a postprocessor
-  $ lua postprocessors versions --postprocessor-name myPost                   View postprocessor versions
-  $ lua postprocessors deploy --postprocessor-name myPost --postprocessor-version 1.0.3   Deploy specific version
-  $ lua postprocessors deploy --postprocessor-name myPost --postprocessor-version latest  Deploy latest version
-  $ lua postprocessors delete --postprocessor-name oldPost                    Delete a postprocessor
-`)
-        .action(postprocessorsCommand);
-    program
-        .command('mcp [action] [name]')
-        .description('🔌 Manage MCP (Model Context Protocol) servers')
-        .option('--server-name <name>', 'MCP server name')
-        .addHelpText('after', `
-Arguments:
-  action                 Optional: 'list', 'activate', 'deactivate', or 'delete'
-  name                   Optional: server name (positional, alternative to --server-name flag)
-
-Options:
-  --server-name <name>   MCP server name (for activate/deactivate/delete actions)
-
-Examples:
-  $ lua mcp                                     Interactive management
-  $ lua mcp list                                List all MCP servers
-  $ lua mcp activate --server-name filesystem   Activate a server (flag style)
-  $ lua mcp activate filesystem                 Activate a server (positional style)
-  $ lua mcp deactivate --server-name api-server Deactivate a server
-  $ lua mcp delete --server-name old-server     Delete a server
-`)
-        .action(mcpCommand);
-    program
-        .command('integrations [action] [subaction]')
-        .description('🔗 Connect third-party integrations via Unified.to')
-        .option('--integration <type>', 'Integration type (e.g., linear, googlecalendar)')
-        .option('--auth-method <method>', "Authentication method: 'oauth' or 'token'")
-        .option('--scopes <scopes>', "Comma-separated OAuth scopes (or 'all' for all scopes)")
-        .option('--hide-sensitive <bool>', 'Hide sensitive data from MCP tools (default: true)')
-        .option('--connection-id <id>', 'Connection ID to disconnect or pause/resume')
-        .option('--connection <id>', 'Connection ID for trigger')
-        .option('--webhook-id <id>', 'Trigger ID to delete/pause/resume')
-        .option('--object <type>', 'Object type for webhook (e.g., task_task, calendar_event)')
-        .option('--event <type>', 'Event type for webhook: created, updated, or deleted')
-        .option('--hook-url <url>', 'Custom webhook URL (default: agent trigger)')
-        .option('--interval <minutes>', 'Polling interval for virtual webhooks (60, 120, 240, 480, 720, 1440, 2880)')
-        .option('--triggers <events>', 'Comma-separated triggers (e.g., task_task.created,task_task.updated)')
-        .option('--custom-webhook', 'Use custom webhook URL instead of agent trigger')
-        .option('--json', 'Output as JSON (for info and webhooks events commands)')
-        .option('--reason <text>', 'Optional reason for pausing a trigger')
-        .addHelpText('after', `
-Arguments:
-  action                 Optional: 'connect', 'update', 'list', 'available', 'info', 'disconnect', 'webhooks', or 'mcp'
-  subaction              For info: <integration-type>
-                         For webhooks: 'list', 'events', 'create', or 'delete'
-                         For mcp: 'list', 'activate', or 'deactivate'
-
-Options:
-  --integration <type>   Integration type (linear, googlecalendar, hubspot, etc.)
-  --auth-method <method> Authentication method: 'oauth' or 'token'
-  --scopes <scopes>      Comma-separated OAuth scopes, or 'all' for all available scopes
-  --hide-sensitive <bool> Hide sensitive data from MCP tools (default: true, use 'false' to show)
-  --triggers <events>    Comma-separated triggers to enable (e.g., task_task.created,task_task.updated)
-  --custom-webhook       Use custom webhook URL instead of agent trigger
-  --hook-url <url>       Custom webhook URL (use with --custom-webhook)
-  --json                 Output as JSON (for info and webhooks events commands)
-
-Webhook/Trigger Options:
-  --connection <id>      Connection ID for webhook or MCP operations
-  --connection-id <id>   Connection ID to disconnect
-  --webhook-id <id>      Trigger ID to delete
-  --object <type>        Object type (task_task, calendar_event, messaging_message, etc.)
-  --event <type>         Event type: created, updated, or deleted
-  --interval <minutes>   Polling interval for virtual webhooks (60=1h, 120=2h, etc.)
-
-Note: Only 1 connection per integration type is allowed per agent.
-
-Examples:
-  $ lua integrations                                    Interactive management
-  $ lua integrations connect                            Connect a new integration (interactive)
-  $ lua integrations connect --integration linear       Connect Linear (prompts for auth/scopes)
-  $ lua integrations connect --integration linear --auth-method oauth --scopes all
-  $ lua integrations connect --integration linear --triggers task_task.created,task_task.updated
-  $ lua integrations update --integration linear --scopes all  Update Linear scopes
-  $ lua integrations available                          List available integrations
-  $ lua integrations list                               List connected integrations
-  $ lua integrations info linear                        Show Linear integration details
-  $ lua integrations info linear --json                 Output as JSON (for scripting)
-  $ lua integrations disconnect --connection-id abc123  Disconnect an integration
-
-Webhook/Trigger Examples:
-  $ lua integrations webhooks list                      List all triggers
-  $ lua integrations webhooks events --integration linear  List available events
-  $ lua integrations webhooks create                    Create trigger (interactive)
-  $ lua integrations webhooks delete --webhook-id wh_xyz789
-  $ lua integrations webhooks pause --webhook-id wh_xyz789
-  $ lua integrations webhooks pause --connection-id abc123   Pause all triggers for a connection
-  $ lua integrations webhooks resume --webhook-id wh_xyz789
-  $ lua integrations webhooks resume --connection-id abc123  Resume all triggers for a connection
-
-MCP Server Examples:
-  $ lua integrations mcp list                           List connections with MCP server status
-  $ lua integrations mcp activate --connection abc123   Activate MCP server for a connection
-  $ lua integrations mcp deactivate --connection abc123 Deactivate MCP server for a connection
-`)
-        .action(integrationsCommand);
-    // 'lua triggers' — top-level alias for 'lua integrations webhooks' (discoverability)
-    program
-        .command('triggers [action]')
-        .description('⚡ Manage integration triggers (alias for: lua integrations webhooks)')
-        .option('--connection-id <id>', 'Connection ID to pause/resume all triggers')
-        .option('--connection <id>', 'Connection ID for creating a trigger')
-        .option('--webhook-id <id>', 'Trigger ID to delete/pause/resume')
-        .option('--object <type>', 'Object type for webhook (e.g., task_task, calendar_event)')
-        .option('--event <type>', 'Event type: created, updated, or deleted')
-        .option('--hook-url <url>', 'Custom webhook URL (default: agent trigger)')
-        .option('--interval <minutes>', 'Polling interval for virtual webhooks')
-        .option('--json', 'Output as JSON')
-        .option('--reason <text>', 'Optional reason for pausing')
-        .addHelpText('after', `
-This is a shortcut for: lua integrations webhooks <action>
-
-Actions: list, create, delete, pause, resume, events
-
-Examples:
-  $ lua triggers                               Interactive trigger management
-  $ lua triggers list                          List all triggers
-  $ lua triggers list --json                   Output as JSON
-  $ lua triggers create                        Create trigger (interactive)
-  $ lua triggers pause --webhook-id <id>       Pause a trigger
-  $ lua triggers pause --connection-id <id>    Pause all triggers for a connection
-  $ lua triggers resume --webhook-id <id>      Resume a trigger
-  $ lua triggers resume --connection-id <id>   Resume all triggers for a connection
-  $ lua triggers delete --webhook-id <id>      Delete a trigger
-`)
-        .action((action, cmdOptions) => {
-        // Delegate to integrations command with webhooks subcommand
-        // integrationsCommand(action, subaction, options) — we map:
-        //   lua triggers <action> → lua integrations webhooks <action>
-        const opts = { ...(cmdOptions || {}) };
-        return integrationsCommand('webhooks', action || '', opts);
-    });
-    program
-        .command('completion [shell]')
-        .description('🎯 Generate shell completion script')
-        .addHelpText('after', `
-Arguments:
-  shell                  Optional: 'bash', 'zsh', or 'fish' (shows instructions if not provided)
-
-Examples:
-  $ lua completion              Show installation instructions
-  $ lua completion bash         Generate bash completion script
-  $ lua completion bash >> ~/.bashrc
-  $ lua completion zsh >> ~/.zshrc
-  $ lua completion fish > ~/.config/fish/completions/lua.fish
-`)
-        .action(completionCommand);
-    program
-        .command('agents')
-        .description('👥 List all organizations and agents you have access to')
-        .option('--json', 'Output as JSON')
-        .addHelpText('after', `
-Examples:
-  $ lua agents              List all orgs and agents (formatted)
-  $ lua agents --json       Output as JSON for scripting
-`)
-        .action(agentsCommand);
-    program
-        .command('models [action]')
-        .description('🧠 List and manage LLM models for your agent')
-        .option('--model <code>', "Model code for 'set' action (e.g. 'openai/gpt-4o')")
-        .option('--json', 'Output as JSON')
-        .addHelpText('after', `
-Arguments:
-  action    Optional: 'list', 'set', or 'unset' (default: list)
-
-Options:
-  --model <code>   Set model non-interactively (use with 'set' action)
-  --json           Output list as JSON (use with 'list' action)
-
-Examples:
-  $ lua models                              List available models (formatted)
-  $ lua models list                         List available models (explicit)
-  $ lua models list --json                  List as JSON for scripting
-  $ lua models set                          Interactively select a model
-  $ lua models set --model openai/gpt-4o    Set model non-interactively
-  $ lua models unset                        Remove model — use platform default
-`)
-        .action(modelsCommand);
-    program
-        .command('status')
-        .alias('describe')
-        .description('📋 Show full state: env, auth, project, updates, sync state')
-        .option('--json', 'Output as machine-readable JSON')
-        .addHelpText('after', `
-Shows full diagnostics in one shot: CLI version + updates, install method,
-auth state and server reachability, project config, per-primitive sync state
-(local vs deployed), persona/backup status, and telemetry. Degrades gracefully
-when run outside a project or unauthenticated.
-
-Use --json for machine consumption (LLM agents).
-
-Examples:
-  $ lua status            Full status report
-  $ lua describe          Same (alias)
-  $ lua status --json     Stable JSON for automation
-`)
-        .action(statusCommand);
-    program
-        .command('update')
-        .description('🔄 Update lua-cli to the latest version')
-        .addHelpText('after', `
-Examples:
-  $ lua update               Check for updates and install the latest version
-`)
-        .action(updateCommand);
-    program
-        .command('telemetry [action]')
-        .description('📊 Manage usage telemetry')
-        .addHelpText('after', `
-Arguments:
-  action    Optional: 'on', 'off', or 'status' (default: status)
-
-Examples:
-  $ lua telemetry          Show current telemetry status
-  $ lua telemetry on       Enable telemetry
-  $ lua telemetry off      Disable telemetry
-`)
-        .action(telemetryCommand);
-    program
-        .command('governance [action]')
-        .description('🛡️  Manage governance for your agent project')
-        .addHelpText('after', `
-Arguments:
-  action    Optional: 'add' or 'remove' (default: interactive setup)
-
-Examples:
-  $ lua governance          Interactive governance setup
-  $ lua governance add      Add governance (SDK or API mode)
-  $ lua governance remove   Remove governance from agent (local + server)
-`)
-        .action(governanceCommand);
-    // Source version management — Phase 5 of the S3 backup hardening plan.
-    // Append-only history: rollback never mutates v<N>; it restores v<N>'s
-    // files locally and creates v<latest+1> with the same contents.
-    const sourceCmd = program.command('source').description('🗂️  Manage workspace source versions');
-    sourceCmd
-        .command('list')
-        .description('List source versions for the current agent')
-        .option('--all', 'Show all versions instead of the most recent 50', false)
-        .option('--limit <n>', 'Number of versions to show', '50')
-        .addHelpText('after', `
-Examples:
-  $ lua source list           List the most recent 50 versions (active marked with *)
-  $ lua source list --all     Show full history
-  $ lua source list --limit 10  Cap output at 10 versions
-`)
-        .action(async (opts) => {
-        await sourceListCommand({ all: opts.all, limit: parseInt(opts.limit, 10) });
-    });
-    sourceCmd
-        .command('rollback')
-        .description('Roll back to a specific source version')
-        .requiredOption('--version <n>', 'Version number to roll back to')
-        .option('--force', 'Skip confirmation prompt', false)
-        .addHelpText('after', `
-Examples:
-  $ lua source rollback --version 5            Restore v5 locally and append as new version
-  $ lua source rollback --version 5 --force    Skip the confirmation prompt
-`)
-        .action(async (opts) => {
-        const v = parseInt(opts.version, 10);
-        if (Number.isNaN(v) || v < 1) {
-            writeError('--version must be a positive integer');
-            process.exit(1);
-        }
-        await sourceRollbackCommand({ version: v, force: opts.force });
-    });
-}
-//# sourceMappingURL=command-definitions.js.map