@moda-ai/cli 1.55.22 → 1.55.24

package/skills/moda-cli/references/signals-and-false-positives.md

@@ -7,23 +7,23 @@ Loaded on demand from the moda-cli skill.
 **Mark anything as a false positive with one command.** `--reason` (why the
 detection is wrong) is optional but recommended; marks are logged for Moda's review.
 A marked item disappears from every list and count (`moda problems`,
-`hallucinations`, `laziness`, `tool-failures`, problem evidence, the dashboard);
-`--undo` brings it back.
+`detections list`, `detections tools`, problem evidence, the dashboard);
+`--verdict=clear` brings it back.
 
 ```bash
-moda false-positive problem <problem_id> --reason="two unrelated tools"   # dismiss: hidden at once
-moda false-positive problem-detection <problem_id> --conversation-id=<id> \
+moda review problem <problem_id> --reason="two unrelated tools"   # dismiss: hidden at once
+moda review problem-detection <problem_id> --conversation-id=<id> \
   --attribution-id=<uuid> --reason="refund was approved"                  # one piece of evidence
-moda false-positive quote <conversation_id> --family=frustration --turn=3 \
+moda review quote <conversation_id> --family=frustration --turn=3 \
   --quote="this is useless lol" --reason="user was joking"               # one user quote
-moda false-positive tool <conversation_id> --tool=send_invoice \
+moda review tool <conversation_id> --tool=send_invoice \
   --tool-use-id=<tool_use_id> --reason="retried upstream"               # one failing tool call
-moda false-positive laziness <conversation_id> --reason="reload is expected"
-moda false-positive hallucination <conversation_id> --reason="price came from the tool result"
-moda false-positive custom-signal <signal_id> --conversation-id=<id> --reason="refund was approved"
-moda false-positive laziness <conversation_id> --undo                    # remove a mark (any kind but problem)
-moda false-positives                                                     # every current mark (--kind=tool, --all, --limit)
-moda false-positives <conversation_id>                                   # marks + problem reviews on a trace
+moda review laziness <conversation_id> --reason="reload is expected"
+moda review hallucination <conversation_id> --reason="price came from the tool result"
+moda review custom-signal <signal_id> --conversation-id=<id> --reason="refund was approved"
+moda review laziness <conversation_id> --verdict=clear                    # remove a mark (any kind but problem)
+moda reviews list                                                     # every current mark (--kind=tool, --all, --limit)
+moda reviews list <conversation_id>                                   # marks + problem reviews on a trace
 ```
 
 What each flag does downstream:
@@ -36,12 +36,12 @@ What each flag does downstream:
 | `quote`, `tool`, `laziness`, `hallucination` | Audit only: recorded for review, never fed back to the detectors |
 
 Find targets with the read commands: `--family`, `--turn` and `--quote` verbatim
-from a `user_quotes` entry in `moda emotions`; a failing call's `tool_use_id` (or `msg_index` when it has none) from
-`moda tool-failure-detail <tool_name>`;
-laziness traces from `moda laziness`; hallucination traces from
-`moda hallucinations`; custom-signal hits from `moda trace-signals` or
-`moda signal <id> --detections`; problem evidence ids from
-`moda problem <id> --evidence`.
+from a `user_quotes` entry in `moda detections list --family=emotion`; a failing call's `tool_use_id` (or `msg_index` when it has none) from
+`moda detections tools <tool_name>`;
+laziness traces from `moda detections list --family=laziness`; hallucination traces from
+`moda detections list --family=hallucination`; custom-signal hits from `moda detections list --family=custom_signal` or
+`moda detections list --family=custom_signal --signal-id=<id>`; problem evidence ids from
+`moda problems get <id> --evidence`.
 
 **Custom signals** are tenant-defined behaviors (pass/fail criteria) judged on
 every trace. Read them, then label hits so each signal has labelled examples:
@@ -49,9 +49,9 @@ every trace. Read them, then label hits so each signal has labelled examples:
 ```bash
 moda signals                                          # every signal: criteria, status, 7-day judged/matched
 moda signal <signal_id>                               # one signal's summary
-moda signal <signal_id> --detections --days-back=30   # recent hits (limit 1–20, --offset to page)
-moda trace-signals <conversation_id>                  # signal hits on one trace
-moda signal-label <signal_id> --conversation-id=<id> --label=does_not_fit \
+moda detections list --family=custom_signal --signal-id=<signal_id> --days-back=30   # recent hits (limit 1–20, --offset to page)
+moda detections list --family=custom_signal --conversation-id=<conversation_id>                  # signal hits on one trace
+moda review custom-signal <signal_id> --conversation-id=<id> --verdict=false_positive \
   --note="refund was approved" --msg-index=<anchor_msg_index>
 ```
 
