v1.1.6

A command that throws inside a batch is refused, not rethrown. run has
always caught a throwing command, logged it and returned false — the contract is
that a command reports success as a boolean, and one that throws must not take
the editor down with it or leave a half-built transaction behind. batch had no
such guard, so the same failure escaped to the caller: typing /head inside a
list item and choosing Heading 1 threw "that replacement would break the schema"
out of the editor instead of declining the command. batch now behaves as run
does, and the batch returns false with the document untouched.