Adopt grouped condition recovery in Server 2.4.37

[rmcdaniel]

Product fix

Adopt published Workflow 2.3.2 in stable Server 2.4.37, so ordinary service Workers can reopen a condition inside a nested parallel group or keyed selection, then complete it from a sufficient signal or delayed deadline.

The Native fix is reviewed and merged in durable-workflow/workflow#602. Exact published package source and dist reference: d8594a67661f63f17d76cd5a1a1349c2d28f4a6d.

Change

• Pin only durable-workflow/workflow from 2.3.1 to 2.3.2. Composer reports one package update and no installs or removals.
• Advance the source release record to Server 2.4.37 and chart 0.1.133, then regenerate the repository's release consumers with sync-source-release.mjs --write.
• Build from stable main. Ordinary Worker protocol remains 1.19. Cooperative cancellation PR feat: add cooperative cancellation requests and claim-bound delivery #291 remains separate.

Qualification and follow-through

• The final Native database/Laravel/corpus/coverage matrix passes. The five actual Rust Worker source cases pass with typed final results and a fresh process per claim: fix: reopen recorded service conditions within groups workflow#602 (comment).
• Rust SDK 2.1.3 includes the corresponding replay correction and is published and registry-verified from reviewed PR fix: replay grouped condition physical reopens sdk-rust#56, source e948cab74406f8e245bd8f761ddb65e4e662ce20. Native's published upgrade checks pass across Laravel 9–13.
• Server's normal checks must pass before merge. Publish 2.4.37 through the repository release workflow and verify the exact image digest.
• Run the published PHP/Python/Rust lifecycle and affected replay checks, plus all five grouped-condition cases using registry Rust 2.1.3 and the published Server digest. Record the exact tuple before closing the Native issue.

Refs durable-workflow/workflow#601 and durable-workflow/.github#136. This does not activate cooperative cancellation or make a Cloud deployment claim.

[rmcdaniel]

Native 2.3.2 published-package and all Laravel 9–13 upgrade checks pass in https://github.com/durable-workflow/workflow/actions/runs/36902068052. Rust 2.1.3 publication and exact registry verification pass in https://github.com/durable-workflow/sdk-rust/actions/runs/36902057106. Helm lint/render/schema checks pass. The kind install job stopped before chart tests while installing kind v0.23.0, with sha256sum reporting no properly formatted checksum lines. Retrying only that failed job once on the unchanged source commit. The gate remains required.

[rmcdaniel]

Reviewed 6890a1457d12ae7ea9136f5480bbadf372616851 and its downstream package identity.

• Composer updates only Native 2.3.1 to published 2.3.2, with identical source/dist reference d8594a67661f63f17d76cd5a1a1349c2d28f4a6d.
• Server 2.4.37 and chart 0.1.133 consumers match the generated release record. No Server application code or cooperative feature activation is included.
• Native's published package and all Laravel 9–13 upgrade checks pass. Rust 2.1.3 publication verifies exact registry bytes and a fresh Rust 1.86 consumer.
• All current Server PR checks pass: feature/Nexus/corpus, repository contracts, MySQL/PostgreSQL predecessor/successor, HTTP replay/query topology, polling bounded-growth smoke, and Helm lint/render/schema/install. The kind download retry passes on the same unchanged source.

Ready to merge and publish the exact stable image. Keep workflow #601 open for published replay, lifecycle and all five actual grouped-condition Worker cases. Cloud and cooperative cancellation delivery remain separately qualified.