[rmcdaniel]

Advance the authoritative chart record from 1.7.0 to 1.7.1 and native app/default image from 3.9.1 to 3.9.2, with generated consumers and versioned upgrade notes. The five-file change describes Unicode command-key/receipt correction and observation-file owner hardening, keeps the unchanged 3.9 schema and old-version restore boundary, and leaves PHP frozen at 2.11.8.

Normal source, kind, PHPUnit, analysis, exact Security review and merge-group checks passed. The merged tree equals the reviewed source; both topic branches were removed. Protected Helm run 43465478903 published and verified a clean anonymous OCI install. Final package/source/manifest receipt and independent Security publication/content PASS bind the exact qualified Server 3.9.2 / Chart 1.7.1 pair.

Docs #538 selects that pair, with independent scoped live manifest/English readback. Installed #216/#228, Cloud/draining uploads, MariaDB #1204 and the later dispatch-summary schema retain separate gates. No runtime/Compose source was changed by this chart release.

[rmcdaniel]

Security source review of Server #1211 exact f2edaa30e4dd330d8dbc408bb96cbf133c33484a: PASS for the five-file chart source slice.

Independent scope and identity checks:

• The complete delta from accepted 5614274d2629d03f92932a07dfee0fb10349ddd9 is exactly resources/release/source-release.json plus the four declared chart consumers: Chart.yaml, values.yaml, README.md, and docs/UPGRADING.md; git diff --check is clean.
• The authoritative record binds chart 1.7.1, native app 3.9.2, and retains frozen PHP Server 2.11.8. The chart version, appVersion, image-reference annotation, default image tag, README example, and upgrade entry agree.
• The 3.9.0/3.9.1 path correctly claims no schema step; the 3.8-or-earlier schema/backup/restore boundary is retained. Rollback wording does not hide the Unicode-key, receipt-metadata, or observation-owner behavior change.
• The text keeps installed Return fenced backend-loss response for workflow completion #216/Adopt Workflow 2.2.10 timestamp repairs #228 cohorts, storage-admission ancestor/mapping and draining-upload/Cloud acceptance, MariaDB MariaDB held activity poll can time out worker re-registration in native tests #1204, protected OCI publication, and downstream consumer selection outside this source PASS.

The exact archived tree passes source synchronization and all 30 Helm release-helper controls; hosted lint/render/kind, repository contracts, boundary and Sonar checks also pass at this head. This verdict does not qualify or publish the OCI chart. Merge/publication remain gated on the final Server 3.9.2 corpus, protected promotion/Release readback, exact-head completion, and the existing chart publication/content checks.

[rmcdaniel]

Normal refresh onto accepted main 8fb983d9fcbf1528a901e8f9844eba7308726240 is exact head 951fb240524a3c9821b0cffa8983462ee48f727d, tree 93e424789177e3de2475ec69e2251dbf387a7fc7. All five chart-owned blobs are byte-identical to reviewed f2edaa30; no conflicts or own-diff changes. The authoritative pair remains Chart 1.7.1 / native app 3.9.2. Incoming main's later dispatch-summary schema does not change the immutable 3.9.2 app or its documented upgrade/rollback boundary.

Fresh release controls pass 30/30, source synchronization and validate-source pass, and the public-boundary scan and diff check pass. The test suite's “OCI already contains content” line is an inert fixture, not a publication result. Normal exact-head CI and bounded Security tree/history countercheck remain required. Draft/merge/publication still waits for native 3.9.2 final GitHub Release and readback; protected alias promotion 43460837991 is now successful and independently reviewed.

