saffron-ai 0.9.1 → 0.9.3

package/CHANGELOG.md

@@ -2,9 +2,407 @@
 
 All notable changes to Saffron, in one place: the `saffron-ai` runner (npm),
 the VS Code extension (`ChathurangaJayasinghe.saffron-vscode`) and the
-JetBrains plugin (`ai.saffron.jetbrains`). Dates are publish dates.
+JetBrains plugin (`ai.saffron.jetbrains`). Dates are publish dates. Each
+release heading names its main feature: `## <version>: <title>`.
 
-## 0.9.1
+## 0.9.3: Review CI heals on your machine
+
+Released 2026-10-04.
+
+Runner
+
+- **A heal made in CI can be reviewed and accepted on your machine.**
+  `saffron export` packs the pending proposals, the run's report and the
+  screenshots and traces it names into one zip, with where the run
+  happened (repository, branch, commit, CI run, shard); CI uploads it as
+  an artifact. `saffron import` checks it against your checkout and files
+  it where a local run would have, so `saffron diff`, `saffron accept`,
+  `saffron trace`, the report and both IDE panels work on it unchanged. A
+  bundle from another repository (by its path; the same path under
+  another host name, such as an SSH host alias, imports with a warning),
+  one that does not say its repository (unless
+  `--allow-unknown-repository`), of a newer format, with a damaged file or
+  a report it cannot show, or with a file over 1 GB (or over 100 times
+  its size unzipped) is refused whole, before anything is written, and so
+  are bundles that add up to over 8 GB unzipped together; a proposal made
+  against a different scenario text or committed recording is refused by
+  name, and the rest import. Bundles are read from disk one file at a
+  time, a URL's downloaded to disk first, so every shard of a large run
+  imports at once. Text from a bundle, in errors and reasons too, is
+  printed without control characters. Export keeps to the same limits:
+  it refuses a file over 1 GB and, when a bundle would be over 4 GB,
+  leaves the traces of green scenarios out first and says so. Shard
+  bundles merge into one report. The imported report says where it came
+  from and links to the CI run. Examples for GitHub Actions and Azure
+  Pipelines are in the guide (§19).
+- **Or CI opens a draft pull request with the heals.**
+  `saffron export --branch <name>` commits the proposal files, not the
+  recordings, onto the commit the run tested (on a pull request build, the
+  head of its branch, where each proposal's binding is checked again and
+  one that does not fit is left out, judged by that commit's own StepSets
+  and data) as a new branch, pushes it and, on GitHub, opens a
+  draft pull request through `gh` whose description is each proposal's
+  verification and diff, with the commands to accept, and a staging line
+  that stages exactly what accept changed (`git add -A .saffron/cache &&
+  git add -u .saffron/proposals`). After a tag build, which tested no
+  branch, name the pull request's branch with `--base`. Only the
+  checkout's HEAD, a commit it merged in or one it descends from is ever
+  built on; a `pull_request_target` build records the base branch and the
+  commit it checked out, never the fork's. The reviewer
+  switches to the branch, runs `saffron accept`, commits and marks it
+  ready: no agent session on their machine. The CI checkout is left as it
+  was, and an existing branch is never pushed onto.
+- **`saffron status --json` says which CI run a proposal was imported
+  from** (`importedFrom`: repository, branch, commit, run and its link,
+  shard), for as long as it is the proposal that was imported, so the
+  editors can show it past the next local run.
+- **`saffron runs` and `saffron import --run <id>`, for GitHub Actions and
+  Azure Pipelines alike.** `runs` lists the branch's CI runs (through `gh`,
+  or `az` with its azure-devops extension), with how many of each run's
+  proposals are pending here; `import --run` downloads a run's bundles and
+  imports them. The repository's host picks the service; a `ci` key in the
+  config sets it, and the Azure DevOps organization and project, for a
+  GitHub repository built by Azure Pipelines. An Azure pull request build
+  is listed under the branch it validates, and only the repository's own
+  builds are listed. Bundles of a re-run take each shard from its latest
+  attempt. `import --run` downloads into a folder under `.saffron/reports`
+  and removes it when done. A download that takes over 10 minutes is
+  stopped and says so. A tag build is listed under its tag on both
+  services. An Azure DevOps SSH remote through a host alias counts as
+  Azure. With `--json`, every `import` failure, an invalid config
+  included, is `{"error": ...}` and exit 2. A `runs --json` whose `gh` or
+  `az` is missing, signed out or failing answers `{provider, branch,
+  runs: [], problem: {kind, message}, error}`, `error` holding the same
+  message, so a client reading either field works; any other failure is
+  `{"error": ...}` alone; both exit 2. On Azure Pipelines the pull
+  request builds are asked for once (`--top 500`), so a listing usually takes
+  three `az` calls, not seven.
+  `export --branch` opens the draft pull request on Azure DevOps too,
+  through `az repos pr create`.
+- **Export streams the bundle to disk.** Screenshots and traces are
+  copied into the zip in chunks, never all held in memory, and the zip
+  is renamed into place only when complete; a file that changes while it
+  is packed is refused.
+- **Failures are one line.** `export` exits 2 for every failure that
+  pushed nothing (an `--out` that is a folder, an invalid config with
+  `--branch`), keeping exit 1 for a branch pushed without its pull
+  request. Any command's expected failure prints `saffron: <message>`
+  and exits 2, never a stack; `SAFFRON_DEBUG=1` shows it.
+- **Safe branch names in the pull request.** The description quotes the
+  branch in its commands, and `--branch` or `--base` with a space, a
+  quote or any of `` $ ` ; | & < > ( ) \ `` is refused up front.
+- **A `pull_request_review` build records its pull request's branch**,
+  read from the event, not `12/merge`.
+- **`import --json` passes on only the manifest fields it knows**, cleaned
+  of control characters.
+- **The pull request's review steps run saffron-ai by name**
+  (`npx -y -p saffron-ai saffron diff`): in a checkout without
+  `node_modules`, a bare `npx saffron` would fetch the unrelated `saffron`
+  package.
+- **A bundle names its run as the CI service does** (`github:<run id>`,
+  `azure:<build id>`), even with `SAFFRON_RUN_ID` set, so `saffron runs`
+  and both editors count its proposals under the right run.
+- **A green scenario's trace over 1 GB is left out of the bundle** like
+  the other green traces, instead of failing the export.
+- **Import hashes, compares and copies traces in chunks**: a 1 GB trace is
+  never held in memory. A bundle that changes on disk while it is
+  imported no longer says "nothing was imported" after some files were
+  written.
+- **`saffron runs` on Azure asks for 50 pull request builds first**, and
+  for more only while too few are the branch's, not 500 on every list.
+
+VS Code extension 0.4.0
+
+- **CI runs**: a new view lists the current branch's CI runs, GitHub
+  Actions or Azure Pipelines, through `saffron runs`. **Import** runs
+  `saffron import --run`, then lists under the run what happened to each
+  proposal and any warning (a checkout at another commit, a scenario that
+  changed since). Imported proposals are marked with the run they came
+  from, linked in the tooltip. From a red CI run to an accepted repair
+  without leaving the editor; commit and push with the Source Control
+  view. The CI's own tool keeps the credentials.
+- **Text from CI cannot act in a tooltip.** Run titles, branch names and
+  a bundle's notes are escaped so they never form links, headings or
+  other markup; a run links out only to GitHub or Azure DevOps, and never
+  when the address carries a user name. Import results are kept per
+  project. An import can be cancelled, and on Windows cancelling stops
+  the whole process tree. The list follows a branch switch, and makes no
+  CI call while its view is hidden.
+- **Cancelling an import stops all of it, and says what it left.** On
+  Windows the whole process tree is stopped however the CLI was started;
+  on macOS and Linux a process that outlives SIGTERM gets SIGKILL. The
+  message says a cancelled import may have written part of the run.
+
+JetBrains plugin 0.4.0
+
+- **CI Runs tab**: the same runs and the same Import, through the same
+  two commands, with each proposal's outcome under its run. The Proposals
+  tab names the CI run an imported proposal came from.
+- **Text from CI is shown as plain text**, in CI Runs and in Last Run
+  after an import, never as markup. Import is a background task you can
+  cancel, with no time limit; a run is imported once even if you switch
+  projects meanwhile; Refresh never starts a second list. The tab loads
+  as soon as the project is trusted, and its processes stop when the
+  project closes.
+- **Choosing another project clears the tabs at once**: a run listed for
+  the last project can no longer be imported into the new one, and a
+  status that arrives late for the last project is dropped.
+- **CI Runs lists again when you check out another branch.** A cancelled
+  import says it may have written part of the run.
+
+## 0.9.2: Bring your own AI agent
+
+Released 2026-09-30.
+
+Runner
+
+- **Browser tool calls are checked call by call.** A security review of
+  the agent's tools found three ways a prompt-injected page could reach
+  the machine: `view-source:file://` slipped past Playwright's `file:`
+  check and read any file; the `filename` option of the snapshot,
+  screenshot, console and network tools wrote page content over any
+  project file (a response body into a bin is code execution on the next
+  run); and a file upload could hand `.env`, with every secret, to the
+  page. Navigation now opens web pages only, uploads take existing files
+  inside the project by their real path (a link out of the project is
+  out) and never dotfiles, `filename` is dropped, and anything the
+  vendor's tools write goes to a private folder of the session, removed
+  when it ends. The checks sit in the one
+  proxy every provider and both paths use, and replay applies the same
+  ones to a cache, which is data anyone can commit. A project reached
+  through a symlinked path (`/var` and `/private/var` on macOS) counts
+  as the project. Claude sessions also set
+  `strictMcpConfig`, so a `.mcp.json` or user-level MCP server of yours
+  never joins a recording. Codex sessions turn off its remaining
+  execution features (`unified_exec`, `multi_agent`, `code_mode_host`,
+  the in-app and external browsers) besides the shell.
+- **Go-to-definition works under a folder with a space, `#` or `%` in
+  its name, and on Windows.** The language server sent unencoded file
+  paths as URIs; a strict client rejected them. A nested project without
+  a `features` key now gets the default folder instead of the outer
+  project's, and on Windows a StepSet in a subfolder is no longer flagged
+  as defined twice.
+- **`--filter "not @wip @slow"` is refused** instead of reading as
+  `not @wip or @slow`: once `and`, `not` or parentheses appear, every
+  tag needs its `and` or `or`. The plain list forms are unchanged.
+- **Outline values no longer replace inside a test id or frame selector
+  by coincidence** (`add` in `add-to-cart`), while a short id with a
+  digit still does (`1234` in `order-1234`), and a `<name>` that opens a
+  regex named group is left alone at replay.
+- **The cost trend leaves a gap for runs whose provider reported no cost**
+  instead of plotting them as $0, and every other run keeps its place. Cursor's turn limit counts tool calls,
+  not the pieces their arguments stream in. An Antigravity session that
+  hits the turn limit says so, and how to raise it, even when agy
+  reports the session a success.
+
+- **No agent can run code on your machine through Playwright.**
+  Playwright MCP's `browser_run_code_unsafe` runs any JavaScript in the
+  Playwright server process (its own docs call it RCE-equivalent); a
+  Codex test session used it to read a file from the home directory. It
+  is now hidden from every provider's agent, Claude's included, and a call
+  to it by name is refused. Nothing recorded depends on it.
+  `browser_evaluate`, which runs in the page, stays.
+- **Claude recordings no longer carry your claude.ai connectors.** On a
+  Claude subscription login, Claude Code loads the account's claude.ai
+  connectors (Gmail, Figma, Canva, ElevenLabs and the like) into every
+  session from its second request on. On one account that added 294 tool
+  definitions, 1.16 MB of schema, to every model call: recording the
+  guestbook example cost $15.74 at API rates and 11.5M cache-read tokens.
+  Saffron's sessions now set `disableClaudeAiConnectors`, and the same
+  recording costs $0.37 with 279k cache-read tokens, in 70 s instead of
+  180 s. The agent never needed those tools; your connectors in Claude
+  itself are untouched.
+- **Record and heal on the subscription you already have.** Besides
+  Claude (still the default), `"provider"` in `saffron.config.json` (or
+  `--provider`) now takes `codex` (a ChatGPT plan, through
+  `@openai/codex-sdk`), `antigravity` (Google AI Pro/Ultra, through
+  Google's `agy` CLI; experimental) and `cursor` (through `@cursor/sdk`).
+  Each runs on the login its official client already has on the machine.
+  These agents reach the browser through a local MCP gateway that records
+  every call with the same hooks as Claude, so their recordings, heals and
+  proof replays work the same. `model` takes the provider's own model
+  names; `saffron author` takes `--provider` too. The two SDKs are
+  optional peer dependencies: install the one you use. Codex runs without
+  your own `~/.codex/config.toml` apart from its login settings (a keyring
+  login works), which needs macOS or Linux for now: on Windows the Codex
+  provider refuses to start rather than run with your own MCP servers.
+  `agy` gets an explicit `--print-timeout` sized to the turn budget, and
+  an `agy` that cannot start fails its scenario instead of the run.
+  Antigravity is verified live with agy 1.2.13 (record, proof replay and
+  heal): its MCP calls go through agy's `call_mcp_tool`, allowed by two
+  rules in agy's settings and limited by a hook to Saffron's two servers.
+- **`saffron login [provider]`** says what a provider still needs on this
+  machine, and does the one-time setup where one is needed:
+  `saffron login cursor` runs Cursor's sign-in, and
+  `saffron login antigravity` checks that agy is signed in and allows
+  Saffron's tools in agy's settings (two rules, everything else kept).
+- **New docs page: AI providers and sign-in** (`docs/PROVIDERS.md`), with
+  every provider's sign-in, what `saffron login` sets up, what Saffron does
+  in its sessions, how to undo it, and troubleshooting.
+- **A pass can no longer leave an assertion unchecked.** `saffron_done`
+  with success is refused once while an announced `Then` step has
+  recorded no check, and Saffron's tool refusals are now MCP errors, so an
+  agent that batches its calls stops and fixes the step instead of filing
+  an unverified proposal. A second pass stands (the proof replay still
+  marks it unverified), so no session burns its turns on it. A step
+  announced twice keeps one adaptation note, and an agent that fails
+  after `saffron_done` keeps its verdict.
+- **Node.js 20.6 or newer** is now required (22.13 for the Cursor
+  provider).
+- **Cost not reported, not $0.** Runs whose provider reports no price say
+  so in the summary line and the report instead of showing $0.0000.
+- **The editor finds a project nested inside a bigger folder.** When the
+  IDE is opened above the Saffron project (a solution folder with the
+  tests in a subfolder), `saffron lsp` now resolves each `.saffron` file
+  against the nearest `saffron.config.json` above it. StepSets defined in
+  a sibling file and `{data:...}` references were reported as undefined
+  in that layout; they resolve now, and completion, hover and
+  go-to-definition follow the same root.
+- **A browser tool result can no longer flood the agent's context.** A
+  recording fetched a 1.5 MB API response body with
+  `browser_network_request` (about 400k tokens). Claude Code then compacted
+  the session in a loop and failed the scenario after a few dollars of
+  tokens. Every browser tool result is now cut at 60,000 characters, with
+  a note asking for less (a snapshot of one region, a filtered request
+  list, or a `saffron_assert` on the field). The Playwright code Saffron
+  records comes first in a result, so a cut result still records its
+  action. The cap applies with and without the trace bridge, and to Codex,
+  Antigravity and Cursor sessions through the tool gateway.
+- **Each Outline row acts on its own element through a locator chain.** A
+  chain keeps the row's value inside its selector; that value now becomes
+  the row's `<param>` (or data-table reference) there too, so another row
+  no longer clicks the recorded row's card. The same goes for every other
+  field replay resolves: an assertion's regex pattern (an `href`, a
+  heading's name), a test id, a prompt answer, a frame and a drag's drop
+  target. An Outline checking a link's `href` failed as written on every
+  row but the recorded one.
+- **A changed table or data value still written in the recording is found
+  escaped too** (in a selector's quoted or regex body, or a pattern), so
+  the recording is made again instead of replaying the old value.
+- **Chains with a comma, an apostrophe or a role option record the element
+  they clicked.** `filter({ hasText: 'Paris, France' })` and
+  `getByText(/^Don't$/)` recorded nothing, a regex with an apostrophe made
+  a selector Playwright read differently, and `getByRole('heading', {
+  level: 2 })` recorded any heading. Role options are kept as selector
+  attributes; one with no selector form records nothing.
+- **Tag lists read the way 0.9.0 read them.** An empty entry (`@a,@b,`) is
+  skipped again, and a tag's own parentheses (`@issue(42)`) stay part of
+  it; a parenthesis after a space or a keyword still groups.
+- **Replay fixes.** A heal that fixes a network assertion is checked
+  against the response the agent's session produced, instead of failing
+  "as written" while waiting for a new one. A replay no longer inherits an
+  upload armed on its page by an earlier replay (a pending proposal that
+  failed), which failed its first click. A value resolved into a regex
+  pattern (`{env:VAR}`, `<param>`, `{data:...}`) matches as written: the
+  `+` in `a+b@x.com` or the `$` in `$9.99` no longer change the pattern.
+- **A failed tool call records nothing** in Codex, Antigravity and Cursor
+  sessions, as in Claude's: an upload refused because no file chooser was
+  open was recorded, and broke replay.
+- **Antigravity gets its prompt on stdin.** The prompt carries resolved
+  `{env:VAR}` values, and `agy -p` put it in the command line, readable by
+  every account on the machine.
+- **Tools a recording cannot replay are hidden from every agent:** going
+  back or forward, reloading, resizing and dropping files.
+  `browser_navigate` reaches any page instead, and is recorded.
+- **`saffron_done` is refused once when a `Then` step recorded only setup**
+  (a click that opens a panel) and no check, the rule replay applies.
+- **Playwright's MCP server gets the whole environment again** when the
+  trace bridge is off, so `PLAYWRIGHT_MCP_*` settings apply there too.
+- **A proposal lock held by a live process on this machine is broken after
+  an hour**: a pid reused after its holder died kept it forever.
+- **`saffron status` says "cost not reported"** for a provider with no
+  price, instead of $0.00. `saffron status --json` leaves such a cost
+  out (the last run's, history's and proposals'), and the editors'
+  last-run lines say "cost not reported" too (VS Code and JetBrains, next
+  editor release).
+- **A Codex or Cursor session stopped at the turn limit says so**, and to
+  raise `maxTurns`, instead of "ended without finalizing".
+- **`saffron login cursor` on Node below 22.13 names the Node version it
+  needs**, and a vendor SDK missing a part of its own reports that part
+  instead of asking to install the SDK again.
+- **A single locator with options records the element it acted on.**
+  `getByText('Save', { exact: true })`, `getByLabel('Email', { exact:
+  true })` and `getByText(/^Save$/)` recorded nothing, so the click or
+  fill was missing from the recording, and `getByRole('checkbox', {
+  checked: false })` recorded any checkbox. They record as a selector now,
+  as in a chain.
+- **An Outline row's value inside a regex matches the row replaying.**
+  Playwright writes exact text as a regex (`filter({ hasText: /^Garden
+  Queen$/ })`); that value becomes the row's `<param>` as well, and replay
+  writes the next row's value escaped, quotes, slashes and brackets
+  included.
+- **A secret inside a selector or an assertion's pattern is masked where
+  it is written escaped** (a quote in a quoted name, a `.` in a regex), and
+  replay writes it back the same way. A short one next to an escape
+  (`\buat\b`) counts as standing alone.
+- **The recorder reads only the code Playwright ran.** A snapshot or a
+  response body that showed Playwright code (a docs page, a code viewer)
+  was recorded as actions.
+- **Only tools a recording can hold reach the agent**, whatever
+  `PLAYWRIGHT_MCP_CAPS` turns on: an allowlist of the tools that record or
+  only read replaces the list of hidden ones, so coordinate mouse,
+  storage, cookie and route tools stay out.
+- **A heal checks a network assertion against the response that came
+  late.** The failed replay's response log keeps listening through the
+  heal, so a response that arrived just after replay gave up counts.
+- **A cut browser result never splits an emoji**, which made Codex drop
+  the whole result.
+- **`saffron login antigravity` writes through a settings link** (a
+  dotfiles repo, even before the file exists there, through chains and
+  linked folders) and keeps the file's permissions; a link into a
+  read-only place (a Nix store) is left as it is, with the two rules to
+  add named.
+- **The editor keeps each nested project's vocabulary**, built once, in
+  editors that watch its files for it (VS Code, JetBrains), and a changed
+  file refreshes every open project's diagnostics. A project whose build
+  fails keeps its last good one, and coming back to a project checks its
+  documents again. Opening a file it already read (go to definition)
+  rebuilds nothing.
+- **A browser action a Codex, Antigravity or Cursor agent gave up on is
+  still recorded.** Playwright finishes a click or a goto whatever the
+  agent does meanwhile, so the recording keeps what the browser did.
+
+Editors (VS Code extension 0.3.3, JetBrains plugin 0.3.3)
+
+- **A project nested inside the folder the IDE opened.** Both editors
+  now find the nearest `saffron.config.json` above a file and treat that
+  folder as the project: runs start there, status, proposals, `.env` and
+  the step vocabulary come from there, and the project's own `saffron`
+  install is used. JetBrains shows a chooser in the tool window title
+  when the IDE root holds several projects, and adds a Working directory
+  to run configurations. Before, a run from a nested project wrote
+  `.saffron/` into the parent folder with default settings and recorded
+  everything again.
+- **JetBrains: nothing runs in a project you have not trusted.** No
+  status, runs, diffs or language server until the project is trusted;
+  the tool window says so and loads as soon as you trust it. The
+  language server and the Run menu entries appear only inside a Saffron
+  project (a `saffron.config.json`, an installed `saffron-ai`, or
+  `.saffron` files), so a Cucumber or Behat folder of `.feature` files
+  no longer launches `npx -y`. A nested project is left out of the outer
+  project's file list and never run from the outer root.
+- **VS Code on Windows: runs no longer pass through a `.cmd` shim**,
+  which cmd.exe re-parses. The installed CLI runs with node directly;
+  the npx fallback escapes every argument.
+- **JetBrains: reused run configurations no longer keep a Re-record tick
+  from an earlier use.** `.feature` files appear in the Files tab and
+  run from the context menu. A new `login` command takes the provider.
+  Links in the Dashboard open in your browser. The tool window refreshes
+  only for Saffron runs and changes inside the project.
+- **Both editors list proposal files the runner cannot read**, with the
+  reason, and count them as pending. A run with no reported cost shows
+  as not reported, never as $0.
+- **VS Code:** the panel keeps the project you were on when a webview,
+  diff or image takes focus, and Select Project lists nested projects;
+  Run Tagged keeps tags written with parentheses such as `@issue(42)`;
+  stale status after a run is gone; status errors show the
+  error line, not the last stack frame; lines inside docstrings are not
+  read as steps; `Example:` is a scenario keyword; Re-record works with
+  Replay only ticked; `{data:...}` flags an empty list and a header-only
+  CSV; Run Tagged skips tags `--filter` cannot express and says which;
+  diagnostics clear when a file closes or is deleted.
+
+## 0.9.1: Tag expressions: and, or, not
 
 Released 2026-09-29.
 
@@ -68,7 +466,7 @@ Editors (VS Code extension 0.3.2, JetBrains plugin 0.3.2)
   tabs, under any file icon theme that has no icon of its own for them
   (Seti, the default, included).
 
-## 0.9.0
+## 0.9.0: Time-travel replay
 
 Released 2026-09-27.
 
@@ -263,7 +661,7 @@ Editors (VS Code extension 0.3.0, JetBrains plugin 0.3.0)
   what is pending when it runs, skipping UNVERIFIED proposals and
   refusing STALE ones.
 
-## 0.8.5
+## 0.8.5: Proposals bound to what you reviewed
 
 Released 2026-09-24.
 
@@ -302,7 +700,7 @@ Editors (VS Code extension 0.2.10, JetBrains plugin 0.2.5)
 - Both Proposals panels mark a stale proposal STALE, with the reason and
   what to do, and note a proposal filed by an older runner.
 
-## 0.8.4
+## 0.8.4: Heal and replay fixes
 
 Released 2026-09-24.
 
@@ -415,7 +813,7 @@ Editors (VS Code extension 0.2.9)
   files and to the config now refresh every open feature file, including a
   custom data folder and environment overlays.
 
-## 0.8.3
+## 0.8.3: Data references in table cells
 
 Released 2026-09-22.
 
@@ -431,7 +829,7 @@ Runner
   Code currently defaults to, which drifts) and which values it takes, so a
   project can pin its recording model.
 
-## 0.8.2
+## 0.8.2: Split a suite across CI machines
 
 Released 2026-09-22.
 
@@ -454,7 +852,7 @@ Runner
   twice does not count the run twice. Setup and teardown run on each shard
   and receive `SAFFRON_SHARD`. The docs have a GitHub Actions example.
 
-## 0.8.1
+## 0.8.1: Chrome, Edge, and setup and teardown
 
 Released 2026-09-22.
 
@@ -517,7 +915,7 @@ Editors (VS Code extension 0.2.8)
   hover and go-to-definition now follow the runner: the environment's CSV
   replaces the base one, and the hover names the file it read.
 
-## 0.8.0
+## 0.8.0: Test data outside the feature file
 
 Released 2026-09-21.
 
@@ -583,7 +981,7 @@ Editors (VS Code extension 0.2.7, JetBrains plugin 0.2.4)
 - Both Orphans lists show the screenshot folders of scenarios that no longer
   exist, so "Remove All" never deletes something it did not show.
 
-## 0.7.2
+## 0.7.2: Failure screenshots
 
 Released 2026-09-21.
 
@@ -638,7 +1036,7 @@ Editors (JetBrains plugin 0.2.2)
   notification says so when it is missing. The presence check uses no
   plugin-manager API, so it stays clean as that API turns internal.
 
-## 0.7.1
+## 0.7.1: Truthful checks and safer edits
 
 Released 2026-09-20.
 
@@ -709,7 +1107,7 @@ Editors (VS Code extension 0.2.5)
   passes the tree item, not the file path the row click passes; both forms
   are accepted, and the project guard applies to both.
 
-## 0.7.0
+## 0.7.0: saffron diff, saffron prune, and an external review
 
 Released 2026-09-19.
 
@@ -902,7 +1300,7 @@ Editors (JetBrains plugin 0.2.2, VS Code extension 0.2.4)
   longer shell syntax, and a file from a second workspace folder runs
   against that folder's config and install.
 
-## 0.6.0
+## 0.6.0: Multi-tab scenarios
 
 Released 2026-09-18.
 
@@ -924,7 +1322,7 @@ Editors
   its short description fits without being cut off, and the overview
   introduces the tool and how to get started before listing features.
 
-## 0.5.7
+## 0.5.7: Claude Code plugin
 
 Released 2026-09-17.
 
@@ -948,7 +1346,7 @@ Agents
   points at `saffron status`. Run `npx saffron init` again to refresh both
   in a project.
 
-## 0.5.6
+## 0.5.6: Fewer false duplicate wordings
 
 Released 2026-09-17.
 
@@ -959,7 +1357,7 @@ Runner
   duplicate wordings; steps are compared by their quote-generalised
   pattern.
 
-## 0.5.5
+## 0.5.5: Duplicate wordings proven by behaviour
 
 Released 2026-09-17.
 
@@ -971,7 +1369,7 @@ Runner
   "enter X in the username field" against "enter Y in the password
   field", which are different steps.
 
-## 0.5.4
+## 0.5.4: saffron status for the IDE panels
 
 Released 2026-09-17.
 
@@ -991,7 +1389,7 @@ Editors
   Health sections and an in-editor dashboard. All read
   `saffron status --json`.
 
-## 0.5.3
+## 0.5.3: Cost by how you pay, and running from JetBrains
 
 Released 2026-09-17.
 
@@ -1032,7 +1430,7 @@ Editors
   extension, the last run's totals with the report one click away, and
   the proposals pending review with Accept all.
 
-## 0.5.2
+## 0.5.2: Scenario Outlines record correctly
 
 Released 2026-09-15.
 
@@ -1061,7 +1459,7 @@ Editors
   hover says where it is defined and never shows the value. In the VS
   Code extension and in `saffron lsp` for JetBrains and other editors.
 
-## 0.5.1
+## 0.5.1: The example suite in .saffron files
 
 Released 2026-09-14.
 
@@ -1078,7 +1476,7 @@ Editors
   parameters instead of the whole step line. Ships in the VS Code
   extension, the JetBrains plugin and the package's TextMate bundle.
 
-## 0.5.0
+## 0.5.0: Guided first run
 
 Released 2026-09-14.
 
@@ -1091,7 +1489,7 @@ Runner
   matching `saffron.config.json` with `retries: 1`. Only installs into an
   empty `features/` directory. Documented as "Your first run".
 
-## 0.4.2
+## 0.4.2: Recover from a wrong recording
 
 Released 2026-09-13.
 
@@ -1123,7 +1521,7 @@ Docs and site
 - Assertion policy documented on the Features page; cache lifecycle gained
   the staleness and wrong-recording stages.
 
-## 0.4.1
+## 0.4.1: JetBrains plugin
 
 Released 2026-09-13.
 
@@ -1145,7 +1543,7 @@ Editors
 - VS Code extension 0.1.3: plain punctuation in README, hover and
   diagnostic messages.
 
-## 0.4.0
+## 0.4.0: Agent skill for AI assistants
 
 Released 2026-09-13.
 
@@ -1171,13 +1569,13 @@ Editors
 - VS Code extension 0.1.2: warning and quick fix when a set name is written
   without the `StepSet` keyword.
 
-## 0.3.1
+## 0.3.1: Version fix
 
 Released 2026-08-15.
 
 - `saffron --version` no longer reports a hardcoded value.
 
-## 0.3.0
+## 0.3.0: Network-aware steps
 
 Released 2026-08-12.
 
@@ -1199,7 +1597,7 @@ Editors
 
 - VS Code extension 0.1.0 published to the Marketplace.
 
-## 0.2.0
+## 0.2.0: Secrets, cross-browser and parallel replay
 
 Released 2026-07-19.
 
@@ -1215,7 +1613,7 @@ Runner
   workers (`--workers N`), and a cheaper model for heal sessions
   (`--heal-model`).
 
-## 0.1.0
+## 0.1.0: First public release
 
 Released 2026-07-10.