Screenpy

------------------

Improvements

- Added `.of_the_first_of_the` aliases to several Actions and Questions, to allow for clearer readings of tests.
- Added an `aside` of the actual value when `See` is about to compare a pre-baked value instead of asking a Question.
- Fixed `IsNot`'s descriptions, especially when they were describing when the negative (... of the negative).

------------------

Bugfixes

- Fixes the Narrator skipping narrations if they occurred within a double-kinked cable. In fact, completely rewrote how the Narrator handles multiple cable kinks in a much more understandable way (h/t bandophahita).

------------------

Bugfixes

- Another bugfix for the Narrator when reporting errors -- if the user isn't using Allure, an error in the script would cause a `StopIteration` error to be raised aftewards. Pretty annoying when debugging!
- Speaking of errors being raised, if an error were raised while the Narrator's mic cable was kinked or while the Narrator was off the air, the Narrator would *never narrate again* (until the next script ran anyway). That's fixed!

Improvements

- Fixed up the quick hackjob for narrating errors to put it in a much more elegant spot.

------------------

Bugfixes

- Kind of critical bugfix for the Narrator's new ability to report errors -- the Narrator now only reports errors if their mic cable is not kinked and they are on air. This was causing some pretty unfortunate interactions with `Eventually`...

------------------

Bugfixes

- The `clean_up` method that all Actors use to clean up after themselves was mutating the cleanup task list as it was iterating through it. This was not good! Actors have been reminded of proper looping etiquette.

Improvements

- `Eventually` now raises a `DeliveryError` to bring it in line with `Wait` and all other Actions which raise errors.
- `Eventually` now mentions all of the exceptions it encountered when it raises `DeliveryError`.
- Several Actions have less-awkwardly-worded `beat`s!

------------------

Bugfixes

- `MakeNote` and `See` both relied on catching an `AttributeError` to figure out if they had been passed a value or a Question. But if the Question itself encountered an `AttributeError` while being answered, a very confusing situation would arise that was very annoying to debug. Now these two Actions use `hasattr` instead!
- The `AllureAdapter` is no longer falsely marking steps which failed as having passed! Bringin' back them reds and yellows.

New Features

- The `Adapter` protocol now supports an `error` method, which allows adapters to report exceptions in their own way.