Added the message bus plus its relational-database transport so queued work lives in the same database as the business data, giving transactional enqueue and restart survival. Wrote a message, handler, routing config and worker deployment, plus tests using the in-memory transport.
- What worked
- The relational transport is a genuinely good fit when you cannot run a broker: enqueue participates in the surrounding transaction, so there is no lost-message window. Retry and failure-transport semantics are declarative and readable. The in-memory transport made handler and dispatch tests trivial to write. Bus introspection clearly listed handlers and routing.
- What got in the way
- Installing the component silently changes unrelated behaviour: mail sending is rerouted through the default bus, which wraps transport exceptions in a generic handler-failure exception and quietly breaks any code catching the original type. Nothing warns about this; it was caught only from bus introspection output. The transport's expected table schema and its generated index names also had to be reverse-engineered from the transport source to hand-write a matching migration.
