[kinyoklion]

Summary

The contract test service now maps configuration.wrapper to wrapper_name/wrapper_version (an empty name or version counts as unset) and configuration.serviceEndpoints to stream_uri/base_uri/events_uri, and streams by default when only serviceEndpoints.streaming is given. It declares wrapper, service-endpoints and tls:verify-peer, so the harness now runs the wrapper header tests, events/disabling, service endpoints/using separate service endpoints properties (v2) and the three invalid tls certificate tests. The SDK verifies peers by default, so TLS needs no mapping.

Tested locally against harness v2.42.0 and v3.2.0-alpha.15 with persistence tests enabled: every newly run test passes and no test that passed on main fails or disappears.

_{Opened from termag}

---

Note

Overview
The contract test ClientEntity now maps harness configuration.serviceEndpoints onto SDK stream_uri / base_uri / events_uri (applied early; legacy streaming/polling/events blocks can still override). When there is no dataSystem, streaming, or polling block, use_ldd is enabled only if serviceEndpoints.streaming is absent—so a streaming-only endpoint config can drive live updates without an explicit streaming section.

configuration.wrapper is mapped to wrapper_name and wrapper_version, treating empty strings as unset.

The test service advertises wrapper, service-endpoints, and tls:verify-peer capabilities so the harness runs wrapper header, separate-endpoints, events-disable, and invalid-TLS scenarios (peer verification relies on SDK defaults, not new mapping).

^{Reviewed by Cursor Bugbot for commit 0370c08. Bugbot is set up for automated code reviews on this repo. Configure here.}