saffron-ai 0.9.8 → 0.9.9

package/CHANGELOG.md

@@ -5,6 +5,68 @@ 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.9: A browser matrix in one run
+
+Released 2026-10-06.
+
+Runner
+
+- **A browser matrix in one run.** `saffron run --browser
+  chromium,firefox,webkit` (or a list in `browser`) runs the suite in each
+  browser, one after another, into one report: a row per scenario per
+  browser, in the terminal, the report, the history and the dashboard.
+  Chromium-family browsers go first, so Firefox and WebKit replay what
+  they recorded. Every browser starts before anything runs. Screenshots
+  and traces are kept per browser, and `saffron trace` names them
+  `feature:scenario@browser`. The dashboard stands a scenario at its
+  worst browser and never calls a difference between browsers flaky.
+  Refused with `--shard`. Every result now names its browser, so running
+  one browser again replaces that browser's rows and keeps the others'.
+  `saffron status --json` (and the MCP `project_status` tool) names the
+  browser of each row that needs attention.
+- **Device and viewport profiles.** `--device "iPhone 15"` (config
+  `device`) runs every scenario under a Playwright device profile,
+  recordings and heals included; `--viewport 1280x720` (config `viewport`)
+  sets the size alone. An unknown device names the closest ones, and a
+  mobile profile in Firefox stops the run up front.
+- **Parallel recording and healing.** `--agent-workers N` (config
+  `agentWorkers`, default 1) lets up to N agent sessions run at once,
+  each in a browser of its own. An outline's rows stay together on one
+  worker. Each session is paid for: raise it deliberately.
+- **Shards know their browser.** A shard records the browser it ran in;
+  `saffron report --merge` refuses shards of different browsers, a
+  re-run attempt replaces only its own browser's shard, and each
+  browser's merge keeps its own history line.
+- **A bad storage state stops the run first.** A `storageState` file that
+  is missing, unreadable or not JSON now stops the run at startup, exit 2,
+  before `--rerecord` deletes any recording.
+- **No second replay without an agent.** With `--workers` and
+  `--no-agent`, or in Firefox and WebKit, a scenario that went red in the
+  parallel phase is no longer run again afterwards: nothing could change
+  its result.
+- **Per-worker timing.** The report has a timing panel (each worker's
+  runs, busy time and share, and the five slowest scenarios), and the
+  terminal prints each worker's share and the three slowest scenarios.
+  Merged shards list each machine's workers.
+- **Saffron's own data in the replay.** Each step shows the tabs it
+  opened or switched to and the response each network check matched,
+  and the Saffron pane shows what the agent cost for the scenario. The
+  report's steps carry `tabs` and `responses` for tools.
+- **Browsers in the editors' contracts.** `saffron status --json` and
+  `saffron report --run <id> --json` give each row its `browser`, and the
+  run's `browsers` when its rows span several.
+
+VS Code extension 0.6.2
+
+- After a browser-matrix run, Last Run and a CI run's results label each
+  row with its browser, and Open Replay and Open Trace open that
+  browser's execution alone (`feature:scenario@browser`).
+
+JetBrains plugin 0.6.2
+
+- The same in the Last Run and CI Runs tabs: rows say their browser, and
+  the replay opens that browser's execution alone.
+
 ## 0.9.8: Run one scenario, from the editor too
 
 Released 2026-10-06.

package/README.md

@@ -73,7 +73,7 @@ node dist/cli/index.js -p examples accept --all
 
 | Command | What it does |
 |---|---|
-| `saffron run [paths] [--headed] [--filter expr] [--rerecord] [--no-agent] [--strict] [--browser b] [--no-hooks] [--workers n] [--heal-model m] [--no-verify] [--no-reuse] [--model m] [--storage-state f] [--trace mode]` | Run features. Cached replays are deterministic; misses/failures escalate to the agent (unless `--no-agent`). A path with a line or a name, `features/login.saffron:12` or `"features/login.saffron:Successful login"`, runs that one scenario. Replay cross-browser with `--browser firefox\|webkit`, parallelize with `--workers N`, heal on a cheaper model with `--heal-model`, keep an execution trace with `--trace retain-on-failure`. Exit 1 on red (and on yellow with `--strict`). |
+| `saffron run [paths] [--headed] [--filter expr] [--rerecord] [--no-agent] [--strict] [--browser b[,b...]] [--device name] [--viewport WxH] [--no-hooks] [--workers n] [--agent-workers n] [--heal-model m] [--no-verify] [--no-reuse] [--model m] [--storage-state f] [--trace mode]` | Run features. Cached replays are deterministic; misses/failures escalate to the agent (unless `--no-agent`). A path with a line or a name, `features/login.saffron:12` or `"features/login.saffron:Successful login"`, runs that one scenario. Replay cross-browser with `--browser firefox\|webkit`, parallelize with `--workers N`, heal on a cheaper model with `--heal-model`, keep an execution trace with `--trace retain-on-failure`. Exit 1 on red (and on yellow with `--strict`). |
 | `saffron accept [files... \| --all] [--include-unverified] [--include-imported] [--with-feature-edit] [--propagate]` | Promote cache proposals to committed caches (`--all` skips UNVERIFIED ones unless `--include-unverified`, and ones imported from a CI run unless `--include-imported`); `--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. |
@@ -155,7 +155,7 @@ milestones, statuses and decision gates, and everything shipped so far in
 its "Where we are" table.
 Headlines ahead: API testing (reusable REST operations, fixtures and schema
 validation), scenarios with two users in two browsers, a configurable
-features folder, parallel recording and a browser matrix in one run, failure video,
+features folder, failure video,
 agent-blind secrets, LLM-less MCP replay, the Level-2 shared step library
 (gated on Level-1 divergence data), and the long-term open-core SaaS layer.