saffron-ai 0.9.3 → 0.9.4

package/CHANGELOG.md

@@ -5,6 +5,50 @@ the VS Code extension (`ChathurangaJayasinghe.saffron-vscode`) and the
 JetBrains plugin (`ai.saffron.jetbrains`). Dates are publish dates. Each
 release heading names its main feature: `## <version>: <title>`.
 
+## 0.9.4: The suite's quality at a glance
+
+Released 2026-10-04.
+
+Runner
+
+- **The agent skill knows the new features.** It shows tag expressions
+  in `--filter`, `saffron trace`, and a CI job that exports its heals as
+  a bundle (or a draft pull request) for `saffron runs` and `saffron
+  import --run`. The AGENTS.md / CLAUDE.md block `saffron init` writes
+  says how a CI heal arrives, and the `project_status` MCP tool says
+  which run an imported proposal came from. Run `npx saffron init` again
+  to update a project's copy.
+- **`saffron dashboard`: the suite's quality at a glance.** A page in
+  the run report's design, read from `.saffron/history.jsonl`: tests,
+  the share passing (each scenario's latest result), failing scenarios
+  and for how many runs in a row, flaky ones (passed and failed by turns
+  over the last 20 runs), ones the agent healed again and again, never
+  run and left out of the last run, the slowest, pass rate and execution
+  time per run, and results per tag. It writes
+  `.saffron/reports/dashboard.html` and opens it; `--stdout` prints the
+  page for the IDE panels. The same numbers are in `saffron status
+  --json` as `quality`.
+
+VS Code extension 0.5.0
+
+- **The dashboard is the suite's quality page**, the one `saffron
+  dashboard` renders, instead of the run report. Click a scenario's
+  name to open it. Needs saffron-ai 0.9.4 or later.
+- **Last run: Open Replay and Open Report in the title bar.** Open
+  Replay opens every scenario the run traced, so it works when
+  everything passed and no row is listed; Open Report opens the HTML
+  report in the browser.
+
+JetBrains plugin 0.5.0
+
+- **The Dashboard is the suite's quality page**, the same one as in VS
+  Code, instead of the embedded run report. Click a scenario's name to
+  open it. Needs saffron-ai 0.9.4 or later.
+- **Last Run: Open Report** opens the run's HTML report in the browser.
+- **Last Run: Open Replay works when everything passed.** With no row to
+  select it did nothing; it now opens every scenario the run traced, or
+  says how to keep traces when the run kept none.
+
 ## 0.9.3: Review CI heals on your machine
 
 Released 2026-10-04.

package/README.md

@@ -77,13 +77,14 @@ node dist/cli/index.js -p examples accept --all
 | `saffron accept [files... \| --all] [--include-unverified] [--with-feature-edit] [--propagate]` | Promote cache proposals to committed caches (`--all` skips UNVERIFIED ones unless `--include-unverified`); `--with-feature-edit` also rewrites the adapted steps in the `.feature` file (and keeps the cache in sync); `--propagate` applies the heal's locator fixes to every other cache using the same locator. One heal repairs N scenarios before they ever fail. No args: list pending proposals. |
 | `saffron reject [files... \| --all]` | Discard proposals; the agent will try again next run. |
 | `saffron export [-o file] [--branch name]` / `saffron runs` / `saffron import <bundles...> \| --run <id>` | Carry a CI heal to your machine: export packs the run's proposals, report, screenshots and traces into one bundle for CI to upload; `runs` lists the branch's CI runs (GitHub Actions or Azure Pipelines); import (of a file, or of a run with `--run`) checks the bundle against your checkout (repository, each proposal's binding) and files it there, ready for `saffron diff` and `saffron accept`. `--branch` also has CI commit the proposals to a new branch and open a draft pull request with their diffs. |
-| `saffron status [--json]` | Project overview for people, IDE panels and dashboards: feature files and scenarios with cache state, tags, pending proposals, last run, history, vocabulary health (divergent steps, duplicate wordings proven by identical recordings), effective config. |
+| `saffron status [--json]` | Project overview for people, IDE panels and dashboards: feature files and scenarios with cache state, tags, pending proposals, last run, history, vocabulary health (divergent steps, duplicate wordings proven by identical recordings), effective config, and suite quality from the run history (failing, flaky, never run, slowest, trends, per tag). |
 | `saffron steps [search] [--json] [--snippets]` | List/search the step vocabulary (files + caches) with recorded/divergent/unrecorded badges and usage; `--snippets` writes `.vscode/saffron.code-snippets` for native VS Code completion. |
 | `saffron mcp` | Serve the vocabulary and the project overview to AI assistants over stdio MCP (`search_steps`, `list_step_sets`, `project_status`), e.g. `claude mcp add saffron -- npx saffron mcp`. |
 | `saffron author <prose-file> [-o out]` | Draft a `.saffron` feature file from plain-paragraph requirements, reusing the project's step vocabulary (AI; reports how many lines are seedable). |
 | `saffron lsp` | Run the Saffron language server over stdio for JetBrains (LSP4IJ/Ultimate), Neovim, any LSP editor: badge completion, StepSet go-to-definition, hover, diagnostics. Highlighting for JetBrains comes from the bundled TextMate grammar (`textmate/saffron` in the package); run `npx saffron lsp` in a terminal for setup steps. |
 | `saffron init [--agents list] [--examples]` | Make the project agent-ready (`--examples` installs the Saucedemo example suite): installs the bundled **Saffron agent skill** into `.claude/skills` and `.agents/skills` (Copilot/Cursor via `--agents`), registers the `saffron mcp` server in `.mcp.json` / `.cursor/mcp.json` / `.vscode/mcp.json`, adds a managed block to `AGENTS.md`/`CLAUDE.md`, scaffolds config. |
 | `saffron report` | Open the latest HTML report. |
+| `saffron dashboard` | Open the suite's quality dashboard: failing, flaky and never-run scenarios, repeated heals, slowest, trends, per tag. |
 | `saffron trace [scenario] [--port n] [--no-open] [--json]` | Open the execution replay of the last run (every traced scenario, or the one you name): its Given / When / Then, the page inspectable at every action, the network alongside, and what the agent changed. Needs `"trace": "retain-on-failure"` (or `"on"`). |
 
 Configuration lives in `saffron.config.json` at your project root: