saffron-ai 0.7.2 → 0.8.0

package/CHANGELOG.md

@@ -4,6 +4,60 @@ 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.
 
+## 0.8.0
+
+Released 2026-09-21.
+
+Test data moves out of the feature file: a `data/` folder, `{data:...}`
+references, list checks, `Examples` from a file, values unique per run, and
+data per environment.
+
+Runner
+
+- **Test data outside the feature file: `{data:file.key}`.** Put values in
+  JSON files under `data/` and reference them from a step, a table cell or
+  a doc string: `When I sign in as {data:users.admin.email}`. Same family
+  as `{env:VAR}`: the recording stores the token and replay reads the file,
+  so changing a value changes the next replay at zero tokens. A recording
+  that still spells out the old value goes stale instead of replaying
+  yesterday's data, and a missing file or key stops the run by name before
+  a browser opens. New config key `dataDir` (default `data`). Not for
+  secrets: data files are committed.
+- **Check a whole list in one step.** `Then the status filter should list
+  every {data:enums.OrderStatus}` records ONE assertion (`expectEach`) that
+  names the list and its container. Replay reads the list from the file, so
+  a value added to the data is checked on the next run at zero tokens, and
+  a missing one fails by name with how many were found. Values match as
+  whole text ("Paid" is not "Unpaid"), extra entries such as "All" are
+  allowed, and a closed dropdown works.
+- **`Examples` from a file**, in `.saffron` files: `Examples: {data:roles}`
+  reads `data/roles.csv` (header row = placeholders) or a JSON list of
+  records. One recording, one zero-token replay per row; a row added to the
+  file records nothing. A placeholder without a column, a missing file and a
+  `.feature` file using it are each parse errors that say what to do.
+- **`{unique:name}`**: a value that is new on every run and the same within
+  one, for scenarios that create things. The agent types the generated
+  value while recording and Saffron turns it back into the token; a run that
+  is not green lists what each token stood for. `{unique:name:digits}` for
+  numeric fields.
+- **Data per environment**: `--env staging` (or `SAFFRON_ENV`, or `env` in
+  the config) lays `data/users.staging.json` over `data/users.json`, key by
+  key. The reference in the step stays the same on every target.
+- `saffron status --json` gains `data`: the folder, the environment, the
+  files, and references that do not resolve. `saffron lsp` completes
+  `{data:` paths, shows values on hover, jumps to the key and flags
+  unresolved references. The bundled grammar highlights `{data:...}` and
+  `{unique:...}`. `saffron init --examples` installs `data/catalog.json` and
+  a scenario that uses it, and the agent skill, its syntax reference and the
+  AGENTS.md block teach the new syntax.
+
+- **`saffron prune` covers failure screenshots.** A deleted scenario also
+  leaves its screenshot folder behind under `.saffron/artifacts/`. Prune
+  lists those folders with the caches and proposals and removes them with
+  `--yes`; a live scenario's folder is kept, per Examples row. `saffron
+  status --json` reports them as orphans of kind `artifact`, and both IDE
+  panels (VS Code 0.2.6, JetBrains 0.2.3) show them.
+
 ## 0.7.2
 
 Released 2026-09-21.
@@ -34,6 +88,13 @@ Runner
 
 Editors (VS Code extension 0.2.6, JetBrains plugin 0.2.3)
 
+- **`{data:...}` in the editor.** VS Code completes data files and keys with
+  their values, shows the current value (or a list's values, or an Examples
+  file's columns) on hover, jumps to the key, and underlines a reference
+  that does not resolve, reading the same files and environment overlay the
+  runner does. JetBrains gets the same through `saffron lsp`. Both highlight
+  `{data:...}` and `{unique:...}` like `{env:VAR}`, including on an
+  `Examples:` line.
 - **Last run, with the screenshot one click away.** Both IDEs list what the
   last run left to look at: failed scenarios, then healed ones, with the
   step that failed. VS Code opens the screenshot in its image preview on

package/README.md

@@ -89,6 +89,7 @@ Configuration lives in `saffron.config.json` at your project root:
 {
   "baseURL": "http://localhost:4173",
   "features": "features",
+  "dataDir": "data",
   "actionTimeoutMs": 5000,
   "pollIntervalMs": 100,
   "retries": 1,