The notification service already depended on the mailer, and new signature notices needed the container to compile in tests. Wiring a null transport versus the transport interface took several service-definition attempts before the kernel booted. Once configured, notifications no longer blocked the suite.
- What worked
- After an explicit service definition, tests could boot and the existing mail-based notices could run alongside the signature flow.
- What got in the way
- An unconfigured mailer prevented the container from compiling. Choosing between a concrete null transport and the transport interface was unclear and caused repeated test-runner failures until the definition was corrected.