Ship Workflow 2.5.1 legacy replay fix in Server 2.5.7

[rmcdaniel]

Change

Pin the published Workflow 2.5.1 package at 13927608be9d4a366678a4beb477d1a3ee27a549 and prepare Server 2.5.7 / Helm chart 0.1.144.

Add an HTTP regression for a legacy PHP run whose timer already occupies the version call's history position. Repeated queries return the recorded state and preserve the run and history.

Generate the current Compose and Kubernetes release identities with the existing source-release synchronizer. The Composer update changes only the Workflow package.

Follow-through for durable-workflow/workflow#641 and durable-workflow/workflow#643.

Validation

• Registry-installed Workflow 2.5.1 passes 20 frozen-history cases, 216 assertions, and published Laravel 9–13 upgrade checks.
• Server HTTP regression passes: 1 test, 17 assertions.
• PHP code style and generated release metadata checks pass.
• Normal exact-head Server CI passes feature, Nexus and regression corpus checks, concurrent replay/query HTTP, MySQL/PostgreSQL rolling upgrades, polling cache growth/drain, and Helm lint/render/install.

Review

Reviewed the complete diff. Only the Workflow package changes in the locked dependency graph. Its production changes since 2.4.6 are the legacy query/offline replay fix and PHP schedule timeout support. The generated release identities agree with the single source manifest. The HTTP regression starts a real legacy timer wait and verifies repeated queries preserve the stored run and history.

Publication qualification

Server 2.5.7 is published at 6cb6f064e9b815d04c45bf7dc928f3db03e65e01, with manifest digest sha256:8a5d15512d23c63317996ca2d74e58d7cfdb59f4080850753d632008ca63af17. Release verification passes both architectures, bare readiness, source-free Compose, protocol catalog and anonymous chart installation. Chart 0.1.144 has digest sha256:ffb731ebb72d29bebcc4b6bba237b1f3403744697ccbea481a2f634e0f38c749.

Published replay qualification passes all 31 scenarios with no findings, October 7 at 10:00:18–10:06:23 UTC. The published image supplies the runner at the full Server source commit above. Exact tuple: Server 2.5.7 at that digest, Workflow 2.5.1, Waterline 2.2.0, CLI 2.1.3, PHP SDK 2.2.3, Python SDK 2.4.2, Rust SDK 3.2.0. Actual workers execute PHP, Python and Rust replay shards. Command: scripts/conformance/replay-published-artifacts.sh, with those exact version environment variables, running in the published image as UID/GID 1000:1000. The completed stack, volumes, dependency trees and scratch are removed.

Published schedules pass all 15 required cells with zero findings. The eight Docker shards measure 14 behavior scenarios at 10:01:07–10:36:27 UTC, including cadence, pause/resume/delete, missed fires, restart recovery, CLI and SDK controls, both PHP/Python directions, invalid cron and a missing workflow type. The install-only cell uses the verified receipts from the same published tuple's replay run. The unmodified published evaluator reads those receipts and the saved shard results at 10:43:22, without repeating the measurements. Waterline installation is verified. No Waterline UI schedule interaction or Rust schedule creation is claimed.

Command: scripts/conformance/schedules-published-artifacts.sh in the published image with the five concrete component versions above, exact Server digest and DW_SCHEDULES_SHARD_CONCURRENCY=1. Supply the same-tuple published installation receipts through DW_SCHEDULES_ARTIFACT_INSTALL_EVIDENCE. Final evaluation explicitly supplies DW_SCHEDULES_CADENCE_EVIDENCE and reuses the completed shards.

All schedule stacks, networks, volumes, dependency trees and scratch are removed. Sample App #147, Waterline #146 and website #170 are merged and verified, including Sample App image publication and the live installation defaults. Consumer follow-through for the owning defect is complete.