[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 final refresh tree/history countercheck: PASS for Chart #1211 exact 951fb240524a3c9821b0cffa8983462ee48f727d, tree 93e424789177e3de2475ec69e2251dbf387a7fc7.

• This is a normal two-parent merge of source-approved f2edaa30e4dd330d8dbc408bb96cbf133c33484a onto accepted main 8fb983d9fcbf1528a901e8f9844eba7308726240.
• Independent git merge-tree --write-tree 8fb983d9... f2edaa30... produces exactly 93e424789177e3de2475ec69e2251dbf387a7fc7.
• All five PR-owned blobs are byte-identical to the reviewed source:
  • Chart.yaml 230a7eccfe489cccf48d290221f3af4a7231e2b0
  • chart README.md 72079aa79f94f822867ebdcc2d735f999b53681e
  • docs/UPGRADING.md 18f4d28607f60e8422f74c57e7e1fbb5e8718259
  • values.yaml 715f47bc4caf34c36188a86aa17e2f4231ce6a5c
  • resources/release/source-release.json da7f1a0b9972df94dda0af61af42f73c67a3bdbe
• The complete diff from accepted main remains exactly those five paths. Incoming Report bounded schedule dispatch summaries for Waterline refresh #1200 dispatch-summary source is preserved and does not change the Chart 1.7.1 / native app 3.9.2 selection or advertise that later unpublished schema through this chart.
• The formerly external native-release prerequisite is now independently closed: Server 3.9.2 is stable/Latest at source 5614274d... and index 8ffcdb2a..., matching this reviewed chart source.

Fresh exact-head CI is still the merge gate (the Rust analysis and PHPUnit feature lane are running at review time). OCI Chart 1.7.1 publication, anonymous install/content readback, Docs pairing and consumer acceptance remain separate and are not inferred here.

[rmcdaniel]

All current exact-head checks at 951fb240524a3c9821b0cffa8983462ee48f727d are terminal green or intended skips, including kind install, Rust analysis and PHPUnit feature qualification. Final Security tree/history PASS and native 3.9.2 final publication PASS are both complete.

Marked ready and submitted through the normal merge queue with an exact-head match. Provider readback shows position 1, awaiting merge-group checks. No administrator/bypass option was used. Server retains merge/main equality, protected OCI publication and exact package/source/content readback. Docs #538 retains paired selection and public deployment afterward; no publication is inferred from queue admission.

[rmcdaniel]

#1211 merged through the normal queue at 298106197bf7edab555302af326f101a02114191. Its complete tree 93e424789177e3de2475ec69e2251dbf387a7fc7 exactly equals reviewed head 951fb240; no extra runtime or release-source change is present. Merge-group checks passed. The merged remote and local topic branches were deleted, and remote absence was verified.

Protected Helm publication run 43465478903 is running from that accepted main source. Server retains exact package/OCI/source/content and qualification readback, followed by independent Security review. Docs #538 retains paired selector and live deployment. No OCI identity is guessed from merge or source checks.

[rmcdaniel]

Chart 1.7.1, app/default native 3.9.2, is published by protected run 43465478903. Both source validation jobs and protected publication/anonymous clean-client kind install are SUCCESS. Actual accepted merge source is 298106197bf7edab555302af326f101a02114191; its tree exactly matches reviewed 951fb240.

Exact public identities:

• OCI reference: oci://ghcr.io/durable-workflow/charts/durable-workflow:1.7.1.
• Anonymous raw manifest digest: sha256:1275bdf200878c292bad204edbd30478574c5c60ee30293281605d5ab551b980.
• Package/layer digest: sha256:ca2a3b60d01b33a9474e28932b41a8e64ac1c21931a9af45c8763b378938490d (52,177 bytes).
• Helm config digest: sha256:8260a6d869f0163e011cbfbb650791de5305379da6ac89fe8846700b59398a5c.
• Actual chart source revision: f2edaa30e4dd330d8dbc408bb96cbf133c33484a, derived by the protected publication command from the last chart-touching source commit, not guessed from the merge SHA.
• Retained evidence artifact: 14059062209, ZIP SHA-256 58787e865e0dfa89194ca6d6b688222c25a7098e1527cf1ea561436783f9c49a (52,883 bytes), from this exact protected main run/source.
• Bound native app index: sha256:8ffcdb2a36af3129a1987849aafe8715fe0d3bf9a9648467f0b5cb8eeef43ba9, the qualified stable 3.9.2 tuple.

I independently read the public OCI manifest/config/layer without credentials, checked descriptor lengths and hashes, and compared all 28 packaged files to the accepted source. Chart.yaml is semantically identical with only the expected source-revision annotation filled; all other packaged files match byte-for-byte. The artifact's package equals the public OCI layer byte-for-byte. Its exact version/app/source/image identities and anonymous_install:pass agree with the successful workflow steps. Merged topic branches are removed and remote absence is verified.

Final independent Security publication/content/OCI PASS is recorded. The qualified Server 3.9.2 / Chart 1.7.1 pair is ready for the Docs selector handoff. Docs #538 owns the paired selection and public all-locale readback. Installed #216/#228, Cloud adoption, draining uploads and the later dispatch-summary schema retain separate gates; this chart does not publish that next schema or claim their completion.

[rmcdaniel]

Security publication/content countercheck: PASS for Chart 1.7.1 / app 3.9.2, protected run 43465478903, accepted source 298106197bf7edab555302af326f101a02114191.

Independent anonymous readback confirms:

• OCI manifest sha256:1275bdf200878c292bad204edbd30478574c5c60ee30293281605d5ab551b980 (2,310 bytes);
• Helm config sha256:8260a6d869f0163e011cbfbb650791de5305379da6ac89fe8846700b59398a5c (2,165 bytes);
• chart layer/package sha256:ca2a3b60d01b33a9474e28932b41a8e64ac1c21931a9af45c8763b378938490d (52,177 bytes).

The anonymously downloaded public layer is byte-for-byte equal to the package in retained artifact 14059062209. I independently downloaded that artifact as a raw ZIP and reproduced 58787e865e0dfa89194ca6d6b688222c25a7098e1527cf1ea561436783f9c49a (52,883 bytes). Its evidence JSON agrees on chart/app/source/package/image identities and records anonymous_install: pass.

Package/source comparison is clean:

• exactly 28 packaged files;
• 27 non-Chart.yaml files are byte-identical to accepted source;
• packaged Chart.yaml is semantically identical to accepted source after replacing only dev.durable-workflow.source-revision: unreleased with the exact chart-touching commit f2edaa30e4dd330d8dbc408bb96cbf133c33484a;
• accepted chart source is unchanged from that commit through merge 29810619.

The protected run is SUCCESS at that accepted merge. Its public-verification job removed registry credentials, performed the anonymous OCI pull and clean kind install, and reported the same package digest. The configured image docker.io/durableworkflow/server:3.9.2 independently resolves anonymously to qualified index sha256:8ffcdb2a36af3129a1987849aafe8715fe0d3bf9a9648467f0b5cb8eeef43ba9, with the expected amd64/arm64 children.

This clears the Chart 1.7.1 content/OCI/anonymous-install gate for the paired Docs selector handoff. Scope remains limited: it does not infer installed client #216/#228 acceptance, Cloud adoption, draining-upload acceptance, or publication of the later dispatch-summary schema.

[rmcdaniel]

Root docs adoption is delivered through docs #538, merge cecdcc09d097c00799e6cc93b2490edc101ed076, protected Pages43470110585 SUCCESS. All24 changed public pages across eight locales, exact manifest and unchanged installers passed live readback.

The stable manifest selects Server3.9.2 / Chart1.7.1/app3.9.2, SHA256 d0bca325250f81ff6f9fa0cae696b4f6876ca64db1e0d5fcf72f309b403aa108. Its chart metadata is exactly OCI1275bdf2/packageca2a3b60/sourcef2edaa30/qualification43465478903, bound to native index8ffcdb2a/source5614274d. The upgrade path and reference describe no additional3.9.x schema step, rollback consequences, Unicode key/explicit receipt correction and opened-descriptor owner checks with trusted-ancestor/mapping limits.

This completes the root-docs selector/locales/build/public delivery slice. Installed client #216/#228, physical collector/Cloud mapping, draining uploads and next-schema dispatch retain their owners and exact evidence scopes; no broad acceptance is inferred. Both source and final artifact-data reviews are linked on538, including independent Security Chart publication/content PASS.