Record SDK direction qualification and give CI bounded resource headroom

[rmcdaniel]

The growing shared fixture suite can exhaust its CI allowances after its comparisons finish. Give PostgreSQL 20 minutes instead of 15, matching MySQL, and give MySQL 8.0 the existing MySQL 8.4 database limit of 1 GiB instead of 768 MiB. Memory-swap remains equal to memory. The earlier PostgreSQL timeout and MySQL OOM are retained as distinct failed attempts; the final MySQL artifact confirms a running database, OOMKilled=false, the actual 1 GiB limit and successful certificate trust/hostname checks.

Update the port log and SDK fixture README to record #401's qualified nine PHP/Python/Rust workflow/activity directions, exact-tree merge and completed six-configuration main follow-through. Preserve its one-scenario/default-namespace scope, canonical embedded applicability, independent 27-record and 54 raw-sidecar checks, and the next parent/child fixture action. Broader consumers, capabilities, matched performance, migrations and cutover remain open under #325.

Validation at c9dc781: Shared qualification passes all six configurations; PHP/source checks and both boundaries pass. Actual SDK preparation artifact/source hashes and runner tree match the final candidate. Official MySQL artifact 11709102686 has matching API/uploader/download identity; retained diagnostic members compare exactly to its ZIP. Diff check passes. Runtime code, fixture semantics, pinned tuples and performance limits are unchanged.

[rmcdaniel]

Head bbe992ec7bc2c0d276471936f35dce19e768bc70 passed PHP/source, both boundaries and five of six runtime configurations. MySQL 8.0 passed all comparison, recovery/refusal, role-token, worker-fencing and SDK database-pressure steps; its trusted TLS probe then reported storage_unavailable. The retained official artifact proves the database container was OOM-killed, exit 137, under its 805306368-byte / 768 MiB cap. The failed TLS step cannot qualify certificate behavior against a dead database, so that head remains unqualified as a whole.

Final head c9dc7818626085833abe6ad40712435b426d477c gives MySQL 8.0 the existing MySQL 8.4 allowance of 1 GiB, with memory-swap still equal to memory. PostgreSQL keeps the bounded 20-minute allowance established here. Runtime code, published tuples, fixture semantics and performance qualification limits are unchanged. New Shared qualification and PHP/source checks are running; final boundaries pass.

Failure evidence is retained under official artifact 11708656464 (SHA-256 b5cfb303b879d53ea758e4097a068d21c82c940b039719ca62fa0a198ab52715, size 38861801), with API/uploader/download identity checked. Relevant retained files compare exactly to its ZIP members. #401's unchanged main retry is independently completed success across all six configurations: receipt.

[rmcdaniel]

Merged as ba830d89d71d71d203ebdc21b18494b9a5ec8d23, with the same qualified tree dee334b1cbbb8371018ef6439c5dfdbddf539985 as final candidate c9dc7818626085833abe6ad40712435b426d477c. Shared qualification passes all six configurations; PHP/source checks and both boundaries pass. The remote PR head is removed and its absence verified.

Independent inspection of final MySQL 8.0 artifact 11709102686 confirms the actual 1 GiB cap, OOMKilled=false, a running database, trusted TLS success and refusal of the untrusted CA and wrong hostname. Its API/uploader/download size and checksum match, and retained diagnostic files compare exactly to the official ZIP. The earlier OOM and PostgreSQL timeout remain separate failed-attempt records.

Post-merge checks are being checked against this exact merge; a completed main result is still pending. #401's main follow-through is already complete. The next #325 fixture family is published parent/child SDK directions, with the bounded acceptance criteria recorded on #325.

[rmcdaniel]

Main follow-through for merged #406 is complete. Shared run 38158528955 passes all six configurations at ba830d89d71d71d203ebdc21b18494b9a5ec8d23. PHP/source 38158528999 and normal push boundary 38158528973 pass at the same merge.

The qualified candidate tree is preserved, including bounded MySQL 8.0 database memory and PostgreSQL job time. The earlier OOM failure and original PostgreSQL timeout remain separately recorded. These are qualification resource changes; they establish no matched performance result.

Draft #408 now carries the additive published parent/child direction definitions. Worker adapters, reader integration and isolated execution remain pending. Unrelated manual boundary metadata scanning is handed to its owner in #407.