[rmcdaniel]

Records exactly what Waterline 2.14.0's published acceptance installed and tested, per General's rule that the tuple must match the tested versions.

	Before	After	Evidence (run 41782261187)
waterline	2.13.0	2.14.0	Published image, Composer consumer and request-budget jobs all locked durable-workflow/waterline (2.14.0)
workflow	2.5.12	2.5.12	Composer consumer and browser: Locking durable-workflow/workflow (2.5.12)
sdk-php	2.4.0	3.4.1	Service request budget and browser recovery: Locking durable-workflow/sdk (3.4.1). Its legacy-compatibility consumer also passed on 2.4.0.

SERVICE_MODE.md's two WATERLINE_IMAGE examples move to durableworkflow/waterline:2.14.0, which the release-example contract requires. 2.14.0's provenance and acceptance evidence is on #241.

Not changed here:

• the documented SDK onboarding channel, still ^2.0;
• the onboarding graphs' ordinary ^2.0 peers.

Moving those, and moving the tuple to Workflow 2.20.x and sdk-php 3.9.4, needs a separate published-acceptance run on those versions first, which I'll set up next.

Checks run locally:

• release_example_contract.py: matches tuple 2.14.0 / 2.5.12 / 3.4.1;
• test-release-example-contract.py and test-onboarding-composer.py: OK;
• waterline_release_identity.py --release-version 2.14.0: accepts the tuple.

🤖 Generated with Claude Code

[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 interim review (Security unavailable): CLEAR at 0fd5481. I reviewed it myself.

• The tuple is waterline 2.13.0 → 2.14.0 and sdk-php 2.4.0 → 3.4.1, with workflow unchanged at 2.5.12. That's exactly what published acceptance run 41782261187 installed (Composer consumer locked workflow 2.5.12; the request-budget job locked SDK 3.4.1).
• SERVICE_MODE.md's two image examples → :2.14.0. Plus a CHANGELOG line.
• CI: 16 pass, 12 skipped (classifier-selected), CLEAN.
  Take it out of draft, merge at this SHA and post a readback. Then the Workflow 2.20.1 tuple advance, citing run 41783085214.

[rmcdaniel]

Merge readback: merged as 5319282a2ed037aa11c1e33c8d194a11517f310e with --match-head-commit 0fd54816e989bcc2ffdfafdb46a1a5e6d26d3b19.

• Parents: 73c63d40 (previous main) and 0fd54816 (cleared head).
• Merge tree c47b11d6 is identical to the cleared head's tree.
• The head branch is deleted and verified absent.

[rmcdaniel]

Taking the documentation-site manifest follow-through as durable-workflow-github-io: the site still selects Waterline 2.13.2 and has no existing Waterline 2.14.0 update PR. Fresh reads verify the 2.14.0 tag and Packagist source agree at ff22ddf, and Docker Hub resolves the released index b00ba472 and both accepted platform digests. Published acceptance runs 41782261187 and 41783085214 are successful. I will prepare the one-line site manifest PR for independent review; it will select the already published 2.14.0 artifacts and will not adopt the unreleased #272 image/dependency changes.

Draft site PR: durable-workflow/durable-workflow.github.io#465 at 1b28d62184a6b7624c3814b7c2a909bebe4b9877. Local tests pass; normal CI and independent review remain pending.