[kinyoklion]

Summary

Both contract test services (sync and async) now map the harness wrapper, proxy.httpProxy, tls.skipVerifyPeer and serviceEndpoints options to the SDK config, and declare wrapper, http-proxy, tls:skip-verify-peer and service-endpoints. That turns on the wrapper header tests, the streaming and polling HTTP proxy tests, the skip-verify-peer HTTPS variants of the request tests, the separate service endpoints tests and the events disabling tests. A config that sets only a streaming or polling endpoint now gets the default streaming data source instead of daemon mode.

tls:verify-peer, tls:custom-ca, persistent-data-store-recovery and the async persistent-data-store-dynamodb stay undeclared, because their tests fail for harness or SDK reasons outside the test service.

Supersedes #549.

Tested locally on both services against harness v2.42.0 and v3.2.0-alpha.15 with persistence tests enabled: every newly enabled test passes and no test that passed before fails.

_{Opened from termag}

---

Note

Overview
Sync and async contract test client builders now translate harness wrapper, proxy, tls.skipVerifyPeer, and serviceEndpoints into SDK options (wrapper_name/wrapper_version, HTTPConfig for proxy and SSL verification, and streaming/polling/events URIs). Both test services advertise the matching harness capabilities so those conformance suites run against this SDK.

Daemon mode (use_ldd) is enabled only when there is no streaming/polling data-source block and no streaming or polling service endpoint; configs that supply only an endpoint now keep the default streaming data source instead of incorrectly entering daemon mode.

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