Durable Workflow 2.0 launch

[rmcdaniel]

Decision boundary

This is the launch checklist for Durable Workflow 2.0. Stable publication requires explicit human approval after every release-critical experiment passes against the frozen published tuple.

Current status: Complete. Durable Workflow 2.0 stable and its launch documentation are public.

Now

• Complete the GitHub-only cutover: Move project coordination and automation fully into GitHub #95
• Publish the final Server candidate against Workflow 2.0.0-rc.55
• Freeze the final-candidate tuple

Frozen tuple

Component	Version
Workflow	2.0.0-rc.55
Waterline	2.0.0-rc.35
Server	2.0.0-rc.71
CLI	2.0.0-rc.36
PHP SDK	2.0.0-rc.54
Python SDK	2.0.0-rc.44 (PyPI 2.0.0rc44)
Rust SDK	2.0.0-rc.39

Server image digest: sha256:75850d067706a2f3b1609c2f1045e2853fe0119f60a91881ddaa85830bb82279

Release-critical experiments

• activities
• child-workflows
• cloud
• heartbeats
• migration
• namespaces
• polyglot
• replay
• schedules
• sdk-matrix
• search-attributes
• signals-queries
• timers
• worker-versioning
• workflow-lifecycle
• workflow-updates

Stable release

• Confirm no release-critical product failure remains open
• Record the operating envelope and explicitly deferred failure modes
• Request explicit human stable-release approval
• Publish Workflow 2.0.0
• Publish CLI 2.0.0
• Publish Server 2.0.0
• Publish PHP SDK 2.0.0
• Publish Python SDK 2.0.0
• Publish Rust SDK 2.0.0
• Publish Waterline 2.0.0
• Verify stable installability, image provenance, and package metadata
• Publish the approved launch article and perform the post-launch docs cutover

Documentation redesign and other non-release-critical improvements remain deferred until after stable.