Verifiers

The v1 verifier vocabulary is screen, region, cell, cursor, process, snapshot, trusted command, file, script, count, link, and the process-telemetry metrics verifier (see Process Telemetry and glyph docs process-telemetry --format md).

Examples:

yaml

outcomes:
  - id: welcome_visible
    verify:
      screen:
        contains: "Welcome"
  - id: ready_exact
    verify:
      screen:
        equals: "ready\n"
  - id: ready_pattern
    verify:
      screen:
        matches: "^Welcome \\d+"
  - id: clean_exit
    verify:
      process:
        exitCode: 0
  - id: cursor_hidden
    verify:
      cursor:
        visible: false
  - id: title_is_bold
    verify:
      cell:
        x: 2
        y: 1
        char: "W"
        style:
          bold: true
  - id: binary_exists
    verify:
      command:
        run: "test -x ./bin/app"

Screen and region verifiers accept exactly one of: equals, contains, notContains, matches (preferred regex form), or legacy regex (alias of matches). Cell verifiers can check characters and style attributes such as foreground color, background color, bold, dim, italic, underline, and reverse.

Color values use a canonical form so style: { fg, bg } assertions are stable across SGR encodings:

the 16 base colors are named: black, red, green, yellow, blue, magenta, cyan, white, and their bright-prefixed variants (e.g. brightred). SGR 31 and 38;5;1 both read as red.
256-palette colors 16–255 are their decimal index as a string (e.g. "201").
truecolor (38;2;r;g;b) is lowercase hex (e.g. "#ff8800").

The same values drive the colors in the rendered screens/final.svg screenshot.

Outcomes can set their own timeoutMs and normalize block when a single assertion needs different polling or text cleanup than the rest of the spec:

yaml

outcomes:
  - id: stable_build_id
    description: volatile build ids are normalized for this assertion
    timeoutMs: 10000
    normalize:
      replace:
        - regex: "build-[0-9]+"
          with: "build-<id>"
    verify:
      screen:
        contains: "build-<id>"

Use trusted command verifiers only for local checks you would be comfortable running from a shell script.

The file, script, and count verifiers extend assertions beyond the screen:

file polls the filesystem for a glob match (filename wildcards supported, directory portion literal) and optionally requires the matched file's body to contain a needle.
script runs an external node or shell script that returns a JSON { ok, evidence } body; the evidence is written to outcomes/<id>.raw.json (on both pass and failure).
count asserts how many cells on the screen, or within a region, match a character or pattern.
link asserts that an OSC 8 hyperlink is present: link: { url, text } matches a substring of the link URI and, optionally, the linked text.

See File & Script Verifiers and Count Verifier for end-to-end examples.

Verifiers ​

Verifiers