@lorekit/cli 1.30.0 → 1.30.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lorekit/cli",
-  "version": "1.30.0",
+  "version": "1.30.1",
   "description": "Install the LoreKit shared-memory skill and run health checks for the LoreKit MCP server.",
   "license": "MIT",
   "repository": {

package/src/deeplink-pure.mjs

@@ -29,7 +29,15 @@ export const LORE_PARAM_DEFAULTS = {
   q: '', // string search query
   range: null, // { from, to } | null (DateRange, "YYYY-MM-DD")
   owner: 'all', // 'all' | 'personal' | { orgId }
-  tags: [], // string[] — label filter (AND across labels); [] means "no filter"
+  // Filter[] | null — the Explorer's multi-dimension filter bar (label / agent /
+  // trigger / repo / branch / pr). `null`, NOT `[]`, is the default on purpose:
+  // the app has to tell "the param is absent" from "the bar is explicitly
+  // empty", because an absent `filters` falls back to the legacy `tags`
+  // shorthand while an empty one deliberately does not. Encoding `[]` here
+  // would emit the param (it is not the default) and mean the opposite of
+  // "unfiltered".
+  filters: null,
+  tags: [], // string[] — legacy label filter (AND across labels); [] means "no filter". Still READ by the app, superseded by `filters`
   view: 'scope', // 'scope' | 'time'
   archived: false, // boolean
   lesson: null, // { scope, key } | null — opens the detail sheet
@@ -37,9 +45,9 @@ export const LORE_PARAM_DEFAULTS = {
 
 // A stable, readable param order (also makes URLs deterministic for tests).
 // Mirrors the `useUrlState` call order in `LoreExplorer.tsx` (+ the `lesson`
-// param last), so `tags` sits between `owner` and `view`. `scope` precedes
-// `lesson` so a lesson link reads `?scope=…&lesson=…`.
-const PARAM_ORDER = ['scope', 'q', 'range', 'owner', 'tags', 'view', 'archived', 'lesson'];
+// param last), so `filters` and `tags` sit between `owner` and `view`. `scope`
+// precedes `lesson` so a lesson link reads `?scope=…&lesson=…`.
+const PARAM_ORDER = ['scope', 'q', 'range', 'owner', 'filters', 'tags', 'view', 'archived', 'lesson'];
 
 // Strip trailing slashes from a base URL, falling back to the default when the
 // input is empty/absent. Pure.

package/src/telemetry.mjs

@@ -483,6 +483,11 @@ function normalizeExitCode(result) {
  * counter point. Returns the command's exit code unchanged. Telemetry failures
  * are swallowed — the command result is never affected.
  *
+ * The span carries an ERROR status only when the command CRASHED. A command
+ * that ran to completion and exited non-zero (a failing `doctor` check, a
+ * `lint` finding) reports `lorekit.cli.outcome=failure` on a span the exporter
+ * emits as STATUS_CODE_OK — never ERROR.
+ *
  * @param {string} command  bounded: install | uninstall | doctor | list | search | show | stats | scopes | diff | tree | lint | dedupe | link | migrate
  * @param {object} args     parsed CLI args (read for allow-listed flags only)
  * @param {string} version  CLI version (from package.json)
@@ -525,6 +530,10 @@ export async function traceCommand(command, args, version, run) {
 
   const startMs = Date.now();
   let exitCode = 0;
+  // `outcome` is the command's VERDICT (ok | failure | error); `status` is the
+  // SPAN status, and only a crash sets it to error. See the note above the
+  // non-zero-exit branch below.
+  let outcome = 'ok';
   let status = 'ok';
   let statusMessage;
   let extraAttrs = {};
@@ -543,11 +552,22 @@ export async function traceCommand(command, args, version, run) {
       }
     }
     if (typeof exitCode === 'number' && exitCode !== 0) {
-      status = 'error';
-      statusMessage = `exit ${exitCode}`;
+      // A non-zero exit is a REPORTED VERDICT, not a fault: `doctor` exits 1
+      // because a check it ran came back failing, and `lint` exits 1 because it
+      // found what it was asked to look for. Both commands did their job. Only
+      // a crash (the catch below) is an error, so `status` stays `'ok'` here —
+      // which `buildTracePayload` emits as STATUS_CODE_OK (1), the same status
+      // a zero-exit run gets — and the verdict is carried by
+      // `lorekit.cli.outcome=failure` +
+      // `lorekit.cli.exit_code` — which keeps the CLI's error rate a measure of
+      // the CLI being broken rather than of the user's environment being
+      // unhealthy. Query the failure verdicts on those attributes, never on the
+      // span status.
+      outcome = 'failure';
     }
     return exitCode;
   } catch (e) {
+    outcome = 'error';
     status = 'error';
     // Record only a bounded, non-PII identifier — NEVER e.message. Node fs /
     // network error messages embed absolute paths (e.g. "ENOENT: ... open
@@ -566,7 +586,7 @@ export async function traceCommand(command, args, version, run) {
       const attributes = commandAttributes({
         command,
         args,
-        outcome: status === 'error' ? 'error' : 'ok',
+        outcome,
         exitCode: typeof exitCode === 'number' ? exitCode : undefined,
         extraAttrs,
       });