@lexq/cli 0.1.28 → 0.1.30

package/dist/index.js

@@ -187,7 +187,7 @@ function registerAuthCommands(program) {
 
         Example:
           $ lexq auth login
-          Enter your API Key: sk_live_****
+          Enter your API Key: lexq_us_****
 
           ✓ API key saved to ~/.lexq/config.json
       `
@@ -218,7 +218,7 @@ function registerAuthCommands(program) {
 
         Example:
           $ lexq auth whoami
-          { "tenantId": "abc-123", "userId": "...", "role": "ADMIN", "apiKey": "sk_live_****abcd" }
+          { "tenantId": "abc-123", "userId": "...", "role": "ADMIN", "apiKey": "lexq_us_****abcd" }
       `
   ).action(async () => {
     try {
@@ -1067,7 +1067,7 @@ function registerFactCommands(program) {
           delete           Remove a fact definition
           action-metadata  Show action runtime fact metadata
 
-        System facts (payment_amount, user_id, etc.) are auto-created and immutable.
+        System facts (user_id, user_tags) are auto-created.
       `
   );
   facts.command("list").description("List fact definitions").option("--keyword <keyword>", "Filter by keyword").option("--page <number>", "Page number", "0").option("--size <number>", "Page size", "20").action(async (opts) => {
@@ -1715,18 +1715,20 @@ function registerAnalyticsCommands(program) {
           $ lexq analytics simulation start --json '{
               "policyVersionId": "<vid>",
               "dataset": {
-                "type": "EXECUTION_LOG",
-                "source": "RECENT",
-                "maxRecords": 1000
+                "type": "HISTORICAL",
+                "source": "EXECUTION_LOGS",
+                "from": "2026-01-01",
+                "to": "2026-01-31"
               },
               "options": {
                 "baselinePolicyVersionId": "<baseline-vid>",
-                "includeRuleStats": true
+                "includeRuleStats": true,
+                "maxRecords": 1000
               }
             }'
-
-        Dataset types: EXECUTION_LOG, MANUAL
-        Dataset sources: RECENT, DATE_RANGE, MANUAL
+            
+        Dataset types: HISTORICAL, UPLOADED, MANUAL
+        Dataset sources: EXECUTION_LOGS, S3_BUCKET, REQUEST_BODY
       `
   ).action(async (opts) => {
     try {
@@ -3125,7 +3127,7 @@ function registerRuleTools(server, callApi) {
 
         Action parameter schemas:
         - MUTATE_FACT: { refVar: string, operator: "ASSIGN"|"ADD"|"SUB"|"MUL"|"DIV", method: "PERCENTAGE"|"AMOUNT", rate?: number (when PERCENTAGE), value?: number (when AMOUNT), rounding?: RoundingOption } Constraints: DIV + PERCENTAGE is invalid (use MUL with rate/100 inverse). DIV + AMOUNT requires value !== 0.
-        - INCREMENT_FACT: { targetVar: string, method: "PERCENTAGE"|"AMOUNT", refVar?: string (required when PERCENTAGE), rate?: number (when PERCENTAGE), value?: number (when AMOUNT), rounding?: RoundingOption } Note: external system call (e.g. point system sync) is NOT a primitive responsibility. Compose [INCREMENT_FACT, EMIT_EVENT] chain instead.
+        - INCREMENT_FACT: { targetVar: string, method: "PERCENTAGE"|"AMOUNT", refVar?: string (required when PERCENTAGE), rate?: number (when PERCENTAGE), value?: number (when AMOUNT), rounding?: RoundingOption } targetVar (accumulation target) must exist at execution; refVar (PERCENTAGE source) must exist when method is PERCENTAGE. Each is supplied as an input fact or written by a prior action in this rule — a missing required fact throws (no 0 default). Note: external system call (e.g. point system sync) is NOT a primitive responsibility. Compose [INCREMENT_FACT, EMIT_EVENT] chain instead.
         - EMIT_EVENT: { integrationId: uuid, eventPayload: object (Map<string,unknown>, ≥1 entry) } eventPayload is passed through to the integration provider as-is. Domain-specific keys (couponId, ticketId, etc.) are routed by the provider, not validated by the engine.
         - BLOCK: { reason: string }
         - EMIT_NOTIFICATION: { integrationId: uuid, targetVar: string, notificationPayload: object (Map<string,unknown>, ≥1 entry) } targetVar identifies the recipient fact (e.g. phone_number / email / device_token). notificationPayload (channel, templateId, body, variables, etc.) is passed through to the provider.
@@ -3296,7 +3298,7 @@ function registerFactTools(server, callApi) {
     "lexq_facts_action_metadata",
     {
       title: "Get Action Runtime Fact Metadata",
-      description: "Retrieve runtime Facts metadata for each Action type. Shows which Facts are required as input, produced as output, or consumed at runtime by each Action (MUTATE_FACT, INCREMENT_FACT, EMIT_EVENT, BLOCK, EMIT_NOTIFICATION, EMIT_WEBHOOK, SET_FACT, ADD_TAG). Use this BEFORE designing rules to understand which Action mutates which fact (e.g., MUTATE_FACT mutates the refVar fact and auto-generates {fact_name}__delta in generatedVariables). Data is static and changes only on engine deployment \u2014 safe to cache in-session.",
+      description: "Retrieve runtime fact requirements per Action type. For each Action, shows which input facts must be present in the execution payload (e.g. MUTATE_FACT requires its refVar fact; INCREMENT_FACT always requires targetVar, plus refVar when method is PERCENTAGE). A required fact absent at runtime throws \u2014 the engine never defaults to 0. Facts are supplied as input or written by a prior action in the same rule; Actions never create a fact from nothing. Static data, safe to cache in-session.",
       inputSchema: {}
     },
     async () => callApi("GET", "schema/action-metadata")

package/dist/mcp/register.js

@@ -294,7 +294,7 @@ function registerRuleTools(server, callApi) {
 
         Action parameter schemas:
         - MUTATE_FACT: { refVar: string, operator: "ASSIGN"|"ADD"|"SUB"|"MUL"|"DIV", method: "PERCENTAGE"|"AMOUNT", rate?: number (when PERCENTAGE), value?: number (when AMOUNT), rounding?: RoundingOption } Constraints: DIV + PERCENTAGE is invalid (use MUL with rate/100 inverse). DIV + AMOUNT requires value !== 0.
-        - INCREMENT_FACT: { targetVar: string, method: "PERCENTAGE"|"AMOUNT", refVar?: string (required when PERCENTAGE), rate?: number (when PERCENTAGE), value?: number (when AMOUNT), rounding?: RoundingOption } Note: external system call (e.g. point system sync) is NOT a primitive responsibility. Compose [INCREMENT_FACT, EMIT_EVENT] chain instead.
+        - INCREMENT_FACT: { targetVar: string, method: "PERCENTAGE"|"AMOUNT", refVar?: string (required when PERCENTAGE), rate?: number (when PERCENTAGE), value?: number (when AMOUNT), rounding?: RoundingOption } targetVar (accumulation target) must exist at execution; refVar (PERCENTAGE source) must exist when method is PERCENTAGE. Each is supplied as an input fact or written by a prior action in this rule — a missing required fact throws (no 0 default). Note: external system call (e.g. point system sync) is NOT a primitive responsibility. Compose [INCREMENT_FACT, EMIT_EVENT] chain instead.
         - EMIT_EVENT: { integrationId: uuid, eventPayload: object (Map<string,unknown>, ≥1 entry) } eventPayload is passed through to the integration provider as-is. Domain-specific keys (couponId, ticketId, etc.) are routed by the provider, not validated by the engine.
         - BLOCK: { reason: string }
         - EMIT_NOTIFICATION: { integrationId: uuid, targetVar: string, notificationPayload: object (Map<string,unknown>, ≥1 entry) } targetVar identifies the recipient fact (e.g. phone_number / email / device_token). notificationPayload (channel, templateId, body, variables, etc.) is passed through to the provider.
@@ -465,7 +465,7 @@ function registerFactTools(server, callApi) {
     "lexq_facts_action_metadata",
     {
       title: "Get Action Runtime Fact Metadata",
-      description: "Retrieve runtime Facts metadata for each Action type. Shows which Facts are required as input, produced as output, or consumed at runtime by each Action (MUTATE_FACT, INCREMENT_FACT, EMIT_EVENT, BLOCK, EMIT_NOTIFICATION, EMIT_WEBHOOK, SET_FACT, ADD_TAG). Use this BEFORE designing rules to understand which Action mutates which fact (e.g., MUTATE_FACT mutates the refVar fact and auto-generates {fact_name}__delta in generatedVariables). Data is static and changes only on engine deployment \u2014 safe to cache in-session.",
+      description: "Retrieve runtime fact requirements per Action type. For each Action, shows which input facts must be present in the execution payload (e.g. MUTATE_FACT requires its refVar fact; INCREMENT_FACT always requires targetVar, plus refVar when method is PERCENTAGE). A required fact absent at runtime throws \u2014 the engine never defaults to 0. Facts are supplied as input or written by a prior action in the same rule; Actions never create a fact from nothing. Static data, safe to cache in-session.",
       inputSchema: {}
     },
     async () => callApi("GET", "schema/action-metadata")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lexq/cli",
-  "version": "0.1.28",
+  "version": "0.1.30",
   "description": "LexQ CLI — manage policies, simulate rules, and deploy from the terminal. Built for humans and AI agents.",
   "type": "module",
   "bin": {

package/skills/lexq-shared/SKILL.md

@@ -13,7 +13,7 @@ simulation** and **A/B testing** for rule versions.
 ```bash
 # Store your API key (persisted at ~/.lexq/config.json)
 lexq auth login
-# Enter your API Key: sk_live_xxxxxxxxxxxxx
+# Enter your API Key: lexq_us_xxxxxxxxxxxxx
 
 # Verify authentication
 lexq auth whoami
@@ -22,7 +22,7 @@ lexq auth whoami
 The API key is passed as `X-API-KEY` header on every request. You can also override per-command:
 
 ```bash
-lexq groups list --api-key sk_live_override_key
+lexq groups list --api-key lexq_us_override_key
 ```
 
 **Base URL:** `https://api.lexq.io/api/v1/partners` (default). Override with `--base-url`.