opcua-client-ext-transport-httpslisted

# php-opcua/opcua-client-ext-transport-https — v4.4.0 skill An optional transport extension of [`php-opcua/opcua-client`](https://github.com/php-opcua/opcua-client) implementing the OPC UA **HTTPS mappings (Part 6 §7.4)**. Each UA service message is exchanged as a single HTTPS `POST`; **TLS is the secure channel**, so the OPC UA `OpenSecureChannel` handshake is skipped entirely. The core `opcua-client` only adds two contract methods on `ClientTransportInterface`; everything else (transport, encoding strategies, HTTP client, events, exceptions) lives here under `PhpOpcua\Client\ExtTransportHttps\*`. ## When to use this skill Activate when any of these apply: - An endpoint URL starts with **`opc.https://`** (or a plain `https://` OPC UA endpoint) - The task is to run OPC UA **over 443 / through a corporate proxy / firewall** where `opc.tcp://` is blocked - The HTTPS **binary** (`application/octet-stream`) or **JSON** (`application/opcua+uajson`) mapping is mentioned (Part 6 §7.4.4 / §7.4.5) - A `HttpsTransport`, `HttpsEncodingStrategy`, `BinaryHttpsEncoding`, `JsonHttpsEncoding`, `CurlHttpClient`, or `ServiceCodecInterface` appears in code - Someone is wiring a non-TCP transport into `ClientBuilder::setTransport()` Do NOT activate for: ordinary `opc.tcp://` connections (core `opcua-client`), Reverse Connect (`opcua-client-ext-reverse-connect`), or generic HTTP/REST work unrelated to OPC UA. ## The 60-second mental model ``` ClientBuilder->setTransport($httpsTransport)->c