@formant/formant-cli 0.3.1 → 0.4.3

package/README.md

@@ -2,16 +2,16 @@
 
 ```
    ███████╗ ██████╗██╗     ██╗
-   ██╔════╝██╔════╝██║     ██║     🤖 Formant CLI
-   █████╗  ██║     ██║     ██║     ⚡ Manage your robot fleet
-   ██╔══╝  ██║     ██║     ██║     🚀 from the command line
+   ██╔════╝██╔════╝██║     ██║     Formant CLI
+   █████╗  ██║     ██║     ██║     Manage your robot fleet
+   ██╔══╝  ██║     ██║     ██║     from the command line
    ██║     ╚██████╗███████╗██║
    ╚═╝      ╚═════╝╚══════╝╚═╝
 ```
 
 **The official command-line interface for [Formant](https://formant.io) — a cloud platform for monitoring, operating, and analyzing robot fleets at scale.**
 
-Formant helps robotics teams observe, troubleshoot, and control their robots in production. With `fcli`, you can manage your entire fleet from the terminal: query telemetry, trigger AI-powered investigations, send remote commands, manage users and permissions, and automate workflows.
+Formant helps robotics teams observe, troubleshoot, and control their robots in production. With `fcli`, you can manage your entire fleet from the terminal: query telemetry, trigger AI-powered investigations, delegate tasks to AI personas, send remote commands, manage users and permissions, and automate workflows.
 
 ## What is Formant?
 
@@ -20,6 +20,7 @@ Formant helps robotics teams observe, troubleshoot, and control their robots in
 - **Real-time monitoring** — Live telemetry streams (battery, sensors, cameras, logs) from all your robots
 - **Event tracking** — Automatic detection and alerting of critical issues (crashes, errors, anomalies)
 - **AI-powered investigations** — Intelligent root cause analysis that diagnoses problems automatically
+- **AI personas** — Configurable AI agents with tools for async task delegation
 - **Remote operations** — Send commands, trigger actions, and control robots from anywhere
 - **Fleet management** — Organize devices by location, type, or purpose; manage user permissions
 - **Analytics & reporting** — Query historical data with SQL to understand performance trends
@@ -28,75 +29,85 @@ Formant helps robotics teams observe, troubleshoot, and control their robots in
 
 This CLI provides programmatic access to all Formant capabilities:
 
-### 🤖 Device Management
+### Device Management
 - List, create, rename, and delete robots/sensors
 - Add tags for organization (environment, location, customer)
 - View real-time device status and configuration
-- List available telemetry streams
+- List available telemetry streams with per-stream data presence (datapoint counts, last seen, freshness)
+- Data-based last seen timestamps and datapoint counts on device listings
+- Filter to devices that have ingested data (`--with-data`)
 
-### 📊 Telemetry Queries
+### Telemetry Queries
 - Query historical sensor data (battery, temperature, position, custom metrics)
 - Retrieve latest values for any stream
 - Filter by time range and device
 - Export data as JSON for analysis
 
-### 📤 Telemetry Ingestion
+### Telemetry Ingestion
 - Send numeric, text, JSON, image, video, bitset, and health data to devices
 - Add tags and custom timestamps to telemetry points
 - Batch upload multiple data points in a single request
 - Programmatically populate device streams from scripts and automation
 
-### 🔍 Event Monitoring
+### Event Monitoring
 - View events filtered by severity (info, warning, critical, error)
 - Track device online/offline status
 - Investigate alert history for troubleshooting
 - Filter events by device, time range, or type
 
-### 🤖 AI Investigations
+### AI Personas
+- List available AI personas and their configurations
+- View persona details including integrations and available tools
+- Delegate async tasks to personas (fire-and-forget)
+- Check task status and results
+
+### AI Investigations
 - List available investigation workflows
-- Trigger investigations manually or on-demand
+- Trigger investigations manually with custom input
 - View investigation runs, execution logs, and results
 - Get investigation statistics and success rates
 - Trace investigations back to their triggering signals
 
-### 📡 Signal Management
+### Signal Management & Ground Truth
+- Create manual signals for testing and evaluation
 - List and query signals (investigation triggers)
+- Assign ground truth (expected outcomes) to signals for evaluation
+- View signals with their ground truth annotations
 - Count signals by type
-- Trace the workflow: Signal → Investigation → Run → Result
-- Understand what triggered each investigation
+- Trace the workflow: Signal -> Investigation -> Run -> Result
 
-### 💬 Remote Commands
+### Remote Commands
 - List available command templates for your fleet
 - Send commands to individual devices with parameters
 - View command execution history
 - Check command delivery status
 
-### 🚨 Event Triggers (Automation)
+### Event Triggers (Automation)
 - View configured trigger rules
 - Understand what conditions create events and signals
 - See trigger configuration (thresholds, exit conditions, device scope)
 
-### 👥 User & Organization Management
+### User & Organization Management
 - View organization details (plan, retention, support tier)
 - Update organization name and description
 - List all users and their roles
 - Inspect user permissions and account status
 
-### 🚀 Fleet & Group Management
+### Fleet & Group Management
 - Create logical groups of devices (by location, project, customer)
 - List all fleets and their member devices
 - Organize your fleet for easier management
 
-### 📅 Scheduled Tasks
+### Scheduled Tasks
 - View scheduled investigations and commands
 - Understand recurring workflows and automation
 
-### 📈 Analytics & SQL
+### Analytics & SQL
 - Execute custom SQL queries against your analytics database
 - List available tables and schemas
 - Analyze fleet performance, uptime, and trends
 
-### 🗂️ Key-Value Metadata Store
+### Key-Value Metadata Store
 - Store custom metadata per device
 - Retrieve configuration values
 - Update device-specific settings
@@ -134,7 +145,7 @@ Formant CLI uses **service account credentials** for authentication. You'll need
 ### Creating a Service Account
 
 1. Log in to [Formant](https://app.formant.io)
-2. Go to **Settings** → **Users**
+2. Go to **Settings** -> **Users**
 3. Click **Create Service Account**
 4. Copy the generated email and password
 
@@ -162,24 +173,29 @@ The CLI will automatically load credentials from your `.env` file.
 # View your organization
 fcli org get
 
-# List all devices
-fcli devices list --dev
+# List devices with data
+fcli device list --with-data --dev
 
 # Get device details
-fcli devices get <device-id> --dev
+fcli device get <device-id> --dev
 
 # Query battery telemetry over the last day
 fcli query --device <device-id> --stream battery_level \
   --start 2026-02-17 --end 2026-02-18 --dev
 
 # View recent critical events
-fcli events list --severity critical --limit 20 --dev
+fcli event list --severity critical --limit 20 --dev
+
+# List AI personas and delegate a task
+fcli persona list --dev
+fcli persona delegate-task <persona-id> "Analyze recent device failures" --dev
+fcli persona task-status <task-id> --dev
 
 # List all investigations
-fcli investigations list --dev
+fcli investigation list --dev
 
 # Send a command to a robot
-fcli commands send <device-id> <template-id> --param speed=5 --dev
+fcli command send <device-id> <template-id> --param speed=5 --dev
 ```
 
 ## Command Reference
@@ -194,43 +210,48 @@ fcli org update --name "Acme Robotics"         # Update organization name
 fcli org update --description "Production fleet" # Update description
 ```
 
-### Devices
+### Device
 
 Create, list, and manage robots/sensors in your fleet.
 
 ```bash
 # Listing and filtering
-fcli devices list                              # List all devices
-fcli devices list --online                     # Only online devices
-fcli devices list --tag location=warehouse     # Filter by tag
+fcli device list                               # Online devices (default)
+fcli device list --include-offline             # Include offline devices
+fcli device list --with-data                   # Only devices with ingested data
+fcli device list --with-data --days 90         # Widen the search window (default: 30d)
+fcli device list --tag location=warehouse      # Filter by tag
 
 # Device details
-fcli devices get <device-id>                   # Get full device details
-fcli devices config <device-id>                # Get device configuration
-fcli devices streams <device-id>               # List available data streams
-fcli devices last-seen <device-id>             # Get last activity timestamp
+fcli device get <device-id>                    # Get full device details
+fcli device config <device-id>                 # Get device configuration
+
+# Stream discovery with data presence
+fcli device streams <device-id>                # List streams with datapoint counts,
+                                               # last seen (ISO), and freshness
+fcli device streams <device-id> --days 30      # Adjust presence lookback (default: 7d)
 
 # Device management
-fcli devices create --name "robot-001"         # Create a new device
-fcli devices rename <device-id> --name "new-name" # Rename a device
-fcli devices delete <device-id>                # Delete (disable) a device
+fcli device create --name "robot-001"          # Create a new device
+fcli device rename <device-id> --name "new-name" # Rename a device
+fcli device delete <device-id>                 # Delete (disable) a device
 
 # Tagging
-fcli devices tag <device-id> --key env --value prod    # Add/update tag
-fcli devices untag <device-id> --key env               # Remove tag
+fcli device tag <device-id> --key env --value prod    # Add/update tag
+fcli device untag <device-id> --key env               # Remove tag
 ```
 
-### Events
+### Event
 
 View and filter important events emitted by your devices.
 
 ```bash
-fcli events list                               # List all recent events
-fcli events list --device <device-id>          # Events for one device
-fcli events list --severity critical           # Filter by severity
-fcli events list --limit 50                    # Limit results
-fcli events list --start 2026-01-01            # Filter by date range
-fcli events get <event-id>                     # Get event details
+fcli event list                                # List all recent events
+fcli event list --device <device-id>           # Events for one device
+fcli event list --severity critical            # Filter by severity
+fcli event list --limit 50                     # Limit results
+fcli event list --start 2026-01-01             # Filter by date range
+fcli event get <event-id>                      # Get event details
 ```
 
 **Severity levels:** `info`, `warning`, `error`, `critical`
@@ -265,15 +286,12 @@ fcli ingest text "Low battery warning" --device <device-id> --stream alerts --ta
 
 # JSON data
 fcli ingest json '{"x":10,"y":20}' --device <device-id> --stream position
-fcli ingest json '{"speed":15,"heading":90}' --device <device-id> --stream nav_data
 
 # Image data
 fcli ingest image https://example.com/camera.jpg --device <device-id> --stream camera_front
-fcli ingest image https://example.com/image.jpg --device <device-id> --stream camera --size 102400
 
 # Video data
 fcli ingest video https://example.com/recording.mp4 --device <device-id> --stream camera_feed --duration 30000
-fcli ingest video https://cdn.example.com/video.webm --device <device-id> --stream video --duration 15000 --mime-type video/webm
 
 # Bitset data (multiple boolean key-value pairs)
 fcli ingest bitset --device <device-id> --stream sensors \
@@ -282,7 +300,6 @@ fcli ingest bitset --device <device-id> --stream sensors \
 
 # Health status
 fcli ingest health --device <device-id> --stream health_status --status operational
-fcli ingest health --device <device-id> --stream health --status error --clock-skew 1500
 
 # Batch ingestion (multiple items from JSON file or stdin)
 fcli ingest batch --file payload.json
@@ -292,114 +309,119 @@ cat batch.json | fcli ingest batch --stdin
 **Common flags for all ingest commands:**
 - `--device <id>` - Target device ID (required)
 - `--stream <name>` - Stream name (required)
-- `--tag key=value` - Add tags as string key-value pairs (repeatable: `--tag env=prod --tag region=us-west`)
+- `--tag key=value` - Add tags as string key-value pairs (repeatable)
 - `--timestamp <ms>` - Unix timestamp in milliseconds (defaults to current time)
 
 **Health status values:** `unknown`, `operational`, `offline`, `error`
 
-**Batch format example** (`payload.json`):
-```json
-{
-  "items": [
-    {
-      "deviceId": "abc-123",
-      "name": "battery_level",
-      "type": "numeric",
-      "tags": {"env": "prod"},
-      "points": [[1642867200000, 42.5]]
-    },
-    {
-      "deviceId": "abc-123",
-      "name": "status",
-      "type": "text",
-      "tags": {"env": "prod"},
-      "points": [[1642867200000, "operational"]]
-    }
-  ]
-}
+### Persona
+
+Manage AI personas and delegate async tasks.
+
+```bash
+# Listing and details
+fcli persona list                              # List all personas
+fcli persona get <persona-id>                  # View persona details and tools
+
+# Async task delegation
+fcli persona delegate-task <persona-id> "Analyze recent device failures"
+fcli persona delegate-task <persona-id> "Generate a daily report" --name "Daily Report"
+fcli persona task-status <task-id>             # Check task status and results
 ```
 
-**Note:** The `tags` field is optional and contains string key-value pairs only. Use `"tags": {}` if no tags are needed.
+The `delegate-task` command creates a task, assigns it to the persona, and queues it for
+async execution. It returns immediately with a task ID. Use `task-status` to check progress.
 
-### Investigations
+### Investigation
 
 Trigger and monitor AI-powered analysis workflows that diagnose device issues.
 
 ```bash
 # Listing
-fcli investigations list                       # List all investigations
-fcli investigations get <investigation-id>     # Get investigation details
+fcli investigation list                        # List all investigations
+fcli investigation get <investigation-id>      # Get investigation details
 
 # Triggering
-fcli investigations trigger <inv-id> <device-id> # Start an investigation
+fcli investigation trigger <id> --input "Robot stopped responding"
 
 # Runs
-fcli investigations runs <investigation-id>    # List all runs
-fcli investigations run <inv-id> <run-id>      # Get run details & logs
-fcli investigations run <inv-id> <run-id> --trace-signal # Trace back to signal
+fcli investigation runs <investigation-id>     # List all runs
+fcli investigation run <inv-id> <run-id>       # Get run details & logs
 
 # Analytics
-fcli investigations stats --start 2026-01-01  # Get metrics
-fcli investigations analytics <investigation-id> # Get investigation analytics
+fcli investigation stats --start 2026-01-01    # Get metrics
+fcli investigation analytics <investigation-id> # Get investigation analytics
 ```
 
-### Signals
+### Signal
 
 Signals are points of interest (from events, schedules, or manual triggers) that start investigations.
+You can create signals manually and assign ground truth (expected outcomes) for evaluation.
 
 ```bash
-fcli signals list                              # List all signals
-fcli signals query --start 2026-01-01 --end 2026-02-01 # Query by time
-fcli signals count                             # Count signals by type
-fcli signals get <signal-id>                   # Get signal details
+# Listing and querying
+fcli signal list                               # List all signals
+fcli signal list --investigation <inv-id>      # List with ground truth annotations
+fcli signal query --start 2026-01-01 --end 2026-02-01 # Query by time
+fcli signal count                              # Count signals by type
+fcli signal get <signal-id>                    # Get signal details
+
+# Creating signals
+fcli signal create "Motor overheated on device X"
+fcli signal create "Sensor fault" --device <device-id>
+fcli signal create "Test scenario" --investigation <inv-id> \
+  --ground-truth "Should detect thermal issue"
+
+# Ground truth (expected outcomes for evaluation)
+fcli signal set-ground-truth <signal-id> <investigation-id> "Expected outcome text"
 ```
 
-### Commands
+### Command
 
 Send remote commands to devices and view execution history.
 
 ```bash
-fcli commands list                             # List all command templates
-fcli commands get <command-id>                 # Get template details
-fcli commands for-device <device-id>           # Commands available for device
-fcli commands send <device-id> <template-id> --param key=value # Send command
-fcli commands history <device-id>              # View command history
+fcli command list                              # List all command templates
+fcli command get <command-id>                  # Get template details
+fcli command for-device <device-id>            # Commands available for device
+fcli command send <device-id> <template-id> --param key=value # Send command
+fcli command history <device-id>               # View command history
 ```
 
-### Event Triggers
+### Event Trigger
 
 View automated trigger rules that generate events and signals based on device conditions.
 
 ```bash
-fcli event-triggers list                       # List all trigger rules
-fcli event-triggers get <trigger-id>           # Get trigger configuration
+fcli event-trigger list                        # List all trigger rules
+fcli event-trigger get <trigger-id>            # Get trigger configuration
 ```
 
-### Users
+### User
 
 Manage users in your organization.
 
 ```bash
-fcli users list                                # List all users
-fcli users get <user-id>                       # Get user details
+fcli user list                                 # List all users
+fcli user get <user-id>                        # Get user details
 ```
 
-### Fleets
+### Fleet
 
 Organize devices into logical groups (by location, type, project, customer).
 
 ```bash
-fcli fleets list                               # List all fleets
-fcli fleets get <fleet-id>                     # Get fleet details
+fcli fleet list                                # List all fleets
+fcli fleet get <fleet-id>                      # Get fleet details
 ```
 
-### Schedules
+### Schedule
 
 View recurring tasks and one-time scheduled jobs.
 
 ```bash
-fcli schedules list                            # List all schedules
-fcli schedules get <schedule-id>               # Get schedule details
+fcli schedule list                             # List all schedules
+fcli schedule get <schedule-id>                # Get schedule details
 ```
 
 ### Analytics
@@ -426,7 +448,7 @@ fcli kv set <device-id> <key> <value>          # Set value
 These flags work with any command:
 
 - `--dev` — Target the dev environment (for testing)
-- `--stage` — Target the stage environment (for staging)  
+- `--stage` — Target the stage environment (for staging)
 - `--json` — Output raw JSON instead of formatted tables
 - `-h, --help` — Show help for any command
 
@@ -439,14 +461,29 @@ These flags work with any command:
 Human-readable tables optimized for terminal viewing:
 
 ```bash
-$ fcli devices list --dev
+$ fcli device list --with-data --dev
 
-Devices (dev):
+Devices — with data (dev):
 
-NAME              ID                                      STATUS   TAGS
-────────────────────────────────────────────────────────────────────────
-robot-001         a1b2c3d4-...                            online   env=prod, location=warehouse
-robot-002         e5f6g7h8-...                            offline  env=dev
+NAME                    ID                                      ONLINE  TYPE      LAST SEEN (30D)             DATAPOINTS (30D)
+──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+carter.1                a8840212-a0a4-4d0b-8a47-098563894748    false   default   2026-02-19T19:05:37.536Z    720156
+DJI Matrice 4E          10f78fd5-c00d-42d9-94c4-b310646f59be    false   default   2026-02-18T01:17:41.167Z    917051
+```
+
+```bash
+$ fcli device streams <device-id> --dev
+
+Device Streams (dev):
+
+  Device: Walt (020e59a1-...)
+  Configured: 10  |  Discovered from data: 34
+  Presence (last 7d): 0 active, 32 recent, 0 stale, 0 dormant, 12 no data
+
+NAME                              TYPE          SOURCE  DATAPOINTS  LAST SEEN                 FRESHNESS
+spot.robot_state.battery          numeric       data    20195       2026-02-19T23:37:01.281Z  recent
+spot.localization                 text          data    16962       2026-02-19T23:37:01.271Z  recent
+spot.hand.image                   custom        config  —           —                         —
 ```
 
 ### JSON
@@ -454,17 +491,15 @@ robot-002         e5f6g7h8-...                            offline  env=dev
 Machine-readable JSON for scripting and automation:
 
 ```bash
-$ fcli devices list --dev --json
+$ fcli device list --with-data --dev --json
 {
   "items": [
     {
-      "id": "a1b2c3d4-...",
-      "name": "robot-001",
-      "online": true,
-      "tags": {
-        "env": "prod",
-        "location": "warehouse"
-      }
+      "id": "a8840212-...",
+      "name": "carter.1",
+      "online": false,
+      "last_seen": "2026-02-19T19:05:37.536Z",
+      "datapoints": 720156
     }
   ]
 }
@@ -473,7 +508,7 @@ $ fcli devices list --dev --json
 Use with `jq` for advanced processing:
 
 ```bash
-fcli devices list --json | jq '.items[] | select(.online==true) | .name'
+fcli device list --json | jq '.items[] | select(.online==true) | .name'
 ```
 
 ## Examples
@@ -481,30 +516,46 @@ fcli devices list --json | jq '.items[] | select(.online==true) | .name'
 ### Monitor fleet health
 
 ```bash
+# Find devices that have data
+fcli device list --with-data
+
+# Find devices with data, wider search window
+fcli device list --with-data --days 90
+
 # Check which devices are offline
-fcli devices list --json | jq '.items[] | select(.online==false) | .name'
+fcli device list --include-offline --json | jq '.items[] | select(.online==false) | .name'
 
 # View recent critical events across the fleet
-fcli events list --severity critical --limit 50
+fcli event list --severity critical --limit 50
 
-# Check battery levels
-for device in $(fcli devices list --json | jq -r '.items[].id'); do
-  echo "Device: $device"
-  fcli query latest-values --device $device --stream battery_level
-done
+# Discover what streams a device has and their data freshness
+fcli device streams <device-id>
+```
+
+### Delegate a task to an AI persona
+
+```bash
+# List available personas
+fcli persona list
+
+# Delegate an async task
+fcli persona delegate-task <persona-id> "Check all offline devices and summarize issues"
+
+# Check the result
+fcli persona task-status <task-id>
 ```
 
 ### Investigate a device issue
 
 ```bash
 # 1. View recent events for the device
-fcli events list --device <device-id> --limit 20
+fcli event list --device <device-id> --limit 20
 
-# 2. Check what investigations have run
-fcli investigations runs <investigation-id>
+# 2. Trigger an investigation
+fcli investigation trigger <investigation-id> --input "Device stopped responding"
 
-# 3. Get detailed logs for a specific run
-fcli investigations run <inv-id> <run-id>
+# 3. Check investigation runs
+fcli investigation runs <investigation-id>
 
 # 4. Query relevant telemetry
 fcli query --device <device-id> --stream temperature \
@@ -515,13 +566,13 @@ fcli query --device <device-id> --stream temperature \
 
 ```bash
 # Tag all production devices
-for device in $(fcli devices list --json | jq -r '.items[].id'); do
-  fcli devices tag $device --key environment --value production
+for device in $(fcli device list --json | jq -r '.items[].id'); do
+  fcli device tag $device --key environment --value production
 done
 
 # Send command to all devices in a fleet
-for device in $(fcli fleets get <fleet-id> --json | jq -r '.devices[].id'); do
-  fcli commands send $device <template-id> --param mode=standby
+for device in $(fcli fleet get <fleet-id> --json | jq -r '.devices[].id'); do
+  fcli command send $device <template-id> --param mode=standby
 done
 ```
 
@@ -529,10 +580,10 @@ done
 
 ```bash
 # Export all critical events to JSON
-fcli events list --severity critical --limit 1000 --json > critical_events.json
+fcli event list --severity critical --limit 1000 --json > critical_events.json
 
 # Export device list with tags
-fcli devices list --json | jq '.items[] | {name, id, tags}' > devices.json
+fcli device list --json | jq '.items[] | {name, id, tags}' > devices.json
 
 # Query analytics and save results
 fcli analytics query --sql "SELECT * FROM events WHERE created_at > '2026-01-01'" \
@@ -553,7 +604,7 @@ npm run build
 ### Run in development mode
 
 ```bash
-npm run dev -- devices list --dev
+npm run dev -- device list --dev
 ```
 
 ### Run directly
@@ -583,4 +634,4 @@ See [LICENSE](./LICENSE) for details.
 
 ---
 
-Made with ⚡ by [Formant](https://formant.io)
+Made with care by [Formant](https://formant.io)

package/dist/commands/{commands → command}/for-device.js

@@ -10,8 +10,8 @@ export default class CommandsForDevice extends BaseCommand {
 Returns commands that match the device's tags and filters. Only enabled commands
 that apply to this device are shown.`;
     static examples = [
-        '<%= config.bin %> commands for-device <device-id>',
-        '<%= config.bin %> commands for-device <device-id> --json',
+        '<%= config.bin %> command for-device <device-id>',
+        '<%= config.bin %> command for-device <device-id> --json',
     ];
     static summary = 'List commands available for a device';
     async run() {

package/dist/commands/command/for-device.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"for-device.js","sourceRoot":"","sources":["../../../src/commands/command/for-device.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,IAAI,EAAC,MAAM,aAAa,CAAA;AAEhC,OAAO,EAAC,WAAW,EAAC,MAAM,uBAAuB,CAAA;AACjD,OAAO,EAAc,WAAW,EAAC,MAAM,yBAAyB,CAAA;AAEhE,MAAM,CAAC,OAAO,OAAO,iBAAkB,SAAQ,WAAqC;IAClF,MAAM,CAAU,IAAI,GAAG;QACrB,QAAQ,EAAE,IAAI,CAAC,MAAM,CAAC,EAAC,WAAW,EAAE,kBAAkB,EAAE,QAAQ,EAAE,IAAI,EAAC,CAAC;KACzE,CAAA;IAED,MAAM,CAAU,WAAW,GAAG;;;qCAGK,CAAA;IAEnC,MAAM,CAAU,QAAQ,GAAG;QACzB,kDAAkD;QAClD,yDAAyD;KAC1D,CAAA;IAED,MAAM,CAAU,OAAO,GAAG,sCAAsC,CAAA;IAEzD,KAAK,CAAC,GAAG;QACd,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,GAAG,CAC3B,OAAO,EACP,WAAW,IAAI,CAAC,IAAI,CAAC,QAAQ,WAAW,EACxC,EAAC,MAAM,EAAE,KAAK,EAAC,CAChB,CAAA;QAED,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE,EAAE,CAAC;YACxB,MAAM,OAAO,GAAa;gBACxB,EAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,KAAK,EAAE,EAAE,EAAC;gBACvC,EAAC,GAAG,EAAE,SAAS,EAAE,KAAK,EAAE,SAAS,EAAE,KAAK,EAAE,EAAE,EAAC;gBAC7C,EAAC,GAAG,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,KAAK,EAAE,EAAE,EAAC;gBACnC,EAAC,GAAG,EAAE,aAAa,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE,EAAE,EAAC;aACtD,CAAA;YAED,IAAI,CAAC,GAAG,CAAC,oCAAoC,IAAI,CAAC,GAAG,MAAM,CAAC,CAAA;YAC5D,IAAI,CAAC,GAAG,CAAC,WAAW,CAAC,MAAM,CAAC,KAAK,IAAI,EAAE,EAAE,OAAO,CAAC,CAAC,CAAA;YAClD,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,CAAA;QACd,CAAC;QAED,OAAO,MAAM,CAAA;IACf,CAAC"}

package/dist/commands/{commands → command}/get.js

@@ -11,8 +11,8 @@ Shows the full template configuration including command string, parameter schema
 device targeting filters, and delivery settings. If the template has structured
 parameters (schema), they are displayed in a readable format.`;
     static examples = [
-        '<%= config.bin %> commands get <template-id>',
-        '<%= config.bin %> commands get <template-id> --json',
+        '<%= config.bin %> command get <template-id>',
+        '<%= config.bin %> command get <template-id> --json',
     ];
     static summary = 'Get command template details';
     async run() {