@lexq/cli 2.1.0 → 3.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lexq/cli",
-  "version": "2.1.0",
+  "version": "3.0.0",
   "mcpName": "io.lexq/lexq",
   "description": "The Decision Operations Platform for engineering teams",
   "type": "module",
@@ -46,6 +46,7 @@
     "test:fact-update": "pnpm build && node tests/fact-update.mjs",
     "test:rollback": "pnpm build && node tests/rollback.mjs",
     "test:dataset-upload": "pnpm build && node tests/dataset-upload.mjs",
+    "test:export-limit": "pnpm build && node tests/export-limit.mjs",
     "prepublishOnly": "pnpm build",
     "knip": "knip",
     "format": "prettier --write \"src/**/*.ts\"",

package/skills/lexq-execution/SKILL.md

@@ -118,26 +118,15 @@ see it.
 lexq logs get --id <logId>
 ```
 
-Includes the original payload and error message. Use it to diagnose before marking the log.
+Includes the original payload and error message. Use it to diagnose the failure.
 
-### Mark a Log
+### Resolve or Ignore a Log
 
-There is no retry action — the engine does not re-execute a failed task on request. Fix the cause
-at the source (webhook endpoint, version state), then mark the log.
-
-```bash
-lexq logs action --id <logId> --action RESOLVE   # cause was fixed
-lexq logs action --id <logId> --action IGNORE    # does not need fixing
-```
-
-Both remove the log from `PENDING`; they differ only in recorded intent.
-
-### Bulk Operations
-
-```bash
-lexq logs bulk-action --ids "id1,id2,id3" --action RESOLVE
-lexq logs bulk-action --ids "id4,id5" --action IGNORE
-```
+The CLI can read failure logs but cannot resolve or ignore them. An organization admin does that in
+the console: Management → Failure Logs (https://console.lexq.io/management/failure-logs). Resolving
+and ignoring both remove the log from `PENDING`; they differ only in recorded intent. There is no
+retry action either: the engine does not re-execute a failed task on request. Fix the cause at the
+source (webhook endpoint, version state), then ask an admin to resolve the log.
 
 ## 3. Deployment Monitoring
 
@@ -278,9 +267,8 @@ lexq provenance get --trace-id <traceId>
 # 4. Check for system failures (covers 7 days back by default; add --start-date for older ones)
 lexq logs list --status PENDING --page 0 --size 10
 
-# 5. Inspect and mark
+# 5. Inspect a failure. Once the cause is fixed, an admin resolves it in the console
 lexq logs get --id <logId>
-lexq logs action --id <logId> --action RESOLVE
 
 # 6. Verify deployment integrity
 lexq deploy overview

package/skills/lexq-recipes/SKILL.md

@@ -374,11 +374,13 @@ live but from a newer deployment. Start again from step 1.
 
 ## Recipe 7: Monitoring + Failure Triage
 
-**Goal:** Check for pending failures and clear the queue.
+**Goal:** Check for pending failures and find their cause.
 
 Failure logs are a dead-letter record for background tasks — platform event webhooks and scheduled
 deployments. There is no retry action: the engine does not re-execute a failed task on request.
-Fix the cause at the source (webhook endpoint, version state), then mark the log.
+Fix the cause at the source (webhook endpoint, version state). The CLI can read failure logs but
+cannot resolve or ignore them: an organization admin does that in the console, under
+Management → Failure Logs (https://console.lexq.io/management/failure-logs).
 
 ```bash
 # 1. List pending failures
@@ -387,22 +389,16 @@ lexq logs list --status PENDING --page 0 --size 50
 # 2. Inspect one to see the original payload and error
 lexq logs get --id <logId>
 
-# 3. Mark as resolved after fixing the cause externally
-lexq logs bulk-action --ids "id1,id2,id3" --action RESOLVE
-
-# 4. Mark as intentionally skipped (won't appear in PENDING again)
-lexq logs bulk-action --ids "id4,id5" --action IGNORE
-
-# 5. Verify clean state
+# 3. After an admin resolves the logs in the console, check that none are still pending
 lexq logs list --status PENDING --page 0 --size 10
 ```
 
 Without `--start-date`, `logs list` covers 7 days back through today, in the organization time
-zone. An empty list in step 5 means there is no PENDING failure in that window, not that there is
-none at all. Add an earlier `--start-date` to steps 1 and 5 to see older ones.
+zone. An empty list in step 3 means there is no PENDING failure in that window, not that there is
+none at all. Add an earlier `--start-date` to steps 1 and 3 to see older ones.
 
-`RESOLVE` and `IGNORE` differ only in intent — both remove the log from PENDING. Use `RESOLVE`
-when the underlying problem was fixed, `IGNORE` when it does not need fixing.
+Resolving and ignoring differ only in intent — both remove the log from PENDING. An admin resolves
+a log when the underlying problem was fixed and ignores it when it does not need fixing.
 
 ---
 

package/skills/lexq-shared/SKILL.md

@@ -99,7 +99,7 @@ Every command accepts these flags:
 | `history`               | `list`, `get`, `stats`                                                                                                     | Execution history               |
 | `replay`                | `decision`, `start`, `list`, `get`, `cancel`                                                                               | Decision replay                 |
 | `provenance`            | `get`, `reveal-audits`                                                                                                     | Decision provenance + PII audit |
-| `logs`                  | `list`, `get`, `action`, `bulk-action`                                                                                     | Failure log management          |
+| `logs`                  | `list`, `get`                                                                                                              | Failure logs (read-only)        |
 | `webhook-subscriptions` | `list`, `get`, `save`, `delete`, `test`                                                                                    | Platform event webhooks         |
 | `serve`                 | `--mcp`                                                                                                                    | MCP server over stdio           |