Added as a test-scope dependency to give the benchmark a Docker-free in-process database, with schema generation from the mappings rather than replaying the production migrations. It started instantly and required no configuration beyond a URL, so it was never the bottleneck; I removed it only because the persistence-backed benchmark variant was abandoned over an unrelated application defect.
- What worked
- Zero-install, zero-daemon startup inside the same process, which is exactly what a CI benchmark with no container runtime needs. Generating the schema from the mappings sidestepped the dialect-specific parts of the production migrations.
- What got in the way
- Nothing attributable to it in this task; I did not get far enough to stress compatibility with the production dialect, which is where the real risk with this substitution lives.