Prepare PHP Server 2.8.0 / Helm 0.1.168 query authority release

[rmcdaniel]

Server 2.8.0 / Helm 0.1.168

Prepare the compatible minor release for the qualified PHP query-authority source in #456. Exact source main d8effcf7 passes all applicable normal checks (#433 checkpoint).

This PR changes the release manifest and its generated consumers only. Composer dependencies, PHP runtime source, native subtree, current protocol schema 54, shared fixtures and frozen actor manifests are unchanged. Composer lock changes only its content hash.

Generation and synchronization checks pass. The local metadata test run has two passes and one tooling failure because its Node image lacks PHP. Required hosted repository checks remain ahead; this is not full local test acceptance.

Before publication: exact candidate review/checks, merge/main checks, then protected publication, normal image/Helm identity verification and affected SDK query consumers. Original admission deadlines, non-renewing 1.20 observation, explicit 1.19 status refusal and fixed committed receipts must hold on the published runtime. Zero result timeout now expires immediately, as agreed in #433.

Python's loading/handler correction is separate draft SDK #151. Keep #433 and SDK #143 open until the respective published/installed gates pass. No native query capability, frozen cohort, Cloud deployment or full loading fix is inferred from this metadata preparation.

[rmcdaniel]

Reviewed exact 6b2349c338606fa91c8301ce178c9d419cfb54b5 / tree 0256585d96f9886f17e934b68db87985b6de1d50 against delivered PHP source d8effcf7.

The 25-file diff is release metadata and generated image/chart consumers. Runtime PHP, routes, schema 54, native source and all Composer package entries remain unchanged; the lock changes only its content hash. Chart annotations, defaults and the manifest agree on Server 2.8.0 / chart 0.1.168. Review caught and corrected the old 2.7.2 Artifact Hub changelog text.

The two incomplete local metadata test attempts remain tooling failures; hosted repository contracts pass. The superseded first metadata head's still-running feature/performance runs were cancelled after this changelog correction to avoid duplicate work. Its completed checks stay attached to that old head; exact current-head acceptance is still required.

No runtime or installed-image claim is made until the protected release and affected query consumers pass. The prior 2.7.2 image remains the rollback identity; zero query result timeout now means immediate expiry under the agreed contract.

[rmcdaniel]

Merged #459 as dd720e6, whole tree 0256585d96f9886f17e934b68db87985b6de1d50, exactly matching the reviewed candidate and its tested synthetic merge.

Required feature checks pass (2,809 tests / 63,893 assertions, six existing deprecations and one skip). Actual MySQL query HTTP, both rolling-upgrade databases, chart lint/kind, polling smoke/bounded contract, repository contracts and boundaries all pass. At merge, only the performance aggregation job remained queued; its two test dependencies had both passed. No aggregate completion is inferred.

Fresh-main feature 38660283737, HTTP 38660283796, performance 38660283651, rolling upgrade 38660283609, chart 38660283653 and boundary 38660283601 are separately running/queued. Protected image publication and affected installed query consumers remain pending. No Server 2.8.0 image or complete #433 delivery claim yet.

[rmcdaniel]

The final candidate performance aggregate has now passed as well. All applicable candidate checks are successful.

Created immutable tag 2.8.0 → dd720e6 for protected publication. Its whole tree 0256585d96f9886f17e934b68db87985b6de1d50 is byte-identical to the fully qualified candidate/synthetic merge. Those exact-tree results provide source acceptance; automatic fresh-main runs remain pending and are not reported as passes.

Protected image publication, clean image/chart verification and affected installed query consumers remain required before published-product acceptance. Source #456, Server #433 and Python #143 retain their stated boundaries. No native query authority or frozen tuple adoption is implied.

[rmcdaniel]

Server 2.8.0 is published from dd720e6b51844707be2885f8873c23de98c847a7, exact qualified tree 0256585d96f9886f17e934b68db87985b6de1d50.

• Immutable image index: sha256:cba7c4c6732529293ef6c2625a64785dcb21b4f7fe0013fdc74f1af466f534ac (amd64 8248d586…, arm64 ebf31bc3…).
• Protected release 38660892747 passes exact image publication, bare/Compose bootstrap, published protocol catalog and matching immutable Helm 0.1.168 publication/verification.
• Fresh-main feature, actual MySQL query HTTP, polling/performance, rolling-upgrade, Helm and boundary checks all pass on this merge. The feature result remains 2,809 tests / 63,893 assertions with the existing six deprecations and one skip.
• A normally pulled image passes the compatible Python candidate's three actual authenticated query-authority cases: timely typed response, expiry during external loading and expiry during async handler execution. Each keeps the original query identity/deadline; expiry prevents completion submission. All phase resources are removed.

The public Python package follow-through is still SDK #152. Server #433 remains open through that registry-installed acceptance; the private candidate does not establish a public SDK release or Cloud cohort qualification. Runtime source is #456; this PR contains release metadata. Rust's combined current schema and native authority qualification remain separate.