[njoubert-cleverage]

Description

Fixes #66.

• RequestTask logs a failed call (SoapFault) as Soap call failed instead of the misleading Empty resultset for query: same error level and log context (options, fault message, last request and response).
• RequestTransformer: remove the monolog.logger tag, the transformer has no logger (the tag had no effect).
• MissingClientException::create(string $code) is typed (the @param string PHPDoc is removed); ClientRegistry passes a string.
• Client reference: a client, shared, keeps its state between two process executions in a long-running worker (Messenger, ui-process-bundle): SoapClient and WSDL, options and headers changed with the setters, last traces. Completes the existing note on shared clients. No ResetInterface: the bundle never changes the WSDL, restores the options and headers after each call, the traces are overwritten at each call, keeping the SoapClient is wanted, and a reset to the constructor values would undo the calls of the service definitions.
• request_task.md and the soap_enrich_csv cookbook mention the new log message. CHANGELOG.

Tests: RequestTaskTest::testFailedCall checks the new message; the extension test checks that the transformer has no monolog.logger tag.

Checked in the container (highest dependencies after composer update): 52 tests (1 skipped, as on main: KernelTest needs process-bundle 5.4), 100 % of the lines (226/226), no risky test (pcov coverage). PHPStan, PHP-CS-Fixer and Rector OK.

Requirements

• Documentation updates
  • Reference
  • Changelog
• Unit tests

Breaking changes

None. The log message of a failed call changes (an alert or a log filter on Empty resultset for query must be updated). Calling MissingClientException::create() with a non-string code from a file in strict_types mode throws a TypeError (the codes are strings everywhere in the bundle).

🤖 Generated with Claude Code