@lexq/cli 0.1.20 → 0.1.22

package/dist/index.js

@@ -876,7 +876,7 @@ ${data.totalElements} total \xB7 page ${data.pageNo + 1}/${data.totalPages}`);
                 "valueType": "STRING"
               },
               "actions": [
-                { "type": "DISCOUNT", "parameters": { "method": "PERCENTAGE", "rate": 20, "refVar": "payment_amount" } }
+                { "type": "MUTATE_FACT", "parameters": { "refVar": "payment_amount", "operator": "SUB", "method": "PERCENTAGE", "rate": 20 } }
               ]
             }'
 
@@ -885,7 +885,7 @@ ${data.totalElements} total \xB7 page ${data.pageNo + 1}/${data.totalPages}`);
           LESS_THAN, LESS_THAN_OR_EQUAL, CONTAINS, IN, NOT_IN
 
         Action Types:
-          DISCOUNT, POINT, COUPON_ISSUE, BLOCK, NOTIFICATION, WEBHOOK, SET_FACT, ADD_TAG
+          MUTATE_FACT, INCREMENT_FACT, EMIT_EVENT, BLOCK, EMIT_NOTIFICATION, EMIT_WEBHOOK, SET_FACT, ADD_TAG
 
         Value Types: STRING, NUMBER, BOOLEAN, LIST_STRING, LIST_NUMBER
 
@@ -925,7 +925,7 @@ ${data.totalElements} total \xB7 page ${data.pageNo + 1}/${data.totalPages}`);
           $ lexq rules update --group-id <gid> --version-id <vid> --id <rid> --json '{
               "name": "VIP 25% Discount",
               "actions": [
-                { "type": "DISCOUNT", "parameters": { "method": "PERCENTAGE", "rate": 25, "refVar": "payment_amount" } }
+                { "type": "MUTATE_FACT", "parameters": { "refVar": "payment_amount", "operator": "SUB", "method": "PERCENTAGE", "rate": 25 } }
               ]
             }'
       `
@@ -2139,7 +2139,7 @@ ${data.totalElements} total \xB7 page ${data.pageNo + 1}/${data.totalPages}`);
     dedent9`
 
         Returns the full execution detail including request facts, result traces,
