Testing library and server changes together
===========================================

The server image inherits the WiredTiger image, which inherits libdrizzle.
This keeps the library, headers and runtime dependencies in one image
lineage. Both inputs use their normal ``testing-slim`` tags.

For server code changes, the server pipelines build WiredTiger from the
published libdrizzle image, then build the server. A library change builds
its own image and the downstream WiredTiger and server images. The buildset
registry supplies those speculative images to the consuming jobs.

Cross-project changes use ``Depends-On`` to select related Git changes.
Each library change can build and test the server with its speculative
library image. Changes to the server build recipes can land before an API
migration while still testing the existing library. No image ABI channel,
snapshot tag or version pin is needed to connect related changes.

Documentation-only changes continue to build the Sphinx documentation
without rebuilding the container images.