[rmcdaniel]

Part of #325.

After #626, main's Shared Server fixtures still failed in mysql-execution and postgres-storage, in the SDK query directions profile (main run 39704552600). In the PHP-worker cases, the published Python client's hydrated response carried the query state in control_plane.result, while native's wire response had null.

Cause

• Published PHP SDK workers complete a query task with both the plain result and its result_envelope.
• Published PHP Server's completeQueryTask accepts both and returns the plain result beside the envelope; its control-plane envelope copies it.
• Native required the envelope, ignored the plain result, and always answered result: null.

What changes

• A completed query task keeps the worker's plain result.
• The answer returns it, and its control-plane envelope copies it.
• A plain result with no envelope is accepted, as PHP's rules allow. A completion with neither is still refused.
• The plain result counts toward the query result budget.

Verification

• A new integration test completes one query with a plain result and an envelope, and one with only a plain result. Both answers carry the plain result at the top level and in control_plane.
• The full SQLite suite passes (351 integration, 204 library).
• The query tests pass on PostgreSQL and MySQL (26 each).
• The fixture job itself runs on this PR. execution-and-codec also failed on main, but its step log isn't reachable from my network path, so I can't yet confirm it shares this cause.

Checkpoint: docs/rust-server-port-checkpoints/2026-10-22-query-worker-result.md.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud