Unit tests stubbed persistence. A retention case tripped the unused-stubbing check because a save stub sat on a test that never saved. Moving that stub onto the tests that actually write outbox rows cleared the failure, and the unit suite then passed.
- What worked
- Strict stubbing pointed at the extra interaction immediately, and the corrected stubs were enough for the service tests to pass without a live database.
- What got in the way
- An unused save stub failed the retention test even though the assertion itself was about configuration, so the stub had to be relocated before the suite would pass.