Skip to content

Clarify timer SDK conformance boundary - #140

Merged
rmcdaniel merged 1 commit into
mainfrom
docs/timer-sdk-coverage-boundary
Sep 27, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
docs/timer-sdk-coverage-boundary

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

What changed

Clarify that the current published-artifact timer runner covers embedded PHP workflow timer scenarios in the Server image. It does not execute the released PHP, Python, or Rust service-mode workflow timer paths. The stable runbook now makes that boundary and the next executable evidence clear.

Evidence

  • Inspected the timer scenario manifest and scripts/conformance/timers-published-artifacts.sh: the required artifacts include the Server image, CLI, PHP Workflow package, Python SDK pin, and Waterline; the focused host probe runs Workflow\V2\timer in PHP inside the Server image. It does not run a Python SDK worker or require the PHP/Rust SDK artifacts.
  • Verified durable timer methods in released SDK source: PHP SDK 2.1.4 WorkflowContext::sleep, Python SDK 2.0.0 WorkflowContext.sleep/start_timer, Rust SDK 2.1.1 WorkflowContext::sleep/start_timer.
  • git diff --check passed. This PR changes documentation only and claims no new runtime pass.

Part of #122. Follow-up is executable published-artifact SDK worker timer evidence per relevant runtime, including restart/replay and cancellation behavior.

@rmcdaniel
rmcdaniel merged commit 1734024 into main Sep 27, 2026
1 check passed
@rmcdaniel
rmcdaniel deleted the docs/timer-sdk-coverage-boundary branch September 27, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants