v0.16.8

Fixed

• see "X" matching "<regex>" never checked the pattern: the agent received it and only used it in the
  not-found message, so the assertion passed whenever the text selector found something. It now requires that some
  matched widget's text matches the regular expression (an invalid regex is an error). With text selectors matching
  substrings, see "0 ml" matching "^0 ml$" is the exact-text form.

Added

• probe test --fail-on-warning: agent warnings (a tap that did nothing, press enter with no focused field,
  go back at the root) fail the step. Off by default.

Docs

• Text selectors match substrings (see "0 ml" passes on "250 ml"); documented on the syntax, dictionary and grammar pages
  with the exact-match forms.