[rmcdaniel]

Both embedded sample applications can retain the MySQL Activity all() lost-wake bug through their 2.20.4 locks. Raise their Workflow floor and exact locks to published 2.20.5 and update the existing artifact manifest together.

The package row comes from the verified normal registry installation of 2.20.5 at b8f6bcdb951602b22259274b13b2261fdebff542. All other package records and Server/SDK/Waterline versions are unchanged. Composer computed both manifest content hashes; offline Composer validation, the existing artifact-graph validator and the public-boundary check pass. Normal hosted application/microservice MySQL and artifact checks are required before merge.

Closes #327. Upstream fix and published regression: durable-workflow/workflow#1052.

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

General Source/consumer qualification is PASS for exact c2f1045954dc03c7ba9deaf38ccdf38c2ec37261. Both embedded manifests now require Workflow^2.20.5; both locked package rows bind published2.20.5/b8f6bcdb, with canonical Composer content hashes and the matching qualified artifact entry. Full parsed-lock comparison confirms every unrelated package and lock field is unchanged.

All37 exact-head hosted checks are terminal SUCCESS, including both application/microservice MySQL suites on PHP8.4/8.5, committed-lock audits, the artifact graph, published polyglot/playground/upgrade/timer/recovery journeys, both disposable devcontainer architectures, CodeQL, Sonar and public boundary. No application/workflow source changed. The devcontainer publisher remains manual-only; normal main integration selects no image publication or production deployment.

Proceed with normal merge, then verify actual main and clean only this merged topic. Upstream published prevention and exact independent-connection MySQL regression remain in durable-workflow/workflow#1052; this update does not repair already-stranded executions.

[rmcdaniel]

Delivered and main-qualified: PR328 merged normally as 3c9c20a116c501653752c1a6efc1e218ad29d238, exact reviewed tree 04b2cfaf5f29c91ba4868add74e23bd326909d86, ordered parents e2c6bfa4c2401f6763787edb403618e3288c7f05 + c2f1045954dc03c7ba9deaf38ccdf38c2ec37261. All 37 PR checks and all 30 actual-main checks are terminal SUCCESS, including root/microservice MySQL, actual upgrade journeys, graph/security checks and disposable development-container controls.

Both root and microservice now require normal published Workflow ^2.20.5 and lock the exact released b8f6bcdb951602b22259274b13b2261fdebff542 package, carrying the Activity success-path lost-wake prevention. Exact published dependency metadata and Composer content hashes were verified; all other lock packages, SDK/Server/Waterline versions and application behavior are unchanged. This is prevention; no existing stranded workflow was repaired.

The own merged topic was removed with its expected-head lease, fresh Git absence and REST404; the local topic is absent and its clean detached accepted checkout is retained for audit. Other WIP was preserved. Issue327 is closed through this delivery. No development-container publication, production deployment or new release was selected.