@lexq/cli 1.1.7 → 2.0.0

package/dist/index.js

@@ -1773,7 +1773,13 @@ function registerDeployCommands(program) {
       process.exit(1);
     }
   });
-  deploy.command("rollback").description("Rollback to the previous deployed version").requiredOption("--group-id <groupId>", "Policy group ID").requiredOption("--memo <memo>", "Rollback reason").option("--force", "Skip confirmation prompt").addHelpText(
+  deploy.command("rollback").description("Rollback to the previous deployed version").requiredOption("--group-id <groupId>", "Policy group ID").requiredOption("--memo <memo>", "Rollback reason").option(
+    "--expected-current-version-id <versionId>",
+    "currentVersionId from your last read of the group"
+  ).option(
+    "--expected-current-deployment-id <deploymentId>",
+    "currentDeploymentId from your last read of the group"
+  ).option("--force", "Skip confirmation prompt").addHelpText(
     "after",
     dedent7`
 
@@ -1781,8 +1787,20 @@ function registerDeployCommands(program) {
         Only available if the previous version is still ACTIVE and its effective end
         has not passed (P-058).
 
+        Run lexq groups get first: currentVersionName is live now and
+        previousVersionName is what a rollback restores. Pass the group's
+        currentVersionId and currentDeploymentId with the two --expected-* options.
+        The server checks only the values you pass. If anyone deployed, rolled back
+        or undeployed in between, the rollback is rejected with 409 and nothing
+        changes: P-062 if another version or no version is live, P-063 if the same
+        version is live but from a newer deployment. Read the group again before
+        retrying.
+
         Example:
-          $ lexq deploy rollback --group-id <gid> --memo "High error rate" --force
+          $ lexq groups get --id <gid>
+          $ lexq deploy rollback --group-id <gid> --memo "High error rate" \
+              --expected-current-version-id <currentVersionId> \
+              --expected-current-deployment-id <currentDeploymentId> --force
       `
   ).action(async (opts) => {
     try {
@@ -1802,7 +1820,11 @@ function registerDeployCommands(program) {
         baseUrl: globalOpts.baseUrl,
         dryRun: globalOpts.dryRun,
         verbose: globalOpts.verbose,
-        body: { memo: opts.memo }
+        body: {
+          memo: opts.memo,
+          expectedCurrentVersionId: opts.expectedCurrentVersionId,
+          expectedCurrentDeploymentId: opts.expectedCurrentDeploymentId
+        }
       });
       console.log(`\u2713 Group ${opts.groupId} rolled back.`);
     } catch (error) {
@@ -2159,7 +2181,7 @@ function registerAnalyticsCommands(program) {
     dedent8`
 
         Examples:
-          $ lexq analytics dry-run --version-id <vid> --debug \\
+          $ lexq analytics dry-run --version-id <vid> --debug \
               --json '{"facts": {"paymentAmount": 150000, "customerTier": "VIP"}}'
 
           $ lexq analytics dry-run --version-id <vid> --file test-input.json
@@ -3526,7 +3548,7 @@ ${data.totalElements} total \xB7 page ${data.pageNo + 1}/${data.totalPages}`);
 
 // src/commands/serve.ts
 import "commander";
-import dedent17 from "dedent";
+import dedent18 from "dedent";
 
 // src/mcp/server.ts
 import { readFileSync as readFileSync3 } from "fs";
@@ -3665,7 +3687,7 @@ function registerGroupTools(server, callApi) {
     {
       title: "Get Policy Group",
       annotations: { readOnlyHint: true },
-      description: "Get a single policy group by ID.",
+      description: "Get a single policy group by ID. Its currentVersionId and currentDeploymentId are what lexq_deploy_rollback expects, and previousVersionName is the version a rollback restores.",
       inputSchema: z2.object({
         groupId: z2.string().uuid().describe("Policy group ID")
       })
@@ -4246,6 +4268,7 @@ function registerFactTools(server, callApi) {
 }
 
 // src/mcp/tools/deploy.ts
+import dedent16 from "dedent";
 import { z as z6 } from "zod";
 function registerDeployTools(server, callApi) {
   server.registerTool(
@@ -4283,14 +4306,20 @@ function registerDeployTools(server, callApi) {
     {
       title: "Rollback Deployment",
       annotations: { readOnlyHint: false, destructiveHint: true },
-      description: "Rollback to the previous deployed version. Only available if there is a previous version that is still ACTIVE and whose effective end has not passed (P-058).",
+      description: dedent16`
+        Roll the group back to the version that was live before the current one. Call lexq_groups_get first: currentVersionName is live now, previousVersionName is what a rollback restores, and a rollback is rejected while canRollback is false. A rollback needs a previous version that is still ACTIVE and whose effective end has not passed (P-058).
+
+        Pass the currentVersionId and currentDeploymentId from that call as expectedCurrentVersionId and expectedCurrentDeploymentId. If anyone deployed, rolled back or undeployed in between, the rollback is rejected with 409 and nothing changes: P-062 if another version or no version is live, P-063 if the same version is live but from a newer deployment. Read the group again and check with the user before retrying.
+      `,
       inputSchema: z6.object({
         groupId: z6.string().uuid().describe("Policy group ID"),
+        expectedCurrentVersionId: z6.string().uuid().describe("currentVersionId from your last read of the group"),
+        expectedCurrentDeploymentId: z6.string().uuid().describe("currentDeploymentId from your last read of the group"),
         memo: z6.string().min(1).describe("Rollback reason (required)")
       })
     },
-    async ({ groupId, memo }) => callApi("POST", `policy-groups/${groupId}/rollback`, {
-      body: { memo }
+    async ({ groupId, expectedCurrentVersionId, expectedCurrentDeploymentId, memo }) => callApi("POST", `policy-groups/${groupId}/rollback`, {
+      body: { memo, expectedCurrentVersionId, expectedCurrentDeploymentId }
     })
   );
   server.registerTool(
@@ -4390,7 +4419,7 @@ function registerDeployTools(server, callApi) {
     {
       title: "Deployment Overview",
       annotations: { readOnlyHint: true },
-      description: "Show current deployment status of all groups \u2014 which version is live, last deployment type, and deployer.",
+      description: "Show current deployment status of all groups \u2014 which version is live, last deployment type, and deployer. Each group also carries currentDeploymentId, previousVersionName (the version a rollback restores) and canRollback, as in lexq_groups_get.",
       inputSchema: z6.object({})
     },
     async () => callApi("GET", "deployments/overview")
@@ -4426,14 +4455,14 @@ function registerDeployTools(server, callApi) {
 
 // src/mcp/tools/analytics.ts
 import { z as z7 } from "zod";
-import dedent16 from "dedent";
+import dedent17 from "dedent";
 function registerAnalyticsTools(server, callApi) {
   server.registerTool(
     "lexq_dry_run",
     {
       title: "Dry Run",
       annotations: { readOnlyHint: true },
-      description: dedent16`
+      description: dedent17`
         Execute a single dry run against a version. Tests how rules evaluate given input facts without side effects.
         
         Returns:
@@ -4463,7 +4492,7 @@ function registerAnalyticsTools(server, callApi) {
     {
       title: "Dry Run Compare",
       annotations: { readOnlyHint: true },
-      description: dedent16`
+      description: dedent17`
         Compare dry run results between two versions using the same input facts. Useful for validating changes.
         
         Returns:
@@ -4501,7 +4530,7 @@ function registerAnalyticsTools(server, callApi) {
     {
       title: "Start Simulation",
       annotations: { readOnlyHint: false, destructiveHint: false },
-      description: dedent16`
+      description: dedent17`
         Start an Impact Simulation against historical, uploaded, or inline data.
 
         dataset.type and dataset.source are BOTH required, and must be paired:
@@ -4606,7 +4635,7 @@ function registerAnalyticsTools(server, callApi) {
     {
       title: "Upload Dataset",
       annotations: { readOnlyHint: false, destructiveHint: false },
-      description: dedent16`
+      description: dedent17`
         Upload inline CSV or JSON content as a simulation dataset.
         The content is uploaded to S3 and a path is returned in the "path" field.
 
@@ -5159,7 +5188,7 @@ function startMcpServer() {
 function registerServeCommand(program) {
   program.command("serve").description("Start LexQ as a server for AI agent integrations").option("--mcp", "Start as MCP (Model Context Protocol) server over stdio").addHelpText(
     "after",
-    dedent17`
+    dedent18`
 
         Example:
           $ lexq serve --mcp
@@ -5190,11 +5219,11 @@ function registerServeCommand(program) {
 
 // src/commands/domain-templates.ts
 import "commander";
-import dedent18 from "dedent";
+import dedent19 from "dedent";
 function registerDomainTemplateCommands(program) {
   const templates = program.command("domain-templates").description("Browse and apply domain templates").addHelpText(
     "after",
-    dedent18`
+    dedent19`
 
         A domain template is an industry-specific starter pack of fact
         definitions and sample rules. Applying one provisions a ready-to-use
@@ -5242,7 +5271,7 @@ function registerDomainTemplateCommands(program) {
   });
   templates.command("preview").description("Preview what a domain template provisions").requiredOption("--template <key>", "Domain template key (e.g. ECOMMERCE)").addHelpText(
     "after",
-    dedent18`
+    dedent19`
 
         Read-only dry run — shows the fact definitions and sample rules the
         template will create. Nothing is provisioned.
@@ -5271,7 +5300,7 @@ function registerDomainTemplateCommands(program) {
   });
   templates.command("apply").description("Apply a domain template to the current tenant").requiredOption("--template <key>", "Domain template key (e.g. ECOMMERCE)").option("--name <n>", "Custom name for the policy group that gets created").option("--force", "Skip confirmation prompt").addHelpText(
     "after",
-    dedent18`
+    dedent19`
 
         Creates the template's fact definitions and a new DRAFT policy group
         populated with its sample rules. A fact that already exists with the

package/dist/mcp/register.js

@@ -84,7 +84,7 @@ function registerGroupTools(server, callApi) {
     {
       title: "Get Policy Group",
       annotations: { readOnlyHint: true },
-      description: "Get a single policy group by ID.",
+      description: "Get a single policy group by ID. Its currentVersionId and currentDeploymentId are what lexq_deploy_rollback expects, and previousVersionName is the version a rollback restores.",
       inputSchema: z2.object({
         groupId: z2.string().uuid().describe("Policy group ID")
       })
@@ -778,6 +778,7 @@ function registerFactTools(server, callApi) {
 }
 
 // src/mcp/tools/deploy.ts
+import dedent2 from "dedent";
 import { z as z6 } from "zod";
 function registerDeployTools(server, callApi) {
   server.registerTool(
@@ -815,14 +816,20 @@ function registerDeployTools(server, callApi) {
     {
       title: "Rollback Deployment",
       annotations: { readOnlyHint: false, destructiveHint: true },
-      description: "Rollback to the previous deployed version. Only available if there is a previous version that is still ACTIVE and whose effective end has not passed (P-058).",
+      description: dedent2`
+        Roll the group back to the version that was live before the current one. Call lexq_groups_get first: currentVersionName is live now, previousVersionName is what a rollback restores, and a rollback is rejected while canRollback is false. A rollback needs a previous version that is still ACTIVE and whose effective end has not passed (P-058).
+
+        Pass the currentVersionId and currentDeploymentId from that call as expectedCurrentVersionId and expectedCurrentDeploymentId. If anyone deployed, rolled back or undeployed in between, the rollback is rejected with 409 and nothing changes: P-062 if another version or no version is live, P-063 if the same version is live but from a newer deployment. Read the group again and check with the user before retrying.
+      `,
       inputSchema: z6.object({
         groupId: z6.string().uuid().describe("Policy group ID"),
+        expectedCurrentVersionId: z6.string().uuid().describe("currentVersionId from your last read of the group"),
+        expectedCurrentDeploymentId: z6.string().uuid().describe("currentDeploymentId from your last read of the group"),
         memo: z6.string().min(1).describe("Rollback reason (required)")
       })
     },
-    async ({ groupId, memo }) => callApi("POST", `policy-groups/${groupId}/rollback`, {
-      body: { memo }
+    async ({ groupId, expectedCurrentVersionId, expectedCurrentDeploymentId, memo }) => callApi("POST", `policy-groups/${groupId}/rollback`, {
+      body: { memo, expectedCurrentVersionId, expectedCurrentDeploymentId }
     })
   );
   server.registerTool(
@@ -922,7 +929,7 @@ function registerDeployTools(server, callApi) {
     {
       title: "Deployment Overview",
       annotations: { readOnlyHint: true },
-      description: "Show current deployment status of all groups \u2014 which version is live, last deployment type, and deployer.",
+      description: "Show current deployment status of all groups \u2014 which version is live, last deployment type, and deployer. Each group also carries currentDeploymentId, previousVersionName (the version a rollback restores) and canRollback, as in lexq_groups_get.",
       inputSchema: z6.object({})
     },
     async () => callApi("GET", "deployments/overview")
@@ -958,14 +965,14 @@ function registerDeployTools(server, callApi) {
 
 // src/mcp/tools/analytics.ts
 import { z as z7 } from "zod";
-import dedent2 from "dedent";
+import dedent3 from "dedent";
 function registerAnalyticsTools(server, callApi) {
   server.registerTool(
     "lexq_dry_run",
     {
       title: "Dry Run",
       annotations: { readOnlyHint: true },
-      description: dedent2`
+      description: dedent3`
         Execute a single dry run against a version. Tests how rules evaluate given input facts without side effects.
         
         Returns:
@@ -995,7 +1002,7 @@ function registerAnalyticsTools(server, callApi) {
     {
       title: "Dry Run Compare",
       annotations: { readOnlyHint: true },
-      description: dedent2`
+      description: dedent3`
         Compare dry run results between two versions using the same input facts. Useful for validating changes.
         
         Returns:
@@ -1033,7 +1040,7 @@ function registerAnalyticsTools(server, callApi) {
     {
       title: "Start Simulation",
       annotations: { readOnlyHint: false, destructiveHint: false },
-      description: dedent2`
+      description: dedent3`
         Start an Impact Simulation against historical, uploaded, or inline data.
 
         dataset.type and dataset.source are BOTH required, and must be paired:
@@ -1138,7 +1145,7 @@ function registerAnalyticsTools(server, callApi) {
     {
       title: "Upload Dataset",
       annotations: { readOnlyHint: false, destructiveHint: false },
-      description: dedent2`
+      description: dedent3`
         Upload inline CSV or JSON content as a simulation dataset.
         The content is uploaded to S3 and a path is returned in the "path" field.
 

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@lexq/cli",
-  "version": "1.1.7",
+  "version": "2.0.0",
   "mcpName": "io.lexq/lexq",
-  "description": "LexQ CLI — manage policies, simulate rules, and deploy from the terminal. Built for humans and AI agents.",
+  "description": "The Decision Operations Platform for engineering teams",
   "type": "module",
   "bin": {
     "lexq": "./dist/index.js"
@@ -44,6 +44,7 @@
     "test:command-options": "node tests/command-options.mjs",
     "test:value-domain": "pnpm build && node tests/value-domain.mjs",
     "test:fact-update": "pnpm build && node tests/fact-update.mjs",
+    "test:rollback": "pnpm build && node tests/rollback.mjs",
     "prepublishOnly": "pnpm build",
     "knip": "knip",
     "format": "prettier --write \"src/**/*.ts\"",
@@ -57,7 +58,11 @@
     "ai-agent",
     "agent-skills",
     "simulation",
-    "business-rules"
+    "business-rules",
+    "developer-tools",
+    "decision-management",
+    "mcp",
+    "mcp-server"
   ],
   "author": "LexQ, LLC",
   "license": "Apache-2.0",

package/skills/lexq-recipes/SKILL.md

@@ -352,17 +352,24 @@ lexq rules create --group-id <gid> --version-id <vid> --json '{
 **Goal:** Something went wrong in production — revert to the previous version.
 
 ```bash
-# 1. Check current state
-lexq deploy overview
+# 1. Read the group: currentVersionName is live now, previousVersionName is what a
+#    rollback restores, and a rollback is rejected while canRollback is false
+lexq groups get --id <gid>
 
-# 2. Rollback
-lexq deploy rollback --group-id <gid> --memo "Reverting due to increased error rate"
+# 2. Roll back with the IDs from step 1
+lexq deploy rollback --group-id <gid> --memo "Reverting due to increased error rate" \
+  --expected-current-version-id <currentVersionId> \
+  --expected-current-deployment-id <currentDeploymentId>
 
 # 3. Verify
 lexq deploy overview
 lexq history stats
 ```
 
+If anyone deployed, rolled back or undeployed after step 1, step 2 is rejected with `409` and
+nothing changes: `P-062` if another version or no version is live, `P-063` if the same version is
+live but from a newer deployment. Start again from step 1.
+
 ---
 
 ## Recipe 7: Monitoring + Failure Triage