@moda-ai/cli 1.55.37 → 1.55.39

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

@@ -44,6 +44,59 @@ slice centered on the anchor. `--window=N` (1–5, default `1`) is the
 half-width; `--window=1` ⇒ 3 messages total (anchor ± 1), the canonical
 "three lines" view.
 
+### 5a. Per-trace lists and dashboard filters (`--group-by=trace`)
+
+By default emotion and frustration rows are one per (trace, family)
+detection, and hallucination rows are one per scored message, so their
+`pagination.total` is NOT the dashboard's trace count. Every list response
+says which counting it uses in `counting` (`per_detection`, `per_message` or
+`per_trace`), and the agent summary repeats it.
+
+`--group-by=trace` reads the dashboard Signals tab's own list: one row per
+trace in `traces[]`, the dashboard's filters and sort, and a total that
+counts traces exactly as the dashboard does. Any filter below implies it.
+
+```bash
+moda detections list --family=emotion --group-by=trace                       # emotion tab, per trace
+moda detections list --family=frustration --trajectory=building              # implies --group-by=trace
+moda detections list --family=emotion:sadness --elicitor=bot --status=detected
+moda detections list --family=emotion --signal=sarcasm,anger --sort=risk_score --order=desc
+moda detections list --family=hallucination --rule=<rule_id> --status=all    # rule ids: summary.rule_breakdown
+moda detections list --family=hallucination --source=judge --sort=last_detected_at
+moda detections list --family=laziness --status=strong --sort=strong_count   # laziness is always per trace
+```
+
+| family | flags (values) |
+|---|---|
+| emotion, frustration | `--search` (trace ID or cause), `--status=all\|detected`, `--elicitor=bot\|external\|self\|ambiguous`, `--trajectory=none\|building\|peak\|resolved\|sustained`, `--signal=<s>[,<s>]`, `--sort=score\|risk_score\|detected_at\|message_count`, `--order=asc\|desc` |
+| hallucination | `--search` (trace ID), `--status=contradicted\|all`, `--rule=<rule_id>`, `--source=rule\|classifier\|gpu\|judge\|human`, `--sort=contradicted_count\|verified_count\|last_detected_at`, `--order` |
+| laziness | `--search` (trace ID), `--status=all\|strong`, `--sort=detections_count\|strong_count\|last_detected_at`, `--order` |
+
+The per-trace list has no user scope and no single-trace read: `--user-id`,
+`--conversation-id`, `--include-window` (and `--kind` for hallucinations) are
+rejected with it; drop the trace filters to use them. `summary` in a per-trace
+response covers the whole window and ignores the list filters (except
+hallucination `--rule`, which scopes the summary too, as on the dashboard).
+
+### 5b. Detector switched off, or trace not processed
+
+An empty detection list is not proof a trace is clean:
+
+- **Detector off.** `moda overview` lists every detector under `detectors`
+  (`enabled: true|false|null`, the `setting` it reads). The emotion stage
+  (every emotion family, frustration included) reads `signals.frustration`;
+  custom signals read `signals.custom_signals`; laziness, hallucination and
+  tool failures have no tenant switch. `detections list --family=emotion|frustration`
+  and `--family=custom_signal` carry the same state in `processing` and warn
+  when it is off.
+- **Not processed yet.** `traces list` rows carry `processing_status`
+  (`pending` until the pipeline completes the trace, then `complete`),
+  `error_message`, `indexed_at` and `membership_score` (use-case confidence
+  for `cluster_id`), the same values as the dashboard trace list.
+  `traces get` (including `--all`) carries them in `trace_state`. Both warn on
+  pending or errored traces: a pending trace may already have some detections,
+  but its detections may be incomplete.
+
 ### 6. Tool failure investigation
 
 ```bash

package/skills/moda-cli/references/production-intelligence.md

@@ -72,7 +72,7 @@ Problem, or before hand-editing prompt/skill files in a repo that talks to Moda.
 ```bash
 moda investigate                             # rank tool failures, frustrations,
                                              # and top Problems with evidence
-moda problems                                # cross-signal Problems by root cause
+moda problems list                           # the Problems the dashboard shows (dream grouping or Book)
 moda problems get <problem_id>                    # compact dossier: what, where, how often
 moda problems get <problem_id> --full             # every dossier block (large)
 moda problems get <problem_id> --evidence         # attribution rationales and anchors