[rmcdaniel]

PHP Server now installs normal published Core 2.8.0 at 2edaa6b1c6f45fcec4570813c2e741aadde92b3b, including released entry-binding safety and optional bounded embedded continuation. Continuation remains disabled by default. Only Core changes in Composer's lock; other dependencies are unchanged. The unpublished alpha repository is removed, and the standard release metadata selects Server 2.9.11 / chart 0.2.1.

Merged at 987b07e1088293d9e5a8c5530a7f5ff563952968, with its whole tree identical to qualified head 512807cd3ef6af64da2df9e625264156a9def6ec. Changes from actual main, including native/shared/fixture/benchmark changes, are preserved without competing implementation or migration adoption in this PR.

Final combined-source qualification passes PHP feature/TLS, Sonar, chart, performance checks, replay/query, MySQL/PostgreSQL memo rolling and public-boundary checks. Local normal-pin controls pass 69 tests / 885 assertions.

The protected immutable publisher is ALL PASS. Server 2.9.11 is public at identical GHCR/Docker Hub index sha256:c4f304da0176ac8b6c3e391b7f541307294b5838140ceb3c85ba1e8c31998726. Chart 0.2.1 is public at OCI digest sha256:52c5fdf1dc7f7815abf9a1b315ad0acc1738e452d10f81122d2aa08e3317e428.

Published-image SQLite first-run, source-free MySQL Compose, catalog convergence, rolling promotion and anonymous chart clean install pass. Independent installed-image inspection matches all 955 Core product files and selected Server/TLS files. All 18 actual-image database TLS probes pass against PostgreSQL 17.11, MySQL 8.0.46 and MariaDB 10.11.19, using installed /app by immutable digest without source/vendor mounts or Composer changes. The exact-image acceptance receipt records architecture digests, successful encryption, CA/hostname and mandatory-TLS refusals, database scope and explicit limits. Functional Server/TLS acceptance is AMD64; both image architectures are published. No HTTPS ingress, native/shared or Cloud adoption is inferred.

Earlier source-alias/candidate results remain historical rather than published-artifact proof. The optional 0c93deb performance run 39508890259 has a failed aggregate after both duplicate product jobs were cancelled with zero executed steps; this is neither a product pass nor an observed product failure. The admitted 82d original and all newest-head checks are preserved. Local generator attempts missing host PHP/container Git remain setup failures; normal repository-contract checks pass. The initial additional published-image checker expected a Composer path reference to be a Git SHA; that failed assumption and its source-preserving correction are documented in the final receipt.

Related: Workflow #748, Core 2.8.0 and configuration/operating limits. #773's later tracing/observability release qualifies independently against this actual published tuple.

[rmcdaniel]

Server 2.9.10 / Helm 0.2.0 publication source is the merged security head 870eb3be36bf4e191cb3e06e52e2b4e88f38039b, whole tree acc127e88865b6b9acf35cdd8744bf40528812e5.

The PHP runtime, Composer dependencies, TLS configuration, release metadata, chart and image inputs are byte-identical to TLS merge 3785364c, whose independent main feature, HTTP, performance, rolling-upgrade, chart, Sonar and boundary workflows all pass. The only subsequent changes are seven reviewed certifi pins/hashes. Their exact candidate tree matches merged 870eb3be; required feature, repository, Sonar and boundary checks pass, all seven actual locked installations and HTTPS/trust checks pass, and GitHub now reports zero open Dependabot alerts. The optional cancelled parity/performance jobs were not acceptance evidence.

I am publishing that exact immutable source through the normal protected release workflow. New main repeats remain independent and are not claimed complete. This is the TLS/security release on the existing Core 2.7.2 reference. It does not adopt the forthcoming Core 2.8 consumer or any native change. The Core consumer owner can use the following ordinary Server/Helm versions after its own exact qualification. Registry image, chart and installed TLS acceptance remain required before closing #540.

[rmcdaniel]

PHP Server 2.9.11 release ordering: #552 now integrates current main f4937be at candidate 0c93deb. Its PHP application, configuration, Composer, Docker, resources, chart and workflow bytes match the preceding tested PHP candidate. Native, benchmark and namespace files match current main. Fresh protected checks still qualify this exact combined head.

The next PHP merge and immutable 2.9.11 tag will use that qualified merged tree once checks finish. Please coordinate any intervening main promotion with the #552 maintainer at this actual merge/tag handoff, so unchanged PHP qualification does not become a repeating ancestry cycle. Independent implementation, branch review and existing admitted qualification continue. Published Core 2.8.0 and Sample #264 acceptance are already complete; this remaining Server consumer release is the current handoff.

[rmcdaniel]

The protected merge of qualified 0c93deb0 was rejected when main advanced from f4937bed to adefcf83 through #543. Its required PHP feature suite had passed, including full tests, candidate first-run and TLS/certificate refusals. Sonar, repository contracts, chart, rolling upgrade and replay/query checks also passed. No bypass or release tag occurred.

Current candidate 512807cd3ef6af64da2df9e625264156a9def6ec now integrates exact main adefcf8315a7a9eaa339852166e08fed15ff51ab. All native/shared fixture, runner, benchmark and conformance changes equal main. PHP application/configuration, Composer, Dockerfile, resources, chart and PHP feature workflow remain identical to 0c93deb0. The fresh required PHP route, Sonar and ordinary affected checks run on this combined source. Its broader new shared fixtures are preserved; no newest-head optional runs are canceled.

