@moda-ai/cli 1.55.8 → 1.55.10

package/dist/{provision-parsn3xg.js → provision-5pkn25hh.js}

@@ -1,15 +1,15 @@
 import {
   selectTenantAndCreateKey
-} from "./cli-fhfdnvh4.js";
+} from "./cli-7s48d6ty.js";
 import {
   loadAuthSession
-} from "./cli-tw8jj190.js";
+} from "./cli-4f0p8erk.js";
 import {
   CliAuthError,
   resolveIngestUrl,
   resolveModaBaseUrl,
   stringOption
-} from "./cli-mx9r1689.js";
+} from "./cli-0qnghzg4.js";
 import"./cli-0v6na3yp.js";
 
 // src/provision.ts

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@moda-ai/cli",
-  "version": "1.55.8",
-  "description": "CLI for Moda - AI agent analytics and observability",
+  "version": "1.55.10",
+  "description": "CLI for Moda: production monitoring and evals for AI agents.",
   "type": "module",
   "bin": {
     "cli": "./dist/cli.js",
@@ -19,7 +19,6 @@
     "dist/**/*.js",
     "dist/**/*.d.ts",
     "!dist/__tests__",
-    "hooks/**",
     "skills/**",
     "README.md"
   ],
@@ -43,11 +42,11 @@
   },
   "keywords": [
     "moda",
+    "ai-agents",
+    "agent-monitoring",
+    "evals",
     "llm",
-    "observability",
-    "cli",
-    "analytics",
-    "ai-agents"
+    "cli"
   ],
   "author": "Moda <hello@moda.dev>",
   "license": "MIT",
@@ -69,6 +68,7 @@
     "@moda/harness-bundle": "*",
     "@moda/harness-snapshot": "*",
     "@moda/integration-skills": "*",
+    "@moda/messaging": "*",
     "@types/node": "^22.10.5",
     "eslint": "^9.17.0",
     "typescript": "^5.7.2",

package/skills/integration/index.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "moda.skill_index.v1",
-  "bundled_at": "2026-10-14T16:47:16.312Z",
-  "cli_version": "1.55.8",
+  "bundled_at": "2026-10-15T04:43:16.280Z",
+  "cli_version": "1.55.10",
   "skills": [
     {
       "id": "integration-cloudflare-think",

package/skills/moda-cli/SKILL.md

@@ -1110,7 +1110,7 @@ What each flag does downstream:
 |---|---|
 | `problem` | Dismisses the problem: it leaves `moda problems` and the dashboard at once, and the reason is folded into the next reconcile. Cannot be undone from the CLI |
 | `problem-detection` | Drops that evidence from the problem and teaches the problem reader (same as `detection-review --verdict=false_positive`) |
-| `custom-signal` | Saved as a `does_not_fit` label with the reason, so the signal learns from it and the live match is retracted (same as `signal-label`). `--undo` removes the label |
+| `custom-signal` | Saved as a `does_not_fit` label with the reason, a labelled counterexample for the signal, and the live match is retracted (same as `signal-label`). `--undo` removes the label |
 | `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
@@ -1122,7 +1122,7 @@ laziness traces from `moda laziness`; hallucination traces from
 `moda problem <id> --evidence`.
 
 **Custom signals** are tenant-defined behaviors (pass/fail criteria) judged on
-every trace. Read them, then label hits so the signal learns:
+every trace. Read them, then label hits so each signal has labelled examples:
 
 ```bash
 moda signals                                          # every signal: criteria, status, 7-day judged/matched
@@ -1291,8 +1291,8 @@ moda feedback "trace is a refund request, not this problem" \
   you saw.
 - Feedback does not change the problem itself. To act on a misroute directly,
   use `moda problem-feedback <problem_id> --action=flag_attribution
-  --attribution-id=<uuid> --reason=TEXT`, `moda false-positive <kind> <target>
-  --reason=TEXT`, or `moda fix dismiss <fix_id> --reason=TEXT`.
+  --attribution-id=<uuid> --reason=TEXT` or `moda false-positive <kind> <target>
+  --reason=TEXT`.
 - Never include secrets or full transcripts in the note.
 
 ## Validation — how to know it worked

package/hooks/moda-snapshot.sh

@@ -1,41 +0,0 @@
-#!/usr/bin/env bash
-# Moda shadow workspace hook for coding agents.
-# Triggered by Claude Code, Codex, and Cursor lifecycle/tool matchers.
-#
-# Claude Code passes hook context as a JSON object on stdin (per the Claude
-# Code hooks reference): session_id, tool_use_id, prompt, hook_event_name,
-# etc. We forward that stdin straight through to `moda workspace snapshot
-# --hook-stdin`, which parses it server-side so the CLI sees the same
-# correlation keys (session_id, tool_use_id, prompt_sha) the ingest worker
-# will later join on. The previous version read $CLAUDE_SESSION_ID and
-# $CLAUDE_PROMPT_HASH env vars, but Claude never sets those — so session_id
-# and prompt-level joins were unrecoverable. Reading stdin fixes that.
-#
-# Runs `moda workspace snapshot` in the background so the hook never blocks
-# Claude; redirects all output to /dev/null so user-visible output stays
-# clean; always exits 0 so a transient failure can't break the user session.
-
-set +e
-case "${1:-}" in
-  claude|claude_code|codex|cursor)
-    PROVIDER="$1"
-    EVENT="${2:-UserPromptSubmit}"
-    ;;
-  *)
-    PROVIDER="claude_code"
-    EVENT="${1:-UserPromptSubmit}"
-    ;;
-esac
-MODA_SNAPSHOT_BIN="${MODA_BIN:-moda}"
-
-# Buffer the hook JSON once so the background subshell sees it after this
-# script's stdin is closed by Claude.
-PAYLOAD="$(cat)"
-
-(
-  printf '%s' "$PAYLOAD" \
-    | "$MODA_SNAPSHOT_BIN" workspace snapshot --provider "$PROVIDER" --event "$EVENT" --json --hook-stdin \
-    > /dev/null 2>&1
-) &
-
-exit 0