[rmcdaniel]

Prepare immutable Server 2.11.7 and Helm chart 0.3.7 for the bridge-update retry correction merged in #862. Synchronize the authoritative source record, Composer product identity/hash, Compose defaults, Kubernetes manifests and chart defaults; add the chart's matching fix note.

The normal published Core dependency remains exactly 2.15.7 at 3aa98b8473b130dbc141457f76ccc32e4aa58062, and Symfony Mime remains 7.4.22. No locked package changes. The diff against qualified main contains release metadata/generated consumers and one narrow CI test correction.

The first Helm run exposed a stale test contract from #859: it forbade the whole-publisher success gate that #859 intentionally added. Update the test evaluator and assertion, replace the outdated partial-success wording, and add five-result behavior coverage proving that successful image/TLS outputs cannot publish a chart after a failed, cancelled, skipped or missing publisher result. The runtime workflows and publisher/credential bindings are unchanged.

Validation: all 29 Helm policy tests pass; the new behavior test produces four expected subcase failures on the original pre-gate workflow, with no errors. The source-release generator's three controls and check-version (0.3.6→0.3.7) pass; consumers are synchronized and diff checks pass. Composer schema/lock metadata is valid; its existing warning about the intentional exact Core pin is retained. #862 passed its fresh protected Feature, Shared and boundary checks before merging at 389c383155b50581f9dc9f6b2b13a858e9b0b7c7.

Refs #861 and #857. Keep both open, and keep 2.11.6's affected rolling aliases and deployment/reference hold explicit, until fresh publisher preflight, normal full publication and exact installed verification complete. Immutable 2.11.6 artifacts and prior rollback remain preserved.

[rmcdaniel]

Security source review accepts exact head c793c7a99bf1c62941ad26a057526c8905c9696e, tree 63e0e2bd29f553c983e515948b624862edf903ce, parent 8171fa277bfdbea7c842c8330859084d3fba132f.

The base-to-head release delta remains the reviewed 25 generated metadata/consumer files for Server 2.11.7 and chart 0.3.7, plus one test-only CI contract correction. Core stays 2.15.7 at 3aa98b8473b130dbc141457f76ccc32e4aa58062; Symfony Mime stays 7.4.22; no locked package changed.

The final one-file correction aligns the Helm release tests with #859's intentional whole-publisher success gate: the evaluator now models needs.publish.result, the structural assertion requires that gate, five result states prove only success may proceed when the exact-image and database-TLS outputs also succeed, and the obsolete partial-success name/message is removed. No runtime workflow, publisher binding, permission or credential consumer changed.

Independent exact-head checks pass:

• source-release syntax/check and all three generator controls;
• all 29 Helm release-policy tests;
• chart version check 0.3.6 -> 0.3.7 and diff check;
• Composer metadata validation (retaining only the existing intentional exact-Core-pin warning);
• Helm 3.16.2 lint for the chart and every checked-in CI/example values file.

The earlier 8171fa2 Helm failure is retained as evidence of the stale contract test. Fresh exact-head Helm run 40906542133 has passed immutable versioning, lint, TLS chart checks, rendering and Kubernetes schema/version validation; its kind install and the remaining hosted checks are still pending. Source review is clear, but protected merge clearance remains contingent on fresh terminal CI for this exact head. No tag, publisher dispatch, alias move, deployment/reference lift or reuse of prior clearance is authorized.

[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]

Security protected-merge gate is clear for exact head c793c7a99bf1c62941ad26a057526c8905c9696e.

• All 65 reported checks are terminal: 64 successful, one expected skip, none pending or failed.
• Fresh corrected-head Helm run 40906542133 passed both render/schema/version validation and the kind lint/install smoke.
• Full Shared run 40906542485 passed all 43 jobs, including the aggregate result.
• GitHub reports CLEAN / MERGEABLE.
• Prospective merge 918cd3859b7b9560c2d9c09c93a39ca0d5809f95 has parents qualified main 389c383155b50581f9dc9f6b2b13a858e9b0b7c7 and accepted head c793c7a99bf1c62941ad26a057526c8905c9696e; tree 63e0e2bd29f553c983e515948b624862edf903ce exactly equals the accepted head tree.

Proceed through the normal protected merge queue, then read back the actual merge identity/tree/parents and run Cloud's fresh five-publisher/consumer preflight against that actual merge. This is merge clearance only: no tag, publisher dispatch, alias move, deployment/reference lift, or reuse of 2.11.6 clearance yet.

[rmcdaniel]

Exact-head qualification is complete at c793c7a99bf1c62941ad26a057526c8905c9696e: 64 successful checks and one expected skip, including all 43 Shared jobs and both Helm jobs. Shared run · Helm run · Security review.

Submitted through the normal protected merge queue. Fresh group f55f90e54a213872f1c164a1b22c082d859c18aa has parents qualified main 389c383155b50581f9dc9f6b2b13a858e9b0b7c7 and the accepted head; tree 63e0e2bd29f553c983e515948b624862edf903ce equals the reviewed head tree. Fresh Feature, Shared and boundary checks are running. The existing scripts/ci/** policy selects the full Shared matrix for the Helm test correction.

No new tag or publication yet. #861 and #857 remain open through normal publication and installed verification.

[rmcdaniel]

Security protected-merge readback: PR #864 merged at 2026-10-29 16:49:50 UTC as f55f90e54a213872f1c164a1b22c082d859c18aa.

Its parents are qualified main 389c383155b50581f9dc9f6b2b13a858e9b0b7c7 and accepted head c793c7a99bf1c62941ad26a057526c8905c9696e; tree 63e0e2bd29f553c983e515948b624862edf903ce exactly matches the independently accepted source tree. Merge-group Feature 40911541461, Shared 40911541426 (all 43 jobs), and Boundary 40911541329 completed successfully. Protected main resolves to this exact merge.

Source and metadata recovery are accepted. Publication remains frozen pending Cloud's fresh complete live five-publisher/credential-consumer preflight bound to this actual merge and Security's bounded publication disposition. No tag, dispatch, alias move, deployment/reference lift, or reuse of prior release clearance is implied by this merge.

[rmcdaniel]

Normal publication has started from the qualified merge. Annotated tag 2.11.7 (object d901301a94edbd394912b00c647fad2fe6f699e7) resolves to exact source f55f90e54a213872f1c164a1b22c082d859c18aa / tree 63e0e2bd29f553c983e515948b624862edf903ce.

Tag-triggered Release 40919882321, created October 29 at 17:17:22 UTC, is the single normal producer run. It is building new immutable images; architecture/trust/first-run/Compose/database-TLS/protocol checks, rolling-alias promotion, GitHub Release and matching chart remain downstream gates. This is an in-progress publication, not installed acceptance. No manual dispatch or rerun.

Keep #861 and #857 open and the deployment/reference hold explicit until terminal publication and the exact-image 202→200/original-run/no-table-write check pass. Existing immutable releases and rollback remain preserved.