What each test layer covers, what it needs to run, and what it is for. Counts are test
functions (a deterministic property of a file); the number of cases depends on how the
suite was invoked, so it is not claimed here.
tests/e2e/test_http_chain.py::test_the_process_stops_on_sigterm skips on Windows — it
uses POSIX signals, and it says so in its skip reason rather than pretending to pass.
Every live layer skips when its lab is absent, naming the missing variable and the
operator step that provides it. A suite that failed without a container would teach nothing.
No layer covers a second database vendor. The dialect seam exists (QueryDialect,
MysqlDialect); the example runs PostgreSQL, and no test claims otherwise.
Coverage of the example is not a gate. The library's own coverage floor is enforced in
CI; the example's layers exist to be run, and their value is the defects they found (see the
README's "what writing it found").