Make the Rust Cloud first-run path current and task-oriented

[rmcdaniel]

Problem

The Rust worker API is usable, but a first-time Cloud evaluator still has to assemble the path from generated API reference, broad protocol documentation, and sample-app conformance code. The Rust documentation landing page redirects directly to generated reference material, the Sample App pins an older Rust SDK than the current published release, and the direct HTTP fallback does not prominently show the required control-plane version header.

The supported journey should be obvious: use separate client and worker credentials, connect both to one namespace runtime URL, start a workflow, execute an activity, and inspect the completed result.

Acceptance criteria

• The Rust documentation site has a task-oriented landing page and a minimal Cloud quickstart before the generated API reference.
• The quickstart shows separate client and worker credentials, one namespace-scoped runtime URL, one task queue, workflow start, activity execution, result retrieval, and clean worker shutdown.
• The Sample App provides a memorable runnable Rust Cloud path from a fresh Codespace without requiring source inspection or a custom release build command.
• Sample App Rust dependencies and displayed version evidence come from the current supported product train; a stale checked-in prerelease cannot silently remain the evaluator default.
• Canonical CLI examples use the supported Cloud-aware CLI path. Raw HTTP examples include every required version header and explain that they are protocol examples, not the normal onboarding path.
• A clean-machine test follows only the published instructions and completes a Rust workflow and activity against Cloud.
• The resulting run is visible through the managed operator surface, and the validation records the exact SDK, CLI, and runtime versions used.

Required source targets

durable-workflow/durable-workflow.github.io@main
durable-workflow/sample-app@main
durable-workflow/sdk-rust@main

[rmcdaniel]

Fresh Codespace evidence on 2026-08-11 narrows the remaining work:

• The prepared image now provides Rust, Cargo, and dw; no tool installation was needed.
• A Rust workflow and activity completed against a managed namespace.
• The evaluator still had to inspect the comprehensive conformance worker because there was no obvious minimal Rust Cloud entrypoint.
• Version guidance is materially out of sync: Sample App pins Rust SDK 2.0.0-rc.5, the generated quickstart contract names 2.0.0-rc.7, and the current published Rust SDK is 2.0.0-rc.11.
• The canonical CLI path failed and forced a raw HTTP fallback; that transport defect is isolated in Support namespace-scoped Cloud runtime URLs in CLI discovery cli#18.
• The raw HTTP path only became usable after the runtime reported the missing control-plane version header.

Keep this open until the clean-machine test can follow one published, current-version Rust Cloud path without source inspection or protocol-level recovery.

[rmcdaniel]

Fresh evaluator evidence (2026-08-11): the Rust docs root still behaves as a redirect into generated API reference, so the evaluator relied on Sample App conformance worker as the practical tutorial. The checkout pinned Rust SDK 2.0.0-rc.5 while the aggregate docs named rc.7 and crates.io exposed rc.11. Authoring compiled and the Cloud worker completed, but workflow start required the CLI-to-raw-HTTP workaround tracked in durable-workflow/cli#18. The canonical first-run proof must use the current train, a minimal caller-owned example, and the supported CLI path; success through the existing matrix worker is useful compatibility evidence but does not satisfy this issue.

[rmcdaniel]

Cross-repository landing evidence (generated from trusted implementation pull requests or authenticated protected-branch completion records):

Target	Latest attempt	Bound provenance	Landing	Required qualification	State
durable-workflow/durable-workflow.github.io@main	Not linked	Pending	Pending	Pending: Executable documentation contracts; required: Executable documentation contracts	pending:no-linked-pull-request
durable-workflow/sample-app@main	Not linked	Pending	Pending	Pending: Target branch qualification, docker compose sample workflows, polyglot smoke (PHP/Python/Rust); required: Target branch qualification, docker compose sample workflows, polyglot smoke (PHP/Python/Rust)	pending:no-linked-pull-request
durable-workflow/sdk-rust@main	Not linked	Pending	Pending	Pending: Target branch qualification; required: Target branch qualification	pending:no-linked-pull-request

The parent remains open until every declared target is complete.