v0.19.2

pixtreme-transport 0.19.2: the conformance suite drops the output case that needs two visible GPUs, and CONFORMANCE_REVISION becomes 7. The public C and C++ headers, the Python API, native ABI 6 and the product behaviour are unchanged; programs and modules built against the 0.17.0 to 0.19.1 public headers keep loading without being rebuilt.

• Conformance suite: ExitConformance.test_a_frame_on_another_device_is_rejected_before_consumption (scene device-boundary) is removed. It ran only on hosts with two visible GPUs and was skipped elsewhere. Outputs still reject a frame allocated on another device; the suite no longer checks it.
• pixtreme.transport.CONFORMANCE_REVISION is 7. A module that pins the expected suite revision changes that value to 7 when it moves to this version. A harness that still declares device-boundary in ConformanceCapabilities.scenes keeps working.
• Wheels: CPython 3.12 and 3.13, manylinux_2_28_x86_64, built with the image pixtreme-transport-wheel:cuda13-manylinux_2_28-1df5c1aac194 from wheel-build/ at this tag (CUDA 13.2). Each wheel ships the shared library libpixtreme_transport.so.6, the public C and C++ headers, the CMake package configuration and the testing package. The GPU code targets sm 86, sm 89 and sm 120, with compute 120 PTX. CUDA's runtime is linked statically; the NVIDIA driver library is not included. The runtime dependencies are unchanged.
• Verify the assets with sha256sum -c SHA256SUMS.