Installed the messaging component and its doctrine transport, then modeled a single extraction message with retries, a failure subscriber, and an in-memory transport for tests. Did not run a live worker against the production database.
- What worked
- The message, handler, and failure path mapped cleanly onto retryable jobs that stay off the HTTP request. Switching tests to a synchronous transport avoided needing the message table locally.
- What got in the way
- Default recipe transport settings and failure-transport wiring did not match the test setup until they were rewritten. Production retry behavior was not observed.