-        and decision traces (SELECTED, BLOCKED_MUTEX, LOST_PRIORITY, etc.).
+        and decision traces (SELECTED, NO_MATCH, BLOCKED, etc.).
       `
   ).action(async (opts) => {
     try {
@@ -3124,18 +3124,20 @@ function registerRuleTools(server, callApi) {
         Actions: [{ type, parameters }]
 
         Action parameter schemas:
-        - DISCOUNT: { refVar: string, method: "PERCENTAGE"|"AMOUNT", rate?: number (when PERCENTAGE), value?: number (when AMOUNT) }
-        - POINT: { refVar: string, targetVar: string, method: "PERCENTAGE"|"AMOUNT", rate?: number (when PERCENTAGE), value?: number (when AMOUNT), integrationId: uuid }
-        - COUPON_ISSUE: { couponId: string, integrationId: uuid }
+        - 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.
+        - 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 }
-        - NOTIFICATION: { channel: "SMS"|"EMAIL"|"PUSH", targetVar: string, templateId: string, integrationId: uuid }
-        - WEBHOOK: { url: string, method: "POST", payloadTemplate?: object } payloadTemplate is optional. Without it, all facts are sent as-is. With it, the object is sent as the HTTP body with {{variables}} replaced at execution time. Variables: {{fact.xxx}}, {{output.xxx}}, {{timestamp}}, {{ruleName}}, {{groupName}}, {{versionNo}}, {{xxx}} (shorthand).
+        - 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.
+        - EMIT_WEBHOOK: { url: string, method: "POST", payloadTemplate?: object } payloadTemplate is optional. Without it, all facts are sent as-is. With it, the object is sent as the HTTP body with {{variables}} replaced at execution time. Variables: {{fact.xxx}}, {{output.xxx}}, {{timestamp}}, {{ruleName}}, {{groupName}}, {{versionNo}}, {{xxx}} (shorthand).
           Platform examples:
             Slack: { "text": "Rule {{ruleName}} fired — {{fact.customer_tier}}" }
             Discord: { "content": "Rule {{ruleName}} fired — {{fact.customer_tier}}" }
             Generic: { "event": "rule_matched", "rule": "{{ruleName}}", "amount": "{{output.payment_amount}}" }
         - SET_FACT: { key: string, value: string|number|boolean }
         - ADD_TAG: { tag: string, targetVar: string }
+        
+        RoundingOption (optional, MUTATE_FACT / INCREMENT_FACT only): { scale: integer (0..16), mode?: "HALF_UP"|"HALF_DOWN"|"HALF_EVEN"|"FLOOR"|"CEILING"|"DOWN"|"UP" } mode defaults to HALF_UP. When omitted, calculator output is preserved at full precision (lossless).
       `,
       inputSchema: {
         groupId: z3.string().uuid().describe("Policy group ID"),
@@ -3448,7 +3450,7 @@ function registerAnalyticsTools(server, callApi) {
           mutatedFacts      — input facts changed by rule actions (e.g. DISCOUNT mutates payment_amount)
           generatedVariables — new variables created by rules (e.g. last_discount_amount)
           executionTraces   — per-rule match status
-          decisionTraces    — per-rule decision (SELECTED / BLOCKED_MUTEX / etc.)
+          decisionTraces    — per-rule decision (SELECTED / NO_MATCH / BLOCKED / etc.)
         
         Example input: { "facts": { "payment_amount": 100000, "customer_tier": "VIP" } }
         Always dry-run before publishing to validate rule behavior.`,

package/dist/mcp/register.js

@@ -293,18 +293,20 @@ function registerRuleTools(server, callApi) {
         Actions: [{ type, parameters }]
 
         Action parameter schemas:
-        - DISCOUNT: { refVar: string, method: "PERCENTAGE"|"AMOUNT", rate?: number (when PERCENTAGE), value?: number (when AMOUNT) }
-        - POINT: { refVar: string, targetVar: string, method: "PERCENTAGE"|"AMOUNT", rate?: number (when PERCENTAGE), value?: number (when AMOUNT), integrationId: uuid }
-        - COUPON_ISSUE: { couponId: string, integrationId: uuid }
+        - 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.
+        - 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 }
-        - NOTIFICATION: { channel: "SMS"|"EMAIL"|"PUSH", targetVar: string, templateId: string, integrationId: uuid }
-        - WEBHOOK: { url: string, method: "POST", payloadTemplate?: object } payloadTemplate is optional. Without it, all facts are sent as-is. With it, the object is sent as the HTTP body with {{variables}} replaced at execution time. Variables: {{fact.xxx}}, {{output.xxx}}, {{timestamp}}, {{ruleName}}, {{groupName}}, {{versionNo}}, {{xxx}} (shorthand).
+        - 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.
+        - EMIT_WEBHOOK: { url: string, method: "POST", payloadTemplate?: object } payloadTemplate is optional. Without it, all facts are sent as-is. With it, the object is sent as the HTTP body with {{variables}} replaced at execution time. Variables: {{fact.xxx}}, {{output.xxx}}, {{timestamp}}, {{ruleName}}, {{groupName}}, {{versionNo}}, {{xxx}} (shorthand).
           Platform examples:
             Slack: { "text": "Rule {{ruleName}} fired — {{fact.customer_tier}}" }
             Discord: { "content": "Rule {{ruleName}} fired — {{fact.customer_tier}}" }
             Generic: { "event": "rule_matched", "rule": "{{ruleName}}", "amount": "{{output.payment_amount}}" }
         - SET_FACT: { key: string, value: string|number|boolean }
         - ADD_TAG: { tag: string, targetVar: string }
+        
+        RoundingOption (optional, MUTATE_FACT / INCREMENT_FACT only): { scale: integer (0..16), mode?: "HALF_UP"|"HALF_DOWN"|"HALF_EVEN"|"FLOOR"|"CEILING"|"DOWN"|"UP" } mode defaults to HALF_UP. When omitted, calculator output is preserved at full precision (lossless).
       `,
       inputSchema: {
         groupId: z3.string().uuid().describe("Policy group ID"),
@@ -617,7 +619,7 @@ function registerAnalyticsTools(server, callApi) {
           mutatedFacts      — input facts changed by rule actions (e.g. DISCOUNT mutates payment_amount)
           generatedVariables — new variables created by rules (e.g. last_discount_amount)
           executionTraces   — per-rule match status
-          decisionTraces    — per-rule decision (SELECTED / BLOCKED_MUTEX / etc.)
+          decisionTraces    — per-rule decision (SELECTED / NO_MATCH / BLOCKED / etc.)
         
         Example input: { "facts": { "payment_amount": 100000, "customer_tier": "VIP" } }
         Always dry-run before publishing to validate rule behavior.`,

package/package.json

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