@crvouga/atlas 0.2.0 → 0.4.0

package/dist/reports/src/report-types.d.ts

@@ -18,8 +18,12 @@ export type ReportPerformanceOptions = {
     /** Diagnostic threshold, not a portable CPU or paint-time assertion. */
     readonly slowStepMs: number;
 };
-/** How a captured value is encoded on disk and rendered in the report. */
-export type SnapshotMedia = 'json' | 'html' | 'png' | 'text' | 'bytes';
+/**
+ * How a captured value is encoded on disk and rendered in the report.
+ * `png` is a still, `html` is a page snapshot, and `video` is an mp4 of the moment or the whole test.
+ * A runner may record any mix. The viewer treats a still, a video, and a timeline of frames as the same kind of evidence.
+ */
+export type SnapshotMedia = 'json' | 'html' | 'png' | 'text' | 'bytes' | 'video';
 export type ReportStepStatus = 'passed' | 'failed';
 /** Test outcome after the harness (e.g. the test runner) has weighed in. */
 export type ReportTestStatus = 'passed' | 'failed' | 'skipped';
@@ -102,10 +106,23 @@ export type RunReportMeta = {
     readonly error?: string;
     readonly errorStack?: string;
 };
+/**
+ * A file attached to the whole test. A runner that can capture each step puts stills and page
+ * snapshots on `steps[].frames` instead, and the viewer builds a timeline from those. This list
+ * is for what the runner can attach when it cannot: a video of the test, a few screenshots, a log.
+ */
+export type ReportArtifact = {
+    readonly name: string;
+    readonly media: SnapshotMedia;
+    readonly file: string;
+    readonly poster?: string;
+    readonly captions?: string;
+};
 /** In-memory / persisted timeline for one test run. */
 export type RunReport = {
     readonly meta: RunReportMeta;
     readonly steps: readonly ReportStep[];
+    readonly artifacts?: readonly ReportArtifact[];
 };
 export type SuiteTestSummary = {
     readonly testId: string;

package/dist/reports/src/source-entries.js

@@ -1,15 +1,7 @@
 import { testFrameKey } from './recording-keys.js';
+import { capturedFiles } from './frames.js';
 import { remoteTestFileKey, remoteTestReportKey } from './keys.js';
 const JSON_TYPE = 'application/json; charset=utf-8';
-function frameFiles(steps, out) {
-    for (const step of steps) {
-        for (const frame of step.frames) {
-            for (const blob of frame.snapshots)
-                out.add(blob.file);
-        }
-        frameFiles(step.steps, out);
-    }
-}
 export async function* sourceEntries(args, source, tests, runId) {
     for (const { report } of [...tests].sort((a, b) => a.report.meta.testId < b.report.meta.testId ? -1 : 1)) {
         const { testId } = report.meta;
@@ -18,9 +10,7 @@ export async function* sourceEntries(args, source, tests, runId) {
             bytes: new TextEncoder().encode(JSON.stringify(report)),
             contentType: JSON_TYPE,
         };
-        const files = new Set();
-        frameFiles(report.steps, files);
-        for (const file of [...files].sort()) {
+        for (const file of capturedFiles(report).sort()) {
             const obj = await args.local.get(testFrameKey(runId, testId, file));
             if (obj === null)
                 throw new Error(`Missing report snapshot: ${file}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crvouga/atlas",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "Atlas: executable statecharts. Spec a product's flows as statecharts, run them against the real app with any driver, and browse what happened.",
   "license": "MIT",
   "type": "module",
@@ -107,7 +107,7 @@
     "test": "bun test && bun test --cwd packages/visualizer --preload ./tests/preload.ts tests",
     "type-check": "for dir in packages/* scripts examples/todo; do tsc --noEmit -p \"$dir\" || exit 1; done",
     "schemas": "bun packages/schema/scripts/emit-json-schemas.ts",
-    "viz:dev": "cd packages/visualizer && INIT_CWD=\"$OLDPWD\" bun --bun vite --configLoader runner",
+    "viz:dev": "bun packages/visualizer/bin/atlas-visualizer.mjs dev --specs \"$(pwd)/packages/visualizer/fixtures/full/specs\" --runs \"$(pwd)/packages/visualizer/fixtures/full/runs\"",
     "viz:build": "cd packages/visualizer && INIT_CWD=\"$OLDPWD\" bun --bun vite build --configLoader runner",
     "viz:publish-data": "bun packages/visualizer/scripts/publish-data.ts",
     "viz:fixtures": "bun packages/visualizer/scripts/make-fixtures.ts",
@@ -115,11 +115,11 @@
     "example:lint": "bun --cwd examples/todo ../../packages/core/bin/atlas.mjs lint --require-implementations",
     "example:plan": "bun --cwd examples/todo ../../packages/core/bin/atlas.mjs plan",
     "example:fast": "bun --cwd examples/todo ../../packages/core/bin/atlas.mjs run --mode fast",
-    "example:run": "bun --cwd examples/todo ../../packages/core/bin/atlas.mjs run --mode showcase",
+    "example:run": "bun examples/todo/run-all.ts",
     "example:clients": "bun --cwd examples/todo ../../packages/core/bin/atlas.mjs run --config clients/atlas.config.ts --mode showcase",
     "example:clients:bun": "ATLAS_DESKTOP=bun bun --cwd examples/todo ../../packages/core/bin/atlas.mjs run --config clients/atlas.config.ts --mode showcase",
     "atlas:run": "status=0; bun run example:clients || status=$?; bun run example:run || status=$?; exit $status",
-    "atlas:viz": "bun packages/visualizer/bin/atlas-visualizer.mjs dev --specs examples/todo/specs --runs examples/todo/atlas-runs",
+    "atlas:viz": "ATLAS_REPORTS_MODULE=\"$(pwd)/examples/todo/reports-dev.ts\" bun packages/visualizer/bin/atlas-visualizer.mjs dev --specs examples/todo/specs --runs examples/todo/atlas-runs",
     "release:plan": "bun scripts/release/plan.ts",
     "release:publish": "bun scripts/release/publish.ts",
     "release:smoke": "bun scripts/release/consumer-smoke.ts",
@@ -171,6 +171,7 @@
   "devDependencies": {
     "@commitlint/cli": "19.8.1",
     "@commitlint/config-conventional": "19.8.1",
+    "@informalsystems/quint": "^0.33.0",
     "@types/bun": "1.4.3",
     "@types/node": "^22.20.3",
     "@types/react": "19.2.7",

package/packages/reports/README.md

@@ -10,11 +10,11 @@ The Atlas visualizer shows each kind of spec in its own tab, with every spec's r
 
 ## Combining evidence
 
-Current specs define the outline. `combineEvidence` fills it with the newest completed result for each producer, check and parameter set, across backends, branches and commits. Equal-time conflicts favor failure. Unfinished runs do not erase completed outcomes. Missing specs stay visible and removed specs retain their evidence outside the outline. `evidenceView` groups those results by check: the outcomes, the recorded timings that qualify them, and a summary per spec. A timing over its allowance never fails a check. `checkHistory` returns every layer's own record of one check, so a superseded result stays readable. Leaving a backend, a branch or one layer out (`contributes`) is how earlier outcomes are inspected.
+Current specs define the outline. A layer is one focused recording: the checks it actually ran, on one environment, from one version and branch, in one store. `combineEvidence` fills the outline from every layer. The newest completed result wins only its own producer, check, environment and parameter set. Desktop web, mobile web, iOS and Android of the same check all stay visible, and any other recorded environment does too. A layer that ran one scenario leaves every other scenario as the newest layer that did run it, so the report fills without one suite that runs everything. Equal-time conflicts favor failure. Unfinished runs do not erase completed outcomes. Missing specs stay visible and removed specs retain their evidence outside the outline. `evidenceView` groups those results by check: the outcomes, the recorded timings that qualify them, and a summary per spec. A timing over its allowance never fails a check. `checkHistory` returns every layer's own record of one check, so a superseded result stays readable. Leaving a backend, an environment, a branch, a version or one layer out (`contributes`) is how earlier outcomes are inspected.
 
 ## Backends
 
-`createReportsApp` combines layers from several stores. `localStore` is the backend `local` ("This machine"), `store` is `shared` ("Shared reports"), and `backends` adds any number of further named stores, such as another team's bucket or a device lab. Every layer says which backend it came from. An unavailable backend is named in the page's notices and leaves the others usable; `GET /evidence?retry=1` asks it again without waiting.
+`createReportsApp` combines layers from several stores. `localStore` is the backend `local` ("This machine"), `store` is `shared` ("Shared reports"), and `backends` adds any number of further named stores. A backend is any `ObjectStore`: the local disk, a shared bucket, S3, or a device lab. Every layer says which backend, version, branch and environment it came from. An unavailable backend is named in the page's notices and leaves the others usable; `GET /evidence?retry=1` asks it again without waiting.
 
 | Route | Returns |
 | --- | --- |
@@ -40,6 +40,8 @@ Freshness warnings preserve the recorded outcome. Changed spec fingerprints or r
 
 Configure `ATLAS_REPORTS_MODULE` with a host composition module exporting `reportsDevFetch(request, repoRoot)`. Atlas's Vite middleware serves it at `/api/reports`, alongside specs and chart runs. `INIT_CWD` identifies the consuming repository. Credentials stay in that server module.
 
+When that module is unset and the open specs are the coffee example or the todo example, the visualizer dev server serves an in-memory layered report for those documents instead. Any other spec set is left alone. The todo example's own module serves that same layered report and adds the desktop web layer `example:run` writes.
+
 For a separately hosted reports API, set `VITE_ATLAS_REPORTS_URL` when building the visualizer. Otherwise a built site reads `data/evidence/`, populated with `exportEvidence`. Atlas still browses specs if evidence is absent.
 
 ## Verification

package/packages/reports/STORAGE.md

@@ -7,7 +7,7 @@ storage and time ports from its caller.
 
 `layers/index/<inverted-time>-<digest>.json` discovers immutable manifests at `layers/manifests/<digest>.json`. Each records producer, origin, parameters, checks, spec fingerprints and a recording bundle. The manifest is written after its blobs and the index last. Distinct results at the same timestamp retain separate identities. Compressed blobs under `layers/blobs/` are addressed by content and reused across runs; ordinary source publication shares its bundle directly with its layer without recompressing snapshots.
 
-Git commits are provenance and exact historical recording addresses, never a report partition. `combineEvidence` chooses completed results per check and parameters, retaining gaps from older layers. `publishSource` accepts `parameters`, and standalone parts may include them too. Inventory must be published before results for fingerprint comparison to be available.
+Git commits are provenance and exact historical recording addresses, never a report partition. `combineEvidence` chooses the newest completed result per check, environment and parameters, and keeps every other cell. An environment is the client that was checked (`desktop-web`, `mobile-web`, `ios`, `android`, or any other recorded name). The same check on two environments contributes twice. A layer that checks one scenario fills only that scenario. `publishSource` accepts `environment` and `parameters`, and a part may name its environment in `parameters.environment`. Inventory must be published before results for fingerprint comparison to be available.
 
 ## Commit inventory
 

package/packages/visualizer/README.md

@@ -11,7 +11,9 @@ reads two independent sources and works with whatever exists:
 
 The explorer is one header, an open index and one plate. The index lists every place and journey of
 the product; each kind of spec (Gherkin, Quint, DMN, Alloy, OpenSLO) has its own tab, with the
-recorded result of every spec in its index. Local directories, published HTTP files and HTTP APIs
+recorded result of every spec in its index. The header finds a flow in ordinary language across
+charts, specs and recorded runs. ⌘K (Ctrl+K on other keyboards) opens it, and `/` does the same
+when you are not already typing. Local directories, published HTTP files and HTTP APIs
 can supply reports simultaneously. Reports update through file watching, polling or server events.
 Latest includes running reports; one unavailable backend leaves the others usable.
 
@@ -36,8 +38,8 @@ atlas-visualizer dev --specs ./specs --runs ./atlas-runs
 | `--port <n>`, `--host <host>` | `dev`: where to listen (default `localhost:5180`, or the next free port).                   |
 
 Relative paths resolve against the directory the command was run from. Without flags the
-environment is read: `ATLAS_SPECS_ROOT`, `ATLAS_RUNS_ROOT` (relative to `INIT_CWD` when your package
-manager sets it to where you ran the command, or the current directory) and `ATLAS_FIXTURE`. With nothing configured and no
+environment is read: `ATLAS_SPECS_ROOT` and `ATLAS_RUNS_ROOT` (relative to `INIT_CWD` when your package
+manager sets it to where you ran the command, or the current directory). With nothing configured and no
 `specs/` directory, the `full` example is shown.
 
 Editing a spec file or a run publishing a snapshot updates the open page in about a second, without a reload,
@@ -60,8 +62,7 @@ sets how often the site checks for new runs (default 60 s, plus when the tab reg
 ### Inside this repository
 
 ```sh
-bun run viz:dev                          # ATLAS_SPECS_ROOT / ATLAS_RUNS_ROOT, or the example
-ATLAS_FIXTURE=partial bun run viz:dev    # one of the fixtures
+bun run viz:dev                          # the full coffee example, charts and layered report
 bun test packages/visualizer/src packages/visualizer/vite   # parsing, composition, statuses, every fixture
 bun run viz:fixtures                     # regenerate the fixtures (needs ImageMagick, cwebp, ffmpeg)
 ```
@@ -147,7 +148,9 @@ MIT
 
 Beside the statechart map, every other kind of spec has its own tab: Gherkin features, Quint models, DMN decision tables, Alloy structures and OpenSLO objectives. A tab appears when the specs folder has files of its kind. The index lists every spec with what was recorded for it, and filters to those with results, those failing, or those with none. A spec page shows each scenario, trace or check with its outcome; opening one shows the recorded steps, the error, the timings, every other run of the same check, and its recording.
 
-Results come from the Atlas reports API (`/api/reports` in dev, `VITE_ATLAS_REPORTS_URL` when hosted elsewhere) or from a static `data/evidence` export. They combine across backends, branches and runs; **Sources** in the header switches any of them off. While a spec suite is running, the header says so and each finished test appears within a couple of seconds. See [Atlas reports](../reports/README.md) for the API and host configuration.
+Results come from the Atlas reports API (`/api/reports` in dev, `VITE_ATLAS_REPORTS_URL` when hosted elsewhere) or from a static `data/evidence` export. They combine across backends, branches, versions, environments and layers; **Sources** in the header switches any of them off. While a spec suite is running, the header says so and each finished test appears within a couple of seconds. See [Atlas reports](../reports/README.md) for the API and host configuration.
+
+The coffee example ships those documents and a layered report. `bun run viz:dev` opens that full example, and the same report is the fallback when a working directory has no `specs/` and `ATLAS_REPORTS_MODULE` is unset. `atlas:viz` serves the same kind of report for the todo example, and adds the desktop web layer `example:run` writes. Each built-in report is five layers: an older desktop web run, a mobile web branch, Android from a device lab, a focused iOS run, and a newer desktop web run that repeated one scenario. The same check stays visible on each environment. A feature with no layer stays empty.
 
 The header title is the product's name, taken from `atlas.yaml`'s `title` up to its first dash or colon, or "Atlas".
 

package/packages/visualizer/example/specs/coffee/ordering/cart.qnt

@@ -0,0 +1,7 @@
+# Cart
+module cart {
+  var items: int
+  var paid: bool
+  action add = items' = items + 1
+  action pay = paid' = true
+}

package/packages/visualizer/example/specs/coffee/ordering/checkout.openslo.yaml

@@ -0,0 +1,10 @@
+# Checkout latency
+apiVersion: openslo/v1
+kind: SLO
+metadata:
+  name: checkout-latency
+spec:
+  description: Checkout answers within a second.
+  objectives:
+    - displayName: Checkout latency
+      target: 0.99

package/packages/visualizer/example/specs/coffee/ordering/drink-price.dmn

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<definitions xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/">
+  <decision id="drink-price" name="Drink price">
+    <decisionTable id="Drink price" hitPolicy="UNIQUE">
+      <input label="Size">
+        <inputExpression typeRef="string"><text>size</text></inputExpression>
+      </input>
+      <input label="Milk">
+        <inputExpression typeRef="string"><text>milk</text></inputExpression>
+      </input>
+      <output label="Price" name="price" />
+      <rule>
+        <inputEntry><text>"Small"</text></inputEntry>
+        <inputEntry><text>"None"</text></inputEntry>
+        <outputEntry><text>3</text></outputEntry>
+      </rule>
+      <rule>
+        <inputEntry><text>"Large"</text></inputEntry>
+        <inputEntry><text>"Oat"</text></inputEntry>
+        <outputEntry><text>5</text></outputEntry>
+      </rule>
+    </decisionTable>
+  </decision>
+</definitions>

package/packages/visualizer/example/specs/coffee/ordering/loyalty.feature

@@ -0,0 +1,7 @@
+Feature: Loyalty stamps
+  A regular earns a free drink. No layer has recorded this yet.
+
+  Scenario: Tenth drink is free
+    Given nine stamps
+    When the customer orders
+    Then the drink is free

package/packages/visualizer/example/specs/coffee/ordering/ordering.feature

@@ -0,0 +1,36 @@
+Feature: Order a drink
+  A customer picks a drink, pays, and picks it up.
+
+  Rule: Paying for the order
+
+    Scenario: Pays by card
+      Given a drink in the cart
+      When the customer pays by card
+      Then the barista can start the drink
+
+    Scenario: Pays with a wallet
+      Given a drink in the cart
+      When the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Card declined, then a wallet works
+      Given a drink in the cart
+      When the card is declined
+      And the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Slow payment
+      Given a drink in the cart
+      When the payment takes longer than a minute
+      Then the customer can check the payment again
+
+    Scenario: Leaves checkout and comes back
+      Given a drink in the cart
+      When the customer closes checkout
+      And the customer starts checkout again
+      Then checkout is open
+
+    Scenario: Drink left too long
+      Given a finished drink
+      When nobody picks it up
+      Then the drink is thrown away and refunded

package/packages/visualizer/example/specs/coffee/ordering/payment.als

@@ -0,0 +1,4 @@
+// An order is paid once.
+sig Order { paid: lone Payment }
+sig Payment {}
+fact { all o: Order | one o.paid }

package/packages/visualizer/fixtures/failures/specs/coffee/ordering/cart.qnt

@@ -0,0 +1,7 @@
+# Cart
+module cart {
+  var items: int
+  var paid: bool
+  action add = items' = items + 1
+  action pay = paid' = true
+}

package/packages/visualizer/fixtures/failures/specs/coffee/ordering/checkout.openslo.yaml

@@ -0,0 +1,10 @@
+# Checkout latency
+apiVersion: openslo/v1
+kind: SLO
+metadata:
+  name: checkout-latency
+spec:
+  description: Checkout answers within a second.
+  objectives:
+    - displayName: Checkout latency
+      target: 0.99

package/packages/visualizer/fixtures/failures/specs/coffee/ordering/drink-price.dmn

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<definitions xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/">
+  <decision id="drink-price" name="Drink price">
+    <decisionTable id="Drink price" hitPolicy="UNIQUE">
+      <input label="Size">
+        <inputExpression typeRef="string"><text>size</text></inputExpression>
+      </input>
+      <input label="Milk">
+        <inputExpression typeRef="string"><text>milk</text></inputExpression>
+      </input>
+      <output label="Price" name="price" />
+      <rule>
+        <inputEntry><text>"Small"</text></inputEntry>
+        <inputEntry><text>"None"</text></inputEntry>
+        <outputEntry><text>3</text></outputEntry>
+      </rule>
+      <rule>
+        <inputEntry><text>"Large"</text></inputEntry>
+        <inputEntry><text>"Oat"</text></inputEntry>
+        <outputEntry><text>5</text></outputEntry>
+      </rule>
+    </decisionTable>
+  </decision>
+</definitions>

package/packages/visualizer/fixtures/failures/specs/coffee/ordering/loyalty.feature

@@ -0,0 +1,7 @@
+Feature: Loyalty stamps
+  A regular earns a free drink. No layer has recorded this yet.
+
+  Scenario: Tenth drink is free
+    Given nine stamps
+    When the customer orders
+    Then the drink is free

package/packages/visualizer/fixtures/failures/specs/coffee/ordering/ordering.feature

@@ -0,0 +1,36 @@
+Feature: Order a drink
+  A customer picks a drink, pays, and picks it up.
+
+  Rule: Paying for the order
+
+    Scenario: Pays by card
+      Given a drink in the cart
+      When the customer pays by card
+      Then the barista can start the drink
+
+    Scenario: Pays with a wallet
+      Given a drink in the cart
+      When the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Card declined, then a wallet works
+      Given a drink in the cart
+      When the card is declined
+      And the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Slow payment
+      Given a drink in the cart
+      When the payment takes longer than a minute
+      Then the customer can check the payment again
+
+    Scenario: Leaves checkout and comes back
+      Given a drink in the cart
+      When the customer closes checkout
+      And the customer starts checkout again
+      Then checkout is open
+
+    Scenario: Drink left too long
+      Given a finished drink
+      When nobody picks it up
+      Then the drink is thrown away and refunded

package/packages/visualizer/fixtures/failures/specs/coffee/ordering/payment.als

@@ -0,0 +1,4 @@
+// An order is paid once.
+sig Order { paid: lone Payment }
+sig Payment {}
+fact { all o: Order | one o.paid }

package/packages/visualizer/fixtures/full/specs/coffee/ordering/cart.qnt

@@ -0,0 +1,7 @@
+# Cart
+module cart {
+  var items: int
+  var paid: bool
+  action add = items' = items + 1
+  action pay = paid' = true
+}

package/packages/visualizer/fixtures/full/specs/coffee/ordering/checkout.openslo.yaml

@@ -0,0 +1,10 @@
+# Checkout latency
+apiVersion: openslo/v1
+kind: SLO
+metadata:
+  name: checkout-latency
+spec:
+  description: Checkout answers within a second.
+  objectives:
+    - displayName: Checkout latency
+      target: 0.99

package/packages/visualizer/fixtures/full/specs/coffee/ordering/drink-price.dmn

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<definitions xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/">
+  <decision id="drink-price" name="Drink price">
+    <decisionTable id="Drink price" hitPolicy="UNIQUE">
+      <input label="Size">
+        <inputExpression typeRef="string"><text>size</text></inputExpression>
+      </input>
+      <input label="Milk">
+        <inputExpression typeRef="string"><text>milk</text></inputExpression>
+      </input>
+      <output label="Price" name="price" />
+      <rule>
+        <inputEntry><text>"Small"</text></inputEntry>
+        <inputEntry><text>"None"</text></inputEntry>
+        <outputEntry><text>3</text></outputEntry>
+      </rule>
+      <rule>
+        <inputEntry><text>"Large"</text></inputEntry>
+        <inputEntry><text>"Oat"</text></inputEntry>
+        <outputEntry><text>5</text></outputEntry>
+      </rule>
+    </decisionTable>
+  </decision>
+</definitions>

package/packages/visualizer/fixtures/full/specs/coffee/ordering/loyalty.feature

@@ -0,0 +1,7 @@
+Feature: Loyalty stamps
+  A regular earns a free drink. No layer has recorded this yet.
+
+  Scenario: Tenth drink is free
+    Given nine stamps
+    When the customer orders
+    Then the drink is free

package/packages/visualizer/fixtures/full/specs/coffee/ordering/ordering.feature

@@ -0,0 +1,36 @@
+Feature: Order a drink
+  A customer picks a drink, pays, and picks it up.
+
+  Rule: Paying for the order
+
+    Scenario: Pays by card
+      Given a drink in the cart
+      When the customer pays by card
+      Then the barista can start the drink
+
+    Scenario: Pays with a wallet
+      Given a drink in the cart
+      When the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Card declined, then a wallet works
+      Given a drink in the cart
+      When the card is declined
+      And the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Slow payment
+      Given a drink in the cart
+      When the payment takes longer than a minute
+      Then the customer can check the payment again
+
+    Scenario: Leaves checkout and comes back
+      Given a drink in the cart
+      When the customer closes checkout
+      And the customer starts checkout again
+      Then checkout is open
+
+    Scenario: Drink left too long
+      Given a finished drink
+      When nobody picks it up
+      Then the drink is thrown away and refunded

package/packages/visualizer/fixtures/full/specs/coffee/ordering/payment.als

@@ -0,0 +1,4 @@
+// An order is paid once.
+sig Order { paid: lone Payment }
+sig Payment {}
+fact { all o: Order | one o.paid }

package/packages/visualizer/fixtures/malformed/specs/coffee/ordering/cart.qnt

@@ -0,0 +1,7 @@
+# Cart
+module cart {
+  var items: int
+  var paid: bool
+  action add = items' = items + 1
+  action pay = paid' = true
+}

package/packages/visualizer/fixtures/malformed/specs/coffee/ordering/checkout.openslo.yaml

@@ -0,0 +1,10 @@
+# Checkout latency
+apiVersion: openslo/v1
+kind: SLO
+metadata:
+  name: checkout-latency
+spec:
+  description: Checkout answers within a second.
+  objectives:
+    - displayName: Checkout latency
+      target: 0.99

package/packages/visualizer/fixtures/malformed/specs/coffee/ordering/drink-price.dmn

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<definitions xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/">
+  <decision id="drink-price" name="Drink price">
+    <decisionTable id="Drink price" hitPolicy="UNIQUE">
+      <input label="Size">
+        <inputExpression typeRef="string"><text>size</text></inputExpression>
+      </input>
+      <input label="Milk">
+        <inputExpression typeRef="string"><text>milk</text></inputExpression>
+      </input>
+      <output label="Price" name="price" />
+      <rule>
+        <inputEntry><text>"Small"</text></inputEntry>
+        <inputEntry><text>"None"</text></inputEntry>
+        <outputEntry><text>3</text></outputEntry>
+      </rule>
+      <rule>
+        <inputEntry><text>"Large"</text></inputEntry>
+        <inputEntry><text>"Oat"</text></inputEntry>
+        <outputEntry><text>5</text></outputEntry>
+      </rule>
+    </decisionTable>
+  </decision>
+</definitions>

package/packages/visualizer/fixtures/malformed/specs/coffee/ordering/loyalty.feature

@@ -0,0 +1,7 @@
+Feature: Loyalty stamps
+  A regular earns a free drink. No layer has recorded this yet.
+
+  Scenario: Tenth drink is free
+    Given nine stamps
+    When the customer orders
+    Then the drink is free

package/packages/visualizer/fixtures/malformed/specs/coffee/ordering/ordering.feature

@@ -0,0 +1,36 @@
+Feature: Order a drink
+  A customer picks a drink, pays, and picks it up.
+
+  Rule: Paying for the order
+
+    Scenario: Pays by card
+      Given a drink in the cart
+      When the customer pays by card
+      Then the barista can start the drink
+
+    Scenario: Pays with a wallet
+      Given a drink in the cart
+      When the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Card declined, then a wallet works
+      Given a drink in the cart
+      When the card is declined
+      And the customer pays with a wallet
+      Then the order is paid
+
+    Scenario: Slow payment
+      Given a drink in the cart
+      When the payment takes longer than a minute
+      Then the customer can check the payment again
+
+    Scenario: Leaves checkout and comes back
+      Given a drink in the cart
+      When the customer closes checkout
+      And the customer starts checkout again
+      Then checkout is open
+
+    Scenario: Drink left too long
+      Given a finished drink
+      When nobody picks it up
+      Then the drink is thrown away and refunded

package/packages/visualizer/fixtures/malformed/specs/coffee/ordering/payment.als

@@ -0,0 +1,4 @@
+// An order is paid once.
+sig Order { paid: lone Payment }
+sig Payment {}
+fact { all o: Order | one o.paid }

package/packages/visualizer/fixtures/partial/specs/coffee/ordering/cart.qnt

@@ -0,0 +1,7 @@
+# Cart
+module cart {
+  var items: int
+  var paid: bool
+  action add = items' = items + 1
+  action pay = paid' = true
+}

package/packages/visualizer/fixtures/partial/specs/coffee/ordering/checkout.openslo.yaml

@@ -0,0 +1,10 @@
+# Checkout latency
+apiVersion: openslo/v1
+kind: SLO
+metadata:
+  name: checkout-latency
+spec:
+  description: Checkout answers within a second.
+  objectives:
+    - displayName: Checkout latency
+      target: 0.99

package/packages/visualizer/fixtures/partial/specs/coffee/ordering/drink-price.dmn

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<definitions xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/">
+  <decision id="drink-price" name="Drink price">
+    <decisionTable id="Drink price" hitPolicy="UNIQUE">
+      <input label="Size">
+        <inputExpression typeRef="string"><text>size</text></inputExpression>
+      </input>
+      <input label="Milk">
+        <inputExpression typeRef="string"><text>milk</text></inputExpression>
+      </input>
+      <output label="Price" name="price" />
+      <rule>
+        <inputEntry><text>"Small"</text></inputEntry>
+        <inputEntry><text>"None"</text></inputEntry>
+        <outputEntry><text>3</text></outputEntry>
+      </rule>
+      <rule>
+        <inputEntry><text>"Large"</text></inputEntry>
+        <inputEntry><text>"Oat"</text></inputEntry>
+        <outputEntry><text>5</text></outputEntry>
+      </rule>
+    </decisionTable>
+  </decision>
+</definitions>