The planned immutable publication remains PHP Server 2.9.11 / chart 0.2.1, consuming normal published Core 2.8.0 at 2edaa6b1. Please coordinate any next main promotion at this actual merge/tag handoff, so an exact qualified source can reach publication. Independent source branches and admitted qualification continue. This requests no source-file freeze or gate bypass.

[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

[rmcdaniel]

The normal protected merge of #552 is complete at 987b07e1088293d9e5a8c5530a7f5ff563952968, merged at 23:20:43 UTC. Its entire tree equals qualified candidate 512807cd. Required PHP feature/TLS, policy, repository contracts and exact-source Sonar checks pass. Current chart, rolling-upgrade and bounded-growth product checks also pass; the remaining aggregate checks are separate from those executed tests.

The annotated immutable 2.9.11 tag is pushed and remotely verified: tag object b5415f6e33d04e8517cf8678f68c4581c0c8c82b peels to 987b07e1088293d9e5a8c5530a7f5ff563952968. Source authority selects PHP Server 2.9.11 / chart 0.2.1 and normal published Core 2.8.0 at 2edaa6b1.

Protected Release 39514473813 is queued at that exact tag/source. Actual image, catalog, rolling-channel and matching immutable chart/install acceptance remain pending. Earlier candidate images and 2.9.10 publication do not supply those results.

This completes the short #552 main merge/tag handoff. Independent branches and subsequent main promotions can continue in the coordinated order; the immutable publication source remains fixed. The next receipt will identify actual published image/chart digests and acceptance outcomes.

[rmcdaniel]

PHP Server 2.9.11 / chart 0.2.1 is published and accepted. PR #552 merged normally at 987b07e1088293d9e5a8c5530a7f5ff563952968; its whole tree equals qualified head 512807cd3ef6af64da2df9e625264156a9def6ec. The immutable annotated tag peels to that merge. The protected publisher completes successfully, including matching chart publication and install.

Artifact identity, independently read back from the registries:

Artifact	Immutable digest
Server 2.9.11 index, identical at GHCR and Docker Hub	sha256:c4f304da0176ac8b6c3e391b7f541307294b5838140ceb3c85ba1e8c31998726
linux/amd64 manifest	sha256:5839f720b5ec221f49aa14b1b6a79d5dc5c439f86aebb5478a693f495e3016ab
linux/arm64 manifest	sha256:c6351c9a881d959c5fa0ecc8ed4756af8623f9c0e19bfd807bd0d2d073b97b28
OCI chart 0.2.1 at ghcr.io/durable-workflow/charts/durable-workflow	sha256:52c5fdf1dc7f7815abf9a1b315ad0acc1738e452d10f81122d2aa08e3317e428

Actual installed-image acceptance is distinct from source qualification:

• The publisher passes bare-image first-run on a fresh SQLite volume, including explicit bootstrap/readiness recovery, source-free MySQL Compose bootstrap, published catalog convergence and rolling promotion. Both image architectures are published; these functional image journeys run on AMD64.
• Chart acceptance passes an anonymous OCI pull, byte comparison with the packaged chart, and a clean kind install with MySQL/Redis fixtures using the actual immutable Server image. This is ordinary chart installation, not a database-TLS Kubernetes deployment.
• Independent inspection of the published AMD64 image matches all 955 Core product files, five vendor classes and two function files to Core 2.8.0 / 2edaa6b1c6f45fcec4570813c2e741aadde92b3b, plus six selected Server/TLS files to the actual Server merge. The standard image's Composer path repository uses reference=auto; canonical .package-provenance and complete product hashes identify the source. An initial extra check incorrectly expected its local path reference to equal the Git SHA; that checker failure is retained and corrected without changing product source, image or tag.
• The existing database TLS probe was then run against installed /app from the published image by digest, without source/vendor mounts, Composer installation or image rebuilding. All 18 probes pass on direct PostgreSQL 17.11, MySQL 8.0.46 and MariaDB 10.11.19 fixtures: three CA/hostname-verified connections, three encrypted require connections, ten expected refusals and two explicit plaintext connections. All six encrypted positive probes report backend TLS 1.3.
• Refusals cover wrong CA and wrong hostname on all three databases; absent/missing CA configuration on PostgreSQL; and require against TLS-disabled PostgreSQL/MySQL. They return readiness 503 with the expected TLS configuration/connection reason. Plaintext mode explicitly succeeds only on the two TLS-disabled fixtures. This covers PHP-to-configured-database transport, not HTTPS ingress, proxy-to-database TLS, client certificates, expired certificates or production rollout.

The final combined-source PHP feature/TLS suite, Sonar, chart, performance checks, replay/query and MySQL/PostgreSQL memo rolling checks all finish successfully. Earlier failed/cancelled originals remain attributed in the PR history. No earlier 2.9.10 image result is carried as 2.9.11 artifact qualification.

Core continuation remains disabled by default, with its documented bounded opt-in profile. This consumer update changes no native/shared/frozen/catalog implementation or migration contract. Other maintainers' main-branch changes are preserved in the release; no native/shared/Cloud adoption is claimed. The local database qualification's containers, volumes, certificates and network have been removed. Related: Workflow #748.