second `unison :error` in transcript doesn't seem to function properly

[mitchellwrosen]

In the following transcript, the second unison :error stanza is accepted by the transcript runner, even though it doesn't contain an error. The preceding unison :error stanza seems to be required to demonstrate the bug.

``` ucm
scratch/main> builtins.merge lib.builtin

  Done.
```

``` unison :error
foo : Nat
foo =
  1 +
```

``` ucm :added-by-ucm
  Loading changes detected in scratch.u.

  I got confused here:

      4 |

  I was surprised to find an end of section here.
  I was expecting one of these instead:

  * bang
  * do
  * false
  * force
  * handle
  * if
  * let
  * newline or semicolon
  * quote
  * termLink
  * true
  * tuple
  * typeLink
```

``` unison :error
foo : Nat
foo =
  1 + 2
```

``` ucm :added-by-ucm
  Loading changes detected in scratch.u.

  I found and typechecked these definitions in scratch.u. If you
  do an `add` or `update`, here's how your codebase would
  change:

    ⍟ These new definitions are ok to `add`:

      foo : Nat
```

[aryairani]

@sellout Any thoughts on this?

[sellout]

It looks like hasErrors is getting re-initialized to False in the wrong place. I.e., for ucm blocks it gets reset, but for unison and api blocks, it’s not. Fix should be easy. I‘ll test it tomorrow.