@moda-ai/cli 1.26.0 → 1.27.1

package/dist/{index-efv643ec.js → index-fwxpt51s.js}

@@ -9,7 +9,7 @@ import {
   runPromptSync,
   runSkillSync,
   upsertSkillManifestRecord
-} from "./cli-xf5nx5hc.js";
+} from "./cli-cjqzrp9k.js";
 import {
   codingAgentDisplayName,
   describeCodingAgentEvent,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moda-ai/cli",
-  "version": "1.26.0",
+  "version": "1.27.1",
   "description": "CLI for Moda - AI agent analytics and observability",
   "type": "module",
   "bin": {

package/skills/integration/index.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "moda.skill_index.v1",
-  "bundled_at": "2026-08-17T00:50:53.917Z",
-  "cli_version": "1.26.0",
+  "bundled_at": "2026-08-19T08:07:44.284Z",
+  "cli_version": "1.27.1",
   "skills": [
     {
       "id": "integration-node-anthropic",

package/skills/moda-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: moda-cli
-version: 2.2.0
+version: 2.4.0
 description: Query Moda's AI agent conversation analytics and manage code-first prompt versions from the terminal — semantic/keyword/hybrid message search, overview KPIs, topic clusters, message context, user frustration detections, tool failures, and moda prompts status/sync/promote. Use when the user asks about moda, modaflows, conversation analytics, prompt management, user frustrations, agent observability, tool failure debugging, wants to find conversations or tool calls about a topic, or wants to investigate how their AI agent is performing.
 ---
 
@@ -55,9 +55,9 @@ Optional:
 
 - `MODA_BASE_URL` defaults to `https://moda.dev`; override only for
   self-hosted or staging.
-- `MODA_SKILL_VERSION` — export to `2.2.0` so search-adoption telemetry can
+- `MODA_SKILL_VERSION` — export to `2.3.0` so search-adoption telemetry can
   attribute usage to this skill version. Set it once per session:
-  `export MODA_SKILL_VERSION=2.2.0`.
+  `export MODA_SKILL_VERSION=2.3.0`.
 
 ## Setup
 
@@ -614,6 +614,77 @@ Do not copy prompt text from the dashboard into source code. The repo prompt
 files are the source of truth; the dashboard is for visibility, usage, labels,
 and future evals.
 
+### 8. Fixing detected Problems (`moda fix` — a fix with proof)
+
+Moda turns detected Problems into **Fixes**: a routed candidate change plus a
+replay **gate** that proves it on held-out production evidence. Use this loop
+whenever you are asked to fix a detected Problem, or before hand-editing
+prompt/skill files in a repo that talks to Moda.
+
+Fixes are typed by where the evidence points: `PROMPT` (a managed prompt
+revision — the checkout/verify/submit loop below), `TOOL_SCHEMA` (a proposed
+rewrite of one tool's description), and `SKILL` (a drafted SKILL.md for an
+agent-behavior problem). Tool and skill candidates are not repo files: read
+them from the packet (they are also written locally under
+`.moda/fixes/<SHORTREF>/`), apply them in your own stack, then confirm with
+`moda fix mark-applied` — no GitHub integration required.
+
+The fail-to-pass loop:
+
+```bash
+moda fixes                                   # ranked queue of fixes with proof
+moda fix <fix_id> --packet                   # moda.fix_packet.v1: cause, target
+                                             # file, evidence links, verify cmd,
+                                             # handback + magic word; tool/skill
+                                             # candidates land in .moda/fixes/
+moda fix start <problem_id> --wait           # draft from a Problem and drive
+                                             # scope -> propose -> gate
+moda fix checkout <fix_id>                   # PROMPT fixes: write the candidate
+                                             # at its target source path
+                                             # (NEVER runs git)
+# ...edit the target file...
+moda fix verify <fix_id> --prompt-file=<path>  # re-gate local content on the
+                                               # frozen holdout (PROMPT only)
+# iterate edit -> verify until exit 0, then hand back:
+moda fix submit <fix_id> --pr                # draft PR via the Moda GitHub App
+moda fix submit <fix_id> --local-ref=<branch>  # or record your own branch
+moda fix mark-applied <fix_id> --note="…"    # tool/skill/no-PR path: confirm a
+                                             # candidate you applied yourself
+moda fix dismiss <fix_id> --reason="why"     # reject (feeds problem feedback)
+```
+
+**`moda fix verify` exit codes are the contract — branch on them:**
+
+| Exit | Meaning | How to treat it |
+|---|---|---|
+| `0` | gate pass — the candidate beat baseline on the frozen holdout (wins clear the noise floor) | Safe to submit. |
+| `1` | gate fail — per-case findings ride the envelope's `findings[]` (`case:<id>` entries with baseline/candidate pass) | Edit the candidate and re-`verify`. |
+| `3` | degraded/inconclusive — too many abstentions, blocked coverage, or no verdict | **Never treat as a pass.** Re-verify or read `moda fix <fix_id> --packet`. |
+
+Rules that keep the proof honest:
+
+- The verdict reads only **holdout** cases the proposer never saw; repair
+  rows are training cases, never the headline.
+- The gate compares against a noise floor from a baseline-vs-baseline control
+  run — a "win" inside the noise floor does not pass.
+- `checkout` only writes the file. Branching (`moda/fix/<shortref-lower>`),
+  committing, and pushing are yours; the CLI never runs git.
+- Fix PRs end with the magic word `Fixes MODA-FIX-<SHORTREF>` in the body —
+  Moda-authored PRs carry it automatically; hand-authored PRs must include it
+  so the merge confirms the fix and starts production monitoring.
+- `mark-applied` is the confirmation for changes shipped without a PR (tool
+  descriptions, installed skills, hand-applied prompts): it flips the fix to
+  `SHIPPED`, records your `--note`, and starts the same monitoring the merge
+  webhook would. It is idempotent — repeating it is a duplicate no-op.
+- `TOOL_SCHEMA` fixes gate like prompt fixes (both arms pin the same current
+  prompt; the proposed description is the only delta). `SKILL` fixes rest at
+  `PROPOSED` until the skill is registered with the Moda skill harness — an
+  inline drafted SKILL.md cannot enter the gate, so deliver it via the packet
+  and `mark-applied`.
+- The pipeline is advance-on-poll: `--wait` (on `start`, `verify`, or
+  `moda fix <fix_id> --wait`) drives it; a fix left `GATING` will not finish
+  on its own.
+
 ## Common workflow recipes
 
 ### Find where something happened (search → context)
@@ -791,6 +862,14 @@ npx: `npx -p @moda-ai/cli moda <command>`.
 | `moda prompts diff` | Read-only local prompt diff/status |
 | `moda prompts sync` | Upload changed prompt versions and update lockfile |
 | `moda prompts promote <key>` | Move a remote prompt label |
+| `moda fixes` | Ranked queue of Fixes ("a fix with proof"); `--status=S`, `--limit=N`, `--cursor=TOKEN` |
+| `moda fix <fix_id>` | One Fix: status + gate result; `--packet` prints `moda.fix_packet.v1` and writes tool/skill candidates under `.moda/fixes/<ref>/`; `--wait` drives a running pipeline to rest |
+| `moda fix start <problem_id>` | Draft a Fix from a Problem (`--type=auto\|prompt`); `--wait` drives scope → propose → gate |
+| `moda fix verify <fix_id>` | Re-gate on the frozen holdout; `--prompt-file=P` gates local content, PROMPT fixes only (exit `0` pass / `1` fail with per-case findings / `3` degraded — never a pass) |
+| `moda fix checkout <fix_id>` | Write the candidate at its target source path (never runs git; PROMPT fixes only) |
+| `moda fix submit <fix_id>` | Deliver: `--pr` opens a draft PR \| `--local-ref=<branch>` records your branch |
+| `moda fix mark-applied <fix_id>` | Confirm a candidate you applied in your own stack (`--note=TEXT`, ≤600 chars); no PR needed — flips to SHIPPED and starts monitoring |
+| `moda fix dismiss <fix_id>` | Reject with `--reason=TEXT` (feeds problem feedback) |
 
 `moda search` flags: `--mode=keyword|semantic|hybrid` (default `hybrid`),
 `--user-id`, `--time-range=<range>`, `--limit=N` (1–100, default 20).