@@ -62,18 +62,18 @@ message, and always give a `--note` when rejecting. Labels are throttled to 10
 per minute per API key and are never retried automatically.
 
 **Problem detections** (the dashboard's flag on problem evidence) are reviewed with
-`detection-review`. A `false_positive` drops the detection out of
-`moda problem <id> --evidence` and is fed back to the problem reader; `clear`
+`moda review problem-detection`. A `false_positive` drops the detection out of
+`moda problems get <id> --evidence` and is fed back to the problem reader; `clear`
 undoes an earlier review.
 
 ```bash
-moda detection-reviews <conversation_id>              # problem detections on a trace + review state
-moda detection-review <problem_id> --conversation-id=<id> \
+moda reviews list <conversation_id> --kind=problem-detection              # problem detections on a trace + review state
+moda review problem-detection <problem_id> --conversation-id=<id> \
   --attribution-id=<uuid> --verdict=false_positive --note="retry was expected"
-moda detection-review <problem_id> --conversation-id=<id> \
+moda review problem-detection <problem_id> --conversation-id=<id> \
   --attribution-id=<uuid> --verdict=clear             # undo
 ```
 
-`attribution_id` comes from `moda detection-reviews <conversation_id>` or
-`moda problem <problem_id> --evidence`. Prefer `detection-review` over
-`problem-feedback --action=flag_attribution` for a single wrong detection.
+`attribution_id` comes from `moda reviews list <conversation_id> --kind=problem-detection` or
+`moda problems get <problem_id> --evidence`. Prefer `review problem-detection` over
+`problems feedback --action=flag_attribution` for a single wrong detection.

package/skills/moda-cli/references/troubleshooting.md

@@ -14,9 +14,9 @@ Loaded on demand from the moda-cli skill.
   mode prints prose to stderr. Check the exit code before claiming success.
 - An unknown trace, problem, or cluster id exits 1 with
   `errors[0].code: "not_found"`; it is not an empty success.
-- `moda world-state` returns success with a warning when state is missing.
+- `moda traces state` returns success with a warning when state is missing.
   This can mean an unknown trace or a real trace without generated state.
-  Use `moda context <id> --metadata-only` to check whether the trace exists.
+  Use `moda traces get <id> --metadata-only` to check whether the trace exists.
 - If the JSON has `"conversations": []` or `"frustrations": []`, the call
   worked but the time window is empty. Widen the window once
   (`--days-back` on detection commands, `--time-range` on `traces`,
@@ -36,7 +36,7 @@ save it with `moda auth login --api-key`.
 **`not_found` (exit 1)**
 The trace, problem, or cluster id does not exist in this tenant (a trace with
 no generated world state returns a warning, not `not_found`).
-`errors[0].cause` names the listing command: `moda search`/`moda traces`,
+`errors[0].cause` names the listing command: `moda traces search`/`moda traces`,
 `moda problems`, `moda clusters`. A tool name with no failures in the window
 returns an empty result with a warning instead.
 
@@ -52,7 +52,7 @@ warning that gives the `--all` command for a wider slice.
 Widen the window: try `--days-back=30` or `--time-range=30d`. Confirm with
 `moda overview` that data exists in the tenant at all.
 
-**`moda search` returns nothing, or semantic feels like keyword**
+**`moda traces search` returns nothing, or semantic feels like keyword**
 The default `--time-range` is `all`, so an empty result usually means the
 phrasing, not the window: try a shorter phrase or the exact identifier with
 `--mode=keyword`, and add `--include-tool-io` for strings that only appear in

package/dist/cli-7ea02wca.js

@@ -1,30 +0,0 @@
-import {
-  resolveTenantId
-} from "./cli-5ke3xe6y.js";
-
-// src/api-key-headers.ts
-var PLATFORM_API_KEY_PREFIX = "moda_pk_";
-var TENANT_HEADER = "x-moda-tenant-id";
-function isPlatformApiKey(key) {
-  return Boolean(key?.startsWith(PLATFORM_API_KEY_PREFIX));
-}
-var platformTenantOverride;
-function setPlatformTenantOverride(tenantId) {
-  platformTenantOverride = tenantId;
-}
-var TENANT_PATH = /\/tenants\/([^/?#]+)/;
-function tenantFromUrl(url) {
-  const match = url ? TENANT_PATH.exec(url) : null;
-  return match ? decodeURIComponent(match[1]) : undefined;
-}
-function apiKeyHeaders(key, options = {}, url) {
-  const headers = { "x-api-key": key };
-  if (isPlatformApiKey(key)) {
-    const tenantId = tenantFromUrl(url) || platformTenantOverride || resolveTenantId(options);
-    if (tenantId)
-      headers[TENANT_HEADER] = tenantId;
-  }
-  return headers;
-}
-
-export { isPlatformApiKey, setPlatformTenantOverride, apiKeyHeaders };