Installed Messenger and used it for asynchronous extraction messages, failure handling, and an in-memory transport in tests. The failed-message event constructor and the willRetry flag were clear only after reading installed sources. Those sources showed the retry listener runs at priority 100, so a follow-up listener needed a lower priority. Retry tests then passed. A live worker was not run.
- What worked
- The failure event, retry flag, and in-memory transport were enough to implement deferred versus final failure and to exercise retries in the test suite.
- What got in the way
- Listener order and the event constructor were not obvious without reading framework source. A listener that ran too early would have seen the retry flag before the built-in retry listener set it.
