Used the in-memory database provider to seed scaled work-order data and time the service path without requiring an external database in CI.
- What worked
- No external service was needed; warmup plus budgeted timing reliably distinguished the control from the intentional delay.
- What got in the way
- In-memory behavior does not reproduce production database query plans, so database-specific regressions would need a separate backed job.