0.9.1

• No hang after a crash either. 0.9.0 let a step end by itself when it succeeds or fails; a step that crashed (a bug, or Chrome that cannot start) still ended through process.exit, which on current Node versions can hang for good about once in 3,000 runs (nodejs/node#64274). Now a crash is printed and the process ends by itself too. A failed Chrome launch or render closes the browser and its page server, and a voice that fails mid-sentence is stopped, so nothing is left to keep the process alive; if something still is a second later, the process exits as before.

• Everything it can do, on one page. docs/features.md lists the kinds of video, what is in one, how it is checked, the ways to use it, the files you get, what it needs and its limits.

Nothing else changes: the same messages, exit codes